Question 100A paid media API uses unsigned Cloud CDN links that anyone can forward to bypass access controls. After this change — Configure signed URLs or another appropriate access control for protected content delivery. — which observation would best demonstrate that it worked? Only properly authenticated edge-to-origin requests reach the private upstream service. Repeated test requests for one session reach the expected backend until its health changes. A validating resolver accepts genuine records and rejects a deliberately invalid signature. An authorized signed request succeeds while an expired or altered signature is rejected. ExplanationCorrect Answer D:An authorized signed request succeeds while an expired or altered signature is rejected. The evidence tests the actual dependency: CDN caching alone does not authenticate requests for restricted media. An uncorrected condition risks: Unauthenticated asset URLs can make licensed content broadly available. Incorrect Answers A:An external CDN origin has distinct network and trust assumptions from a Google-managed backend. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An authorized signed request succeeds while an expired or altered signature is rejected. B:Backend affinity is an explicit load-balancer behavior, not a guaranteed property of every HTTP request. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An authorized signed request succeeds while an expired or altered signature is rejected. C:DNSSEC validation relies on consistent child signing and parent delegation information. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An authorized signed request succeeds while an expired or altered signature is rejected.
Question 101A GKE service must be internal to the enterprise but its developers select a public-facing Gateway class. The team proposes: Choose the supported internal Gateway or internal load-balancing configuration for the application's scope. Which networking principle explains why this change is appropriate? The Gateway controller's class and traffic policy determine whether application entry is private or public. Hybrid DNS forwarding requires explicit authority and one-way recursion boundaries. Location, edge entry and service tier are architecture decisions with measurable cost and latency effects. Google Cloud VPCs are global networks, while subnets and many operational resources remain regional. ExplanationCorrect Answer A:The Gateway controller's class and traffic policy determine whether application entry is private or public. Under these conditions, the remedy follows from the principle: Choose the supported internal Gateway or internal load-balancing configuration for the application's scope. Confirm: Internal clients can connect while external probes cannot reach a public application entry. Incorrect Answers B:Hybrid DNS forwarding requires explicit authority and one-way recursion boundaries. This does not establish the proposed intervention. The governing principle here is: The Gateway controller's class and traffic policy determine whether application entry is private or public. Apply it by: Choose the supported internal Gateway or internal load-balancing configuration for the application's scope. C:Location, edge entry and service tier are architecture decisions with measurable cost and latency effects. This does not establish the proposed intervention. The governing principle here is: The Gateway controller's class and traffic policy determine whether application entry is private or public. Apply it by: Choose the supported internal Gateway or internal load-balancing configuration for the application's scope. D:Google Cloud VPCs are global networks, while subnets and many operational resources remain regional. This does not establish the proposed intervention. The governing principle here is: The Gateway controller's class and traffic policy determine whether application entry is private or public. Apply it by: Choose the supported internal Gateway or internal load-balancing configuration for the application's scope.
Question 102A financial service configures a star topology but expects two edge spokes to communicate without passing the approved central hub policy. After this change — Use the NCC topology model that reflects authorized spoke-to-spoke communications. — which observation would best demonstrate that it worked? A test from one branch to another follows only the designated hub-controlled path. Each spoke's effective destination routes remain distinct in controlled reachability tests. The intended workload matches the allow policy and a neighboring workload does not. Gateway routes lead to healthy Pods with an authorized response from a synthetic client. ExplanationCorrect Answer A:A test from one branch to another follows only the designated hub-controlled path. The relevant control is operating as intended. Star and mesh designs have different connectivity and isolation behaviors. An unresolved issue would mean: A topology mismatch can bypass inspection or prevent required branch connectivity. Incorrect Answers B:A central connectivity fabric cannot infer tenant identity from duplicated destination CIDRs. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test from one branch to another follows only the designated hub-controlled path. C:Service-account-targeted firewall policy requires the correct identity association in the destination environment. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test from one branch to another follows only the designated hub-controlled path. D:GKE load-balancer endpoints must become healthy and discoverable before external traffic can be served. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test from one branch to another follows only the designated hub-controlled path.
Question 103A compliance service requires Layer 4 source-IP preservation but the team selects a proxy design that changes the observed client address. After this change — Select a supported passthrough load-balancing architecture and review backend source visibility. — which observation would best demonstrate that it worked? An approved cross-region client reaches the service without opening an internet path. Regional clients receive the intended answers and a failing target is excluded after evaluation. The backend log shows the required approved client source behavior on test TCP flows. A new installer build appears through a new URL while old versions follow retention policy. ExplanationCorrect Answer C:The backend log shows the required approved client source behavior on test TCP flows. The result directly exercises the remedy: Select a supported passthrough load-balancing architecture and review backend source visibility. It reduces the risk that wrong proxy semantics can disrupt source-dependent network controls. Incorrect Answers A:Regional internal load-balancer reachability is not automatically universal across every network location. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The backend log shows the required approved client source behavior on test TCP flows. B:DNS response policies can direct clients based on location and health, within DNS caching limits. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The backend log shows the required approved client source behavior on test TCP flows. D:Cache immutability should align with an object's versioning and security update requirements. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The backend log shows the required approved client source behavior on test TCP flows.
Question 104A shared cloud hub changes routing mode but team members look only at the local Cloud Router peer's session state. What is the most direct consequence of leaving the problem uncorrected? Overbroad advertisements can redirect or expose third-party traffic. Peering transitivity assumptions can cause unexpected site isolation. Local-only validation can conceal remote-region path regressions. An unsupported failover assumption can lead to preventable regional outages. ExplanationCorrect Answer C:Local-only validation can conceal remote-region path regressions. That harm follows from the missing network or security control. Cloud Router BGP state does not alone prove regional workload routing decisions. Repair it by: Inspect effective VPC routes in all affected regions after the dynamic routing mode adjustment. Incorrect Answers A:BGP advertisement scope should follow actual ownership and route policy rather than convenience summaries. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Local-only validation can conceal remote-region path regressions. B:Hybrid network transit depends on explicitly supported spoke types and topology configuration. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Local-only validation can conceal remote-region path regressions. D:Classic and HA VPN differ in available availability and routing behavior. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Local-only validation can conceal remote-region path regressions.
Question 105A platform owner selects an address block for GKE Pods that overlaps an already advertised datacenter route. The team proposes: Choose a compatible Pod range and update the hybrid IPAM registry before cluster build. Which networking principle explains why this change is appropriate? Connectivity selection depends on throughput, availability and security constraints, not only tunnel setup ease. The smallest supported transport segment limits the effective packet size of an end-to-end path. Availability must consider an entire regional failure domain, not merely redundant instances in one zone. Pod ranges participate in real network reachability and must not conflict with hybrid destination prefixes. ExplanationCorrect Answer D:Pod ranges participate in real network reachability and must not conflict with hybrid destination prefixes. The principle explains the failed dependency. Choose a compatible Pod range and update the hybrid IPAM registry before cluster build. Then verify: A Pod-to-datacenter test reaches only the approved target without ambiguous routes. Incorrect Answers A:Connectivity selection depends on throughput, availability and security constraints, not only tunnel setup ease. This does not establish the proposed intervention. The governing principle here is: Pod ranges participate in real network reachability and must not conflict with hybrid destination prefixes. Apply it by: Choose a compatible Pod range and update the hybrid IPAM registry before cluster build. B:The smallest supported transport segment limits the effective packet size of an end-to-end path. This does not establish the proposed intervention. The governing principle here is: Pod ranges participate in real network reachability and must not conflict with hybrid destination prefixes. Apply it by: Choose a compatible Pod range and update the hybrid IPAM registry before cluster build. C:Availability must consider an entire regional failure domain, not merely redundant instances in one zone. This does not establish the proposed intervention. The governing principle here is: Pod ranges participate in real network reachability and must not conflict with hybrid destination prefixes. Apply it by: Choose a compatible Pod range and update the hybrid IPAM registry before cluster build.
Question 106A firewall team configures an egress rule but mistakenly sets ingress direction and the application still reaches a forbidden internet endpoint. The team proposes: Correct the rule direction and match criteria under the actual effective policy order. Which networking principle explains why this change is appropriate? Ingress and egress are different policy enforcement directions and cannot be used interchangeably. Out-of-band security integration is a detection workflow distinct from the traffic-forwarding data plane. Edge and backend security policies have different attachment and request-processing characteristics. Cloud NAT performs translation; it does not replace application-aware web proxy controls. ExplanationCorrect Answer A:Ingress and egress are different policy enforcement directions and cannot be used interchangeably. Applying this rule leads to the stated remedy: Correct the rule direction and match criteria under the actual effective policy order. The expected outcome is: The prohibited outbound connection is blocked and the approved egress path remains usable. Incorrect Answers B:Out-of-band security integration is a detection workflow distinct from the traffic-forwarding data plane. This does not establish the proposed intervention. The governing principle here is: Ingress and egress are different policy enforcement directions and cannot be used interchangeably. Apply it by: Correct the rule direction and match criteria under the actual effective policy order. C:Edge and backend security policies have different attachment and request-processing characteristics. This does not establish the proposed intervention. The governing principle here is: Ingress and egress are different policy enforcement directions and cannot be used interchangeably. Apply it by: Correct the rule direction and match criteria under the actual effective policy order. D:Cloud NAT performs translation; it does not replace application-aware web proxy controls. This does not establish the proposed intervention. The governing principle here is: Ingress and egress are different policy enforcement directions and cannot be used interchangeably. Apply it by: Correct the rule direction and match criteria under the actual effective policy order.
Question 107A media company connects Google Cloud to another hyperscaler through Cross-Cloud Interconnect but never provisions the receiving cloud's required virtual interface. The team proposes: Coordinate both cloud-side connection and VLAN attachment provisioning before route activation. Which networking principle explains why this change is appropriate? Cloud VPN IKE negotiation requires the actual current reachable peer identity. BGP neighbor establishment depends on coherent local and peer autonomous-system identities. Cross-cloud private connectivity has separate endpoint requirements in both cloud environments. High availability requires appliance placement and health beyond a logical hub configuration. ExplanationCorrect Answer C:Cross-cloud private connectivity has separate endpoint requirements in both cloud environments. The distinction connects the symptoms to the proposed engineering work. Coordinate both cloud-side connection and VLAN attachment provisioning before route activation. Evidence: BGP and application traffic flow across the approved cross-cloud attachments. Incorrect Answers A:Cloud VPN IKE negotiation requires the actual current reachable peer identity. This does not establish the proposed intervention. The governing principle here is: Cross-cloud private connectivity has separate endpoint requirements in both cloud environments. Apply it by: Coordinate both cloud-side connection and VLAN attachment provisioning before route activation. B:BGP neighbor establishment depends on coherent local and peer autonomous-system identities. This does not establish the proposed intervention. The governing principle here is: Cross-cloud private connectivity has separate endpoint requirements in both cloud environments. Apply it by: Coordinate both cloud-side connection and VLAN attachment provisioning before route activation. D:High availability requires appliance placement and health beyond a logical hub configuration. This does not establish the proposed intervention. The governing principle here is: Cross-cloud private connectivity has separate endpoint requirements in both cloud environments. Apply it by: Coordinate both cloud-side connection and VLAN attachment provisioning before route activation.
Question 108A company defines a forwarding policy for partner DNS but has no route or firewall path to the partner resolver IP addresses. Which Google Cloud networking change should the engineer make first? Establish approved hybrid resolver connectivity before enabling the Cloud DNS forwarding target. Configure supported connection draining and staged backend rollouts. Invalidate the affected Cloud CDN cache entries or use versioned asset URLs. Configure a supported backend bucket and activate CDN for the required frontend. ExplanationCorrect Answer A:Establish approved hybrid resolver connectivity before enabling the Cloud DNS forwarding target. The outcome depends on this distinction: A DNS policy cannot resolve through a target that is unreachable at the transport layer. A successful deployment shows: Forwarded partner lookups complete and are visible in both resolver and network logs. Incorrect Answers B:Connection draining separates new connection admission from completing existing client transactions. That is relevant to a different intervention. For the stated situation, the required action is: Establish approved hybrid resolver connectivity before enabling the Cloud DNS forwarding target. The governing reason is: A DNS policy cannot resolve through a target that is unreachable at the transport layer. C:An origin update does not instantly replace every cached object at distributed edges. That is relevant to a different intervention. For the stated situation, the required action is: Establish approved hybrid resolver connectivity before enabling the Cloud DNS forwarding target. The governing reason is: A DNS policy cannot resolve through a target that is unreachable at the transport layer. D:Cloud CDN origin support depends on an eligible backend integration with the serving load balancer. That is relevant to a different intervention. For the stated situation, the required action is: Establish approved hybrid resolver connectivity before enabling the Cloud DNS forwarding target. The governing reason is: A DNS policy cannot resolve through a target that is unreachable at the transport layer.
Question 109An internal Application Load Balancer serves only regional clients but the application must now be reached from authorized remote regions. The team proposes: Enable the supported global access capability or choose an appropriate global internal design. Which networking principle explains why this change is appropriate? An external CDN origin has distinct network and trust assumptions from a Google-managed backend. Regional internal load-balancer reachability is not automatically universal across every network location. A DNS policy cannot resolve through a target that is unreachable at the transport layer. Serverless CDN integration requires the correct backend and ingress design. ExplanationCorrect Answer B:Regional internal load-balancer reachability is not automatically universal across every network location. Under these conditions, the remedy follows from the principle: Enable the supported global access capability or choose an appropriate global internal design. Confirm: An approved cross-region client reaches the service without opening an internet path. Incorrect Answers A:An external CDN origin has distinct network and trust assumptions from a Google-managed backend. This does not establish the proposed intervention. The governing principle here is: Regional internal load-balancer reachability is not automatically universal across every network location. Apply it by: Enable the supported global access capability or choose an appropriate global internal design. C:A DNS policy cannot resolve through a target that is unreachable at the transport layer. This does not establish the proposed intervention. The governing principle here is: Regional internal load-balancer reachability is not automatically universal across every network location. Apply it by: Enable the supported global access capability or choose an appropriate global internal design. D:Serverless CDN integration requires the correct backend and ingress design. This does not establish the proposed intervention. The governing principle here is: Regional internal load-balancer reachability is not automatically universal across every network location. Apply it by: Enable the supported global access capability or choose an appropriate global internal design.
Question 110A network administrator deploys HA VPN over Cloud Interconnect but forgets to configure one of the planned VPN gateway interfaces. The team proposes: Complete the supported redundant VPN tunnel and interface pairing over the Interconnect topology. Which networking principle explains why this change is appropriate? Encrypting a hybrid interconnect can introduce its own tunnel-level redundancy dependencies. A tunnel cannot establish when its peers have no compatible security proposals. Cloud Router BGP state does not alone prove regional workload routing decisions. Spoke operational status does not prove the topology provides required site-to-site transitivity. ExplanationCorrect Answer A:Encrypting a hybrid interconnect can introduce its own tunnel-level redundancy dependencies. The network behavior in the question follows this rule. Complete the supported redundant VPN tunnel and interface pairing over the Interconnect topology. Check success by observing: Each protected tunnel establishes and the application stays reachable after one interface fails. Incorrect Answers B:A tunnel cannot establish when its peers have no compatible security proposals. This does not establish the proposed intervention. The governing principle here is: Encrypting a hybrid interconnect can introduce its own tunnel-level redundancy dependencies. Apply it by: Complete the supported redundant VPN tunnel and interface pairing over the Interconnect topology. C:Cloud Router BGP state does not alone prove regional workload routing decisions. This does not establish the proposed intervention. The governing principle here is: Encrypting a hybrid interconnect can introduce its own tunnel-level redundancy dependencies. Apply it by: Complete the supported redundant VPN tunnel and interface pairing over the Interconnect topology. D:Spoke operational status does not prove the topology provides required site-to-site transitivity. This does not establish the proposed intervention. The governing principle here is: Encrypting a hybrid interconnect can introduce its own tunnel-level redundancy dependencies. Apply it by: Complete the supported redundant VPN tunnel and interface pairing over the Interconnect topology.