Question 320A control-plane authorized network list includes a discontinued office address but omits the new operations VPN range. After this change — Update the authorized network list to the current verified operator source ranges. — which observation would best demonstrate that it worked? An operator connects from the current VPN while the retired source no longer gains access. Cluster creation completes in the service project without broad host project ownership. Authorized health probes reach the service while requests from an unapproved source remain blocked. New VM instances inherit the tag and choose the authorized next-hop route. ExplanationCorrect Answer A:An operator connects from the current VPN while the retired source no longer gains access. The observation verifies the stated change. Allowlisting access to cluster control planes must track changes to administrator network locations. It also helps prevent this exposure: Outdated administration allowlists create denial or unnecessary exposure. Incorrect Answers B:GKE cluster provisioning across projects requires explicit host-network authorization. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An operator connects from the current VPN while the retired source no longer gains access. C:VPC routing alone does not allow ingress traffic that the effective firewall policy denies. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An operator connects from the current VPN while the retired source no longer gains access. D:Tag-based routing eligibility depends on actual instance metadata, not an operator's intention. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An operator connects from the current VPN while the retired source no longer gains access.
Question 321A corporate DNS design forwards a private zone back to itself through on-premises resolvers and creates recursive timeout loops. Which Google Cloud networking change should the engineer make first? Define directional forwarding and DNS peering paths that avoid cyclic resolution. Define a hierarchical IPAM allocation with address-space reservations for future networks and managed services. Distribute critical workloads over adequately sized node pools and planned zones. Design geographically redundant backends and the appropriate cross-region frontend failover strategy. ExplanationCorrect Answer A:Define directional forwarding and DNS peering paths that avoid cyclic resolution. This addresses the underlying network dependency. Hybrid DNS forwarding requires explicit authority and one-way recursion boundaries. Confirm the change by checking: Repeated internal-name lookups resolve quickly without cyclical query logs. Incorrect Answers B:Private address conservation is a multi-environment capacity and overlap-planning problem. That is relevant to a different intervention. For the stated situation, the required action is: Define directional forwarding and DNS peering paths that avoid cyclic resolution. The governing reason is: Hybrid DNS forwarding requires explicit authority and one-way recursion boundaries. C:GKE networking availability also depends on node and scheduling failure domains. That is relevant to a different intervention. For the stated situation, the required action is: Define directional forwarding and DNS peering paths that avoid cyclic resolution. The governing reason is: Hybrid DNS forwarding requires explicit authority and one-way recursion boundaries. D:Availability must consider an entire regional failure domain, not merely redundant instances in one zone. That is relevant to a different intervention. For the stated situation, the required action is: Define directional forwarding and DNS peering paths that avoid cyclic resolution. The governing reason is: Hybrid DNS forwarding requires explicit authority and one-way recursion boundaries.
Question 322A platform operator assumes enabling GKE Dataplane V2 automatically imports every existing legacy NetworkPolicy rule unchanged. Which Google Cloud networking change should the engineer make first? Reconcile dependent address allowlists and confirm the supported subnet range expansion. Use the NCC topology model that reflects authorized spoke-to-spoke communications. Configure compatible custom route export and import settings on the intended peering. Validate the supported Dataplane V2 policy behavior and test the application's intended allow and deny rules. ExplanationCorrect Answer D:Validate the supported Dataplane V2 policy behavior and test the application's intended allow and deny rules. Dataplane implementation choices require policy compatibility and enforcement verification. In a controlled test, approved Pod traffic passes and disallowed cross-namespace traffic is rejected in a controlled test. Without the change, unexpected policy semantics can create outages or lateral network exposure. Incorrect Answers A:Changing a VPC subnet range does not automatically update independent external security allowlists. That is relevant to a different intervention. For the stated situation, the required action is: Validate the supported Dataplane V2 policy behavior and test the application's intended allow and deny rules. The governing reason is: Dataplane implementation choices require policy compatibility and enforcement verification. B:Star and mesh designs have different connectivity and isolation behaviors. That is relevant to a different intervention. For the stated situation, the required action is: Validate the supported Dataplane V2 policy behavior and test the application's intended allow and deny rules. The governing reason is: Dataplane implementation choices require policy compatibility and enforcement verification. C:Custom static and dynamic route exchange over peering is not assumed from peering connectivity alone. That is relevant to a different intervention. For the stated situation, the required action is: Validate the supported Dataplane V2 policy behavior and test the application's intended allow and deny rules. The governing reason is: Dataplane implementation choices require policy compatibility and enforcement verification.
Question 323A support engineer sees an NCC spoke marked active and concludes that a missing service route must be a firewall issue. Which Google Cloud networking change should the engineer make first? Inspect NCC propagated routes, spoke association and range filters before changing firewall rules. Validate supported Service, Gateway and NEG configuration and allow health check traffic. Design supported explicit connectivity instead of relying on peering for transitive appliance routes. Bind the intended workload service identity and scope the policy to its actual service account. ExplanationCorrect Answer A:Inspect NCC propagated routes, spoke association and range filters before changing firewall rules. The intervention corrects the described failure rather than a nearby symptom. Spoke health and destination-specific connectivity are separate states. Verification: A route-view correction restores the intended prefix and the application transaction succeeds. Incorrect Answers B:GKE load-balancer endpoints must become healthy and discoverable before external traffic can be served. That is relevant to a different intervention. For the stated situation, the required action is: Inspect NCC propagated routes, spoke association and range filters before changing firewall rules. The governing reason is: Spoke health and destination-specific connectivity are separate states. C:Peer route exchange does not transform arbitrary next-hop insertion into transitive multi-VPC forwarding. That is relevant to a different intervention. For the stated situation, the required action is: Inspect NCC propagated routes, spoke association and range filters before changing firewall rules. The governing reason is: Spoke health and destination-specific connectivity are separate states. D:Service-account-targeted firewall policy requires the correct identity association in the destination environment. That is relevant to a different intervention. For the stated situation, the required action is: Inspect NCC propagated routes, spoke association and range filters before changing firewall rules. The governing reason is: Spoke health and destination-specific connectivity are separate states.
Question 324An e-commerce backend needs to rewrite an inbound URL path before forwarding to a legacy service. Which Google Cloud networking change should the engineer make first? Invalidate the affected Cloud CDN cache entries or use versioned asset URLs. Configure the supported URL rewrite on the appropriate application load-balancer route. Coordinate authoritative record import and delegation cutover at the domain registrar. Version release URLs and apply cache lifetimes that support security update propagation. ExplanationCorrect Answer B:Configure the supported URL rewrite on the appropriate application load-balancer route. The outcome depends on this distinction: HTTP path transformations are proxy-level functions that must match the chosen load-balancer class. A successful deployment shows: A test request arrives at the legacy backend with the intended rewritten path. Incorrect Answers A: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: Configure the supported URL rewrite on the appropriate application load-balancer route. The governing reason is: HTTP path transformations are proxy-level functions that must match the chosen load-balancer class. C:Creating a DNS zone does not transfer internet authority until delegation is changed. That is relevant to a different intervention. For the stated situation, the required action is: Configure the supported URL rewrite on the appropriate application load-balancer route. The governing reason is: HTTP path transformations are proxy-level functions that must match the chosen load-balancer class. D:Cache immutability should align with an object's versioning and security update requirements. That is relevant to a different intervention. For the stated situation, the required action is: Configure the supported URL rewrite on the appropriate application load-balancer route. The governing reason is: HTTP path transformations are proxy-level functions that must match the chosen load-balancer class.
Question 325A platform team receives a Network Analyzer warning about a subnet range nearing exhaustion but assumes it is a transient console glitch. Which Google Cloud networking change should the engineer make first? Investigate the detected capacity issue and expand or redistribute supported subnet allocations. Validate gateway public peer reachability and route before modifying approved cryptography. Create a targeted Cloud Router BGP-session alert with peer and attachment context. Drain the backend using the supported load-balancer capacity and connection-draining workflow. ExplanationCorrect Answer A:Investigate the detected capacity issue and expand or redistribute supported subnet allocations. Network Analyzer warnings are actionable configuration observations that need evidence-based triage. Its operational proof is: Address-capacity metrics improve and new instances receive valid addresses. The avoidable impact is: Ignored subnet exhaustion can halt deployment of essential services. Incorrect Answers B:IKE negotiation requires a reachable underlying transport path independent of crypto proposals. That is relevant to a different intervention. For the stated situation, the required action is: Investigate the detected capacity issue and expand or redistribute supported subnet allocations. The governing reason is: Network Analyzer warnings are actionable configuration observations that need evidence-based triage. C:Routing session availability needs timely control-plane monitoring beyond periodic manual inspection. That is relevant to a different intervention. For the stated situation, the required action is: Investigate the detected capacity issue and expand or redistribute supported subnet allocations. The governing reason is: Network Analyzer warnings are actionable configuration observations that need evidence-based triage. D:Graceful backend removal must distinguish active in-flight requests from new session admission. That is relevant to a different intervention. For the stated situation, the required action is: Investigate the detected capacity issue and expand or redistribute supported subnet allocations. The governing reason is: Network Analyzer warnings are actionable configuration observations that need evidence-based triage.
Question 326A regulated backup connection uses a shared secret copied from another partner VPN and lacks a rotation owner. Which Google Cloud networking change should the engineer make first? Correct the approved BGP ASN pairing and verify session capabilities with the peer operator. Use independently managed supported VPN credentials and document rotation responsibilities. Estimate NCC data-transfer consumption and validate it against the approved hybrid route design. Reconcile attachment capacity settings and approved utilization against the actual traffic forecast. ExplanationCorrect Answer B:Use independently managed supported VPN credentials and document rotation responsibilities. This step targets the failure path itself. Site-to-site VPN security relies on a separate peer trust boundary for each partner. Observe: Rotating the pilot partner secret leaves unrelated tunnels unaffected and the intended tunnel reconnects. Incorrect Answers A:BGP neighbor establishment depends on coherent local and peer autonomous-system identities. That is relevant to a different intervention. For the stated situation, the required action is: Use independently managed supported VPN credentials and document rotation responsibilities. The governing reason is: Site-to-site VPN security relies on a separate peer trust boundary for each partner. C:Transit design carries capacity and commercial constraints that differ from simple endpoint attachment. That is relevant to a different intervention. For the stated situation, the required action is: Use independently managed supported VPN credentials and document rotation responsibilities. The governing reason is: Site-to-site VPN security relies on a separate peer trust boundary for each partner. D:Link-level physical capacity and logical attachment capacity are distinct constraints. That is relevant to a different intervention. For the stated situation, the required action is: Use independently managed supported VPN credentials and document rotation responsibilities. The governing reason is: Site-to-site VPN security relies on a separate peer trust boundary for each partner.
Question 327An architect assigns a producer spoke to provide one restricted API service but clients are still using public service addresses. Which Google Cloud networking change should the engineer make first? Verify supported bidirectional routing and stateful appliance insertion for the targeted flows. Plan and add supported additional Pod ranges with sufficient allocation before scaling. Add the least-privilege ingress rule or firewall policy targeting the intended instances and probes. Create a supported private consumer endpoint and point clients at the private service name. ExplanationCorrect Answer D:Create a supported private consumer endpoint and point clients at the private service name. NCC producer connectivity alone does not reconfigure a consumer's DNS or application endpoint. The evidence to require before closing the incident is: A consumer resolves the approved private name and reaches the producer without public egress. Incorrect Answers A:Stateful network inspection requires coherent paths for request and response traffic. That is relevant to a different intervention. For the stated situation, the required action is: Create a supported private consumer endpoint and point clients at the private service name. The governing reason is: NCC producer connectivity alone does not reconfigure a consumer's DNS or application endpoint. B:Pod scheduling depends on alias-IP range capacity, not just available node CPU. That is relevant to a different intervention. For the stated situation, the required action is: Create a supported private consumer endpoint and point clients at the private service name. The governing reason is: NCC producer connectivity alone does not reconfigure a consumer's DNS or application endpoint. C:VPC routing alone does not allow ingress traffic that the effective firewall policy denies. That is relevant to a different intervention. For the stated situation, the required action is: Create a supported private consumer endpoint and point clients at the private service name. The governing reason is: NCC producer connectivity alone does not reconfigure a consumer's DNS or application endpoint.
Question 328A security team configures a policy-based route to send traffic through a firewall appliance but the return direction follows an unrelated path. After this change — Verify supported bidirectional routing and stateful appliance insertion for the targeted flows. — which observation would best demonstrate that it worked? Test packets from the regulated workload traverse inspection and unrelated service packets keep normal routing. A full transaction completes through authorized inspection in both directions. Approved administrators connect while unrelated networks cannot reach the control-plane endpoint. A route-view correction restores the intended prefix and the application transaction succeeds. ExplanationCorrect Answer B:A full transaction completes through authorized inspection in both directions. The observation verifies the stated change. Stateful network inspection requires coherent paths for request and response traffic. It also helps prevent this exposure: Asymmetric routing can drop return packets and disrupt working services. Incorrect Answers A:Traffic insertion criteria must not capture unrelated workloads merely because they share a subnet. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A full transaction completes through authorized inspection in both directions. C:Restricting control-plane reachability is independent of whether worker nodes are private. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A full transaction completes through authorized inspection in both directions. D:Spoke health and destination-specific connectivity are separate states. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A full transaction completes through authorized inspection in both directions.
Question 329A support engineer sees an NCC spoke marked active and concludes that a missing service route must be a firewall issue. After this change — Inspect NCC propagated routes, spoke association and range filters before changing firewall rules. — which observation would best demonstrate that it worked? A test from one branch to another follows only the designated hub-controlled path. Cluster creation completes in the service project without broad host project ownership. A route-view correction restores the intended prefix and the application transaction succeeds. The deployment succeeds in its service project while unrelated host subnets remain inaccessible. ExplanationCorrect Answer C:A route-view correction restores the intended prefix and the application transaction succeeds. That test checks the affected service boundary directly. Inspect NCC propagated routes, spoke association and range filters before changing firewall rules. Without it, premature firewall relaxation can leave the actual routing fault intact and reduce protection. Incorrect Answers A:Star and mesh designs have different connectivity and isolation behaviors. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A route-view correction restores the intended prefix and the application transaction succeeds. B:GKE cluster provisioning across projects requires explicit host-network authorization. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A route-view correction restores the intended prefix and the application transaction succeeds. D:Workload creation and permission to use shared subnet resources are separately enforced by IAM. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A route-view correction restores the intended prefix and the application transaction succeeds.
Question 330A mobile game requires session affinity but its new backend service was created without an affinity mode compatible with its workload. After this change — Configure supported backend session affinity and verify its scaling tradeoffs. — which observation would best demonstrate that it worked? Measured requests distribute approximately to the authorized stable and canary weights. Repeated test requests for one session reach the expected backend until its health changes. Only properly authenticated edge-to-origin requests reach the private upstream service. External resolvers consistently return the new authorized record set after propagation. ExplanationCorrect Answer B:Repeated test requests for one session reach the expected backend until its health changes. The measured result matches the intended correction rather than a dashboard-only status. Backend affinity is an explicit load-balancer behavior, not a guaranteed property of every HTTP request. Incorrect Answers A:Layer-seven traffic splitting can control rollout exposure independently of application DNS. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Repeated test requests for one session reach the expected backend until its health changes. C: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: Repeated test requests for one session reach the expected backend until its health changes. D:Creating a DNS zone does not transfer internet authority until delegation is changed. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Repeated test requests for one session reach the expected backend until its health changes.