Question 300A payments team selects an internal passthrough balancer for a browser application that requires TLS termination and URL routing. After this change — Choose the appropriate internal Application Load Balancer and specify its HTTP routing behavior. — which observation would best demonstrate that it worked? Load tests show authorized private calls succeed at target concurrency without connector saturation. Requests for separate URL paths reach the intended healthy backends over approved TLS policy. A Pod-to-datacenter test reaches only the approved target without ambiguous routes. The approved on-premises client resolves and reaches the designated API privately. ExplanationCorrect Answer B:Requests for separate URL paths reach the intended healthy backends over approved TLS policy. The evidence tests the actual dependency: Layer-seven request routing and proxy termination require a compatible application load-balancing class. An uncorrected condition risks: The wrong balancer class prevents application routing requirements from being met. Incorrect Answers A:Serverless private network attachment has deployment, scaling, and regional constraints beyond firewall permission. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Requests for separate URL paths reach the intended healthy backends over approved TLS policy. C:Pod ranges participate in real network reachability and must not conflict with hybrid destination prefixes. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Requests for separate URL paths reach the intended healthy backends over approved TLS policy. D:Private API access depends on DNS, eligible service endpoints and network routing together. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Requests for separate URL paths reach the intended healthy backends over approved TLS policy.
Question 301A canary release has no way to send 5 percent of traffic to a new build without changing clients. The team proposes: Use the supported Application Load Balancer URL-map weighted backend service behavior. Which networking principle explains why this change is appropriate? Creating a DNS zone does not transfer internet authority until delegation is changed. An external object origin needs explicit frontend, origin and caching configuration. Layer-seven traffic splitting can control rollout exposure independently of application DNS. An external CDN origin has distinct network and trust assumptions from a Google-managed backend. ExplanationCorrect Answer C:Layer-seven traffic splitting can control rollout exposure independently of application DNS. Under these conditions, the remedy follows from the principle: Use the supported Application Load Balancer URL-map weighted backend service behavior. Confirm: Measured requests distribute approximately to the authorized stable and canary weights. Incorrect Answers A:Creating a DNS zone does not transfer internet authority until delegation is changed. This does not establish the proposed intervention. The governing principle here is: Layer-seven traffic splitting can control rollout exposure independently of application DNS. Apply it by: Use the supported Application Load Balancer URL-map weighted backend service behavior. B:An external object origin needs explicit frontend, origin and caching configuration. This does not establish the proposed intervention. The governing principle here is: Layer-seven traffic splitting can control rollout exposure independently of application DNS. Apply it by: Use the supported Application Load Balancer URL-map weighted backend service behavior. D: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: Layer-seven traffic splitting can control rollout exposure independently of application DNS. Apply it by: Use the supported Application Load Balancer URL-map weighted backend service behavior.
Question 302A paid media API uses unsigned Cloud CDN links that anyone can forward to bypass access controls. The team proposes: Configure signed URLs or another appropriate access control for protected content delivery. Which networking principle explains why this change is appropriate? CDN caching alone does not authenticate requests for restricted media. GKE Gateway and Ingress controllers have distinct resource contracts and provisioning requirements. Automated DNS record management should operate at the least practical privilege. Hybrid private DNS requires a reachable inbound resolver path and correct forwarding rules. ExplanationCorrect Answer A:CDN caching alone does not authenticate requests for restricted media. The network behavior in the question follows this rule. Configure signed URLs or another appropriate access control for protected content delivery. Check success by observing: An authorized signed request succeeds while an expired or altered signature is rejected. Incorrect Answers B:GKE Gateway and Ingress controllers have distinct resource contracts and provisioning requirements. This does not establish the proposed intervention. The governing principle here is: CDN caching alone does not authenticate requests for restricted media. Apply it by: Configure signed URLs or another appropriate access control for protected content delivery. C:Automated DNS record management should operate at the least practical privilege. This does not establish the proposed intervention. The governing principle here is: CDN caching alone does not authenticate requests for restricted media. Apply it by: Configure signed URLs or another appropriate access control for protected content delivery. D:Hybrid private DNS requires a reachable inbound resolver path and correct forwarding rules. This does not establish the proposed intervention. The governing principle here is: CDN caching alone does not authenticate requests for restricted media. Apply it by: Configure signed URLs or another appropriate access control for protected content delivery.
Question 303A financial institution chooses Cloud VPN for steady multi-gigabit transfer without testing tunnel throughput limits. After this change — Estimate sustained bandwidth and select appropriately sized Interconnect capacity with redundant connections. — which observation would best demonstrate that it worked? A two-cloud traceroute and route table show unique reachable destination prefixes. Preflight quota checks cover intended regional endpoints and a staged scale deployment succeeds. A simulated appliance failure preserves inspected flow reachability through the remaining approved instance. An end-to-end bulk transfer reaches the target rate without saturated tunnel paths. ExplanationCorrect Answer D:An end-to-end bulk transfer reaches the target rate without saturated tunnel paths. The result directly exercises the remedy: Estimate sustained bandwidth and select appropriately sized Interconnect capacity with redundant connections. It reduces the risk that insufficient hybrid capacity can delay settlements and backlog replication. Incorrect Answers A:Cross-cloud routing cannot reliably distinguish destinations when overlapping prefixes are exchanged. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An end-to-end bulk transfer reaches the target rate without saturated tunnel paths. B:Cloud architecture scale requires resource quota capacity as well as routable IP address space. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An end-to-end bulk transfer reaches the target rate without saturated tunnel paths. C:Inspection insertion must maintain both routing intent and a healthy appliance failure domain. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An end-to-end bulk transfer reaches the target rate without saturated tunnel paths.
Question 304A monitoring system reports a service region is slow but the operator only checks individual VM ping latency. Which Google Cloud networking change should the engineer make first? Correlate Network Topology paths, Performance Dashboard and load-balancer metrics for the affected service. Compare effective firewall policies, tags and service-account identities for both VMs. Enable Cloud NAT allocation and error metrics with meaningful alert thresholds. Enable the appropriate subnet flow logging and correlate it with firewall and service logs. ExplanationCorrect Answer A:Correlate Network Topology paths, Performance Dashboard and load-balancer metrics for the affected service. Observed network latency can include routing, load-balancing and endpoint contributions. The relevant acceptance test is concrete: A controlled request trace identifies the slow path component under representative traffic. Incorrect Answers B:Same-subnet placement does not imply equivalent firewall targeting or identity policy. That is relevant to a different intervention. For the stated situation, the required action is: Correlate Network Topology paths, Performance Dashboard and load-balancer metrics for the affected service. The governing reason is: Observed network latency can include routing, load-balancing and endpoint contributions. C:Source-port exhaustion is a network translation capacity problem independent of guest CPU load. That is relevant to a different intervention. For the stated situation, the required action is: Correlate Network Topology paths, Performance Dashboard and load-balancer metrics for the affected service. The governing reason is: Observed network latency can include routing, load-balancing and endpoint contributions. D:Packet-flow visibility depends on data collection at the actual source or destination subnet. That is relevant to a different intervention. For the stated situation, the required action is: Correlate Network Topology paths, Performance Dashboard and load-balancer metrics for the affected service. The governing reason is: Observed network latency can include routing, load-balancing and endpoint contributions.
Question 305A team exposes an internal-only service through a public Application Load Balancer and then tries to fix privacy using an URL rule. After this change — Move the service to an appropriate internal load-balancing frontend with access controls. — which observation would best demonstrate that it worked? The app is reachable from approved VPC clients but not the public internet. Healthy instances appear in the serving pool and an unhealthy instance is excluded. A validating resolver accepts genuine records and rejects a deliberately invalid signature. Requests from separate regions return the current approved logo version. ExplanationCorrect Answer A:The app is reachable from approved VPC clients but not the public internet. That test checks the affected service boundary directly. Move the service to an appropriate internal load-balancing frontend with access controls. Without it, a public listener can expose an application even when URLs appear obscure. Incorrect Answers B:Load balancing requires an observable backend health state before distributing live requests. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The app is reachable from approved VPC clients but not the public internet. 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: The app is reachable from approved VPC clients but not the public internet. D:An origin update does not instantly replace every cached object at distributed edges. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The app is reachable from approved VPC clients but not the public internet.
Question 306A platform operator assumes enabling GKE Dataplane V2 automatically imports every existing legacy NetworkPolicy rule unchanged. What is the most direct consequence of leaving the problem uncorrected? Unexpected per-node reservations can exhaust the secondary range. Undetected transit drift can impact many networks at once. Unexpected policy semantics can create outages or lateral network exposure. Healthy instances may be marked unavailable because probing traffic is denied. ExplanationCorrect Answer C:Unexpected policy semantics can create outages or lateral network exposure. This is the most immediate service or security consequence. Dataplane implementation choices require policy compatibility and enforcement verification. Test the correction by verifying: Approved Pod traffic passes and disallowed cross-namespace traffic is rejected in a controlled test. Incorrect Answers A:Per-node alias-IP allocation consumes address space beyond the current number of running Pods. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unexpected policy semantics can create outages or lateral network exposure. B:Centralized network scaling requires visibility into effective propagation and filter decisions. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unexpected policy semantics can create outages or lateral network exposure. D:VPC routing alone does not allow ingress traffic that the effective firewall policy denies. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Unexpected policy semantics can create outages or lateral network exposure.
Question 307A Kubernetes group deploys private nodes but grants the cluster control plane a public endpoint open to all source networks. The team proposes: Choose a private or appropriately restricted control-plane endpoint with approved administrator access. Which networking principle explains why this change is appropriate? Private address conservation is a multi-environment capacity and overlap-planning problem. Managed-service private connectivity is service-dependent and not the same as internet routing. Private managed-service endpoints have service-specific attachment and transitivity constraints. Private node addressing and control-plane exposure are independent design controls. ExplanationCorrect Answer D:Private node addressing and control-plane exposure are independent design controls. The distinction connects the symptoms to the proposed engineering work. Choose a private or appropriately restricted control-plane endpoint with approved administrator access. Evidence: A trusted admin reaches the endpoint and unauthorized internet probes cannot reach it. Incorrect Answers A:Private address conservation is a multi-environment capacity and overlap-planning problem. This does not establish the proposed intervention. The governing principle here is: Private node addressing and control-plane exposure are independent design controls. Apply it by: Choose a private or appropriately restricted control-plane endpoint with approved administrator access. B:Managed-service private connectivity is service-dependent and not the same as internet routing. This does not establish the proposed intervention. The governing principle here is: Private node addressing and control-plane exposure are independent design controls. Apply it by: Choose a private or appropriately restricted control-plane endpoint with approved administrator access. C:Private managed-service endpoints have service-specific attachment and transitivity constraints. This does not establish the proposed intervention. The governing principle here is: Private node addressing and control-plane exposure are independent design controls. Apply it by: Choose a private or appropriately restricted control-plane endpoint with approved administrator access.
Question 308A private VM attempts to reach a Google-managed service using its documented public hostname but an incorrect custom DNS override resolves to a private unused address. After this change — Remove the unsupported DNS override and configure the appropriate service endpoint resolution. — which observation would best demonstrate that it worked? Authorized health probes reach the service while requests from an unapproved source remain blocked. The managed API hostname resolves correctly and the private VM completes an authorized request. Approved Pod traffic passes and disallowed cross-namespace traffic is rejected in a controlled test. Route diagnostics in two regions select the intended preferred and fallback attachment. ExplanationCorrect Answer B:The managed API hostname resolves correctly and the private VM completes an authorized request. The evidence tests the actual dependency: Private service access depends on supported DNS names and reachable endpoints, not arbitrary address rewrites. An uncorrected condition risks: Incorrect DNS overrides can silently direct cloud API calls to dead endpoints. Incorrect Answers A: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: The managed API hostname resolves correctly and the private VM completes an authorized request. C:Dataplane implementation choices require policy compatibility and enforcement verification. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The managed API hostname resolves correctly and the private VM completes an authorized request. D:Dynamic route propagation mode changes visibility and best-route evaluation across Google Cloud regions. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The managed API hostname resolves correctly and the private VM completes an authorized request.
Question 309A cluster uses the Gateway controller but its service backends lack the required network endpoint group readiness and health-check behavior. Which Google Cloud networking change should the engineer make first? Validate supported Service, Gateway and NEG configuration and allow health check traffic. Apply the route-selection tag consistently through its instance template. Configure the supported PSC propagation design and inspect consumer endpoint reachability. Validate the intended subnet routes and effective firewall policies at both peered ends. ExplanationCorrect Answer A:Validate supported Service, Gateway and NEG configuration and allow health check traffic. GKE load-balancer endpoints must become healthy and discoverable before external traffic can be served. Its operational proof is: Gateway routes lead to healthy Pods with an authorized response from a synthetic client. The avoidable impact is: Incorrect endpoint readiness can take healthy Pods out of service. Incorrect Answers B:Tag-based routing eligibility depends on actual instance metadata, not an operator's intention. That is relevant to a different intervention. For the stated situation, the required action is: Validate supported Service, Gateway and NEG configuration and allow health check traffic. The governing reason is: GKE load-balancer endpoints must become healthy and discoverable before external traffic can be served. C:Managed producer connectivity and ordinary VPC route propagation are distinct mechanisms. That is relevant to a different intervention. For the stated situation, the required action is: Validate supported Service, Gateway and NEG configuration and allow health check traffic. The governing reason is: GKE load-balancer endpoints must become healthy and discoverable before external traffic can be served. D:Peering route exchange does not override each VPC's security enforcement. That is relevant to a different intervention. For the stated situation, the required action is: Validate supported Service, Gateway and NEG configuration and allow health check traffic. The governing reason is: GKE load-balancer endpoints must become healthy and discoverable before external traffic can be served.
Question 310A reviewer sees hundreds of firewall log records and uses a raw count to conclude that one denied service is under attack. Which Google Cloud networking change should the engineer make first? Segment logs by action, service identity, source and rate before evaluating the security signal. Monitor attachment-specific errors and utilization separately from physical circuit status. Inspect effective VPC dynamic routes, BGP attributes and next hops for the actual destination. Inspect BGP advertisements, route policies and dynamic route visibility in the destination region. ExplanationCorrect Answer A:Segment logs by action, service identity, source and rate before evaluating the security signal. This step targets the failure path itself. Firewall event counts require traffic context to distinguish normal policy enforcement from threat activity. Observe: The analyzed rule data identifies the real source and affected service without suppressing valid alerts. Incorrect Answers B:A healthy transport circuit can conceal congestion or faults at the virtual attachment layer. That is relevant to a different intervention. For the stated situation, the required action is: Segment logs by action, service identity, source and rate before evaluating the security signal. The governing reason is: Firewall event counts require traffic context to distinguish normal policy enforcement from threat activity. C:An application response can succeed even when the traffic uses an expensive or unsafe route. That is relevant to a different intervention. For the stated situation, the required action is: Segment logs by action, service identity, source and rate before evaluating the security signal. The governing reason is: Firewall event counts require traffic context to distinguish normal policy enforcement from threat activity. D:A live BGP session is necessary but not sufficient for learning a specific destination route. That is relevant to a different intervention. For the stated situation, the required action is: Segment logs by action, service identity, source and rate before evaluating the security signal. The governing reason is: Firewall event counts require traffic context to distinguish normal policy enforcement from threat activity.