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.
Question 311A network team connects Cloud Router appliances to NCC but leaves their VM interfaces attached to the wrong subnets. The team proposes: Place router appliance interfaces on the intended networks and validate the supported BGP attachment. Which networking principle explains why this change is appropriate? BGP session security requires compatible credentials at both ends of the neighbor relationship. Cloud VPN IKE negotiation requires the actual current reachable peer identity. Router appliances need real VPC interface connectivity before they can exchange hybrid routes. Hybrid availability requires working route convergence in addition to redundant physical links. ExplanationCorrect Answer C:Router appliances need real VPC interface connectivity before they can exchange hybrid routes. The proposed change addresses the correct subsystem. Place router appliance interfaces on the intended networks and validate the supported BGP attachment. The observable proof is: The appliance peers establish and approved remote prefixes become reachable. Incorrect Answers A:BGP session security requires compatible credentials at both ends of the neighbor relationship. This does not establish the proposed intervention. The governing principle here is: Router appliances need real VPC interface connectivity before they can exchange hybrid routes. Apply it by: Place router appliance interfaces on the intended networks and validate the supported BGP attachment. B:Cloud VPN IKE negotiation requires the actual current reachable peer identity. This does not establish the proposed intervention. The governing principle here is: Router appliances need real VPC interface connectivity before they can exchange hybrid routes. Apply it by: Place router appliance interfaces on the intended networks and validate the supported BGP attachment. D:Hybrid availability requires working route convergence in addition to redundant physical links. This does not establish the proposed intervention. The governing principle here is: Router appliances need real VPC interface connectivity before they can exchange hybrid routes. Apply it by: Place router appliance interfaces on the intended networks and validate the supported BGP attachment.
Question 312A software firm enables DNSSEC signing but omits the necessary delegation signer record at the parent zone. After this change — Complete supported DNSSEC DS delegation and validate chain-of-trust responses. — which observation would best demonstrate that it worked? The controller creates its authorized service record but cannot alter unrelated zones. The backend log shows the required approved client source behavior on test TCP flows. Requests from separate regions return the current approved logo version. A validating resolver accepts genuine records and rejects a deliberately invalid signature. ExplanationCorrect Answer D:A validating resolver accepts genuine records and rejects a deliberately invalid signature. The observation verifies the stated change. DNSSEC validation relies on consistent child signing and parent delegation information. It also helps prevent this exposure: Broken DNSSEC delegation can make the domain inaccessible to validating clients. Incorrect Answers A:Automated DNS record management should operate at the least practical privilege. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A validating resolver accepts genuine records and rejects a deliberately invalid signature. B:Proxy and passthrough load balancers differ in how client connections and addresses are handled. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A validating resolver accepts genuine records and rejects a deliberately invalid signature. C: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: A validating resolver accepts genuine records and rejects a deliberately invalid signature.
Question 313A SaaS provider migrates an authoritative public zone to Cloud DNS but forgets to update registrar name servers. Which Google Cloud networking change should the engineer make first? Coordinate authoritative record import and delegation cutover at the domain registrar. Restrict or disable traffic mirroring and use a sanitized test target under approved controls. Version release URLs and apply cache lifetimes that support security update propagation. Select a supported passthrough load-balancing architecture and review backend source visibility. ExplanationCorrect Answer A:Coordinate authoritative record import and delegation cutover at the domain registrar. This addresses the underlying network dependency. Creating a DNS zone does not transfer internet authority until delegation is changed. Confirm the change by checking: External resolvers consistently return the new authorized record set after propagation. Incorrect Answers B:Mirroring duplicates application traffic and therefore inherits the original request's data handling obligations. That is relevant to a different intervention. For the stated situation, the required action is: Coordinate authoritative record import and delegation cutover at the domain registrar. The governing reason is: Creating a DNS zone does not transfer internet authority until delegation is changed. C: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: Coordinate authoritative record import and delegation cutover at the domain registrar. The governing reason is: Creating a DNS zone does not transfer internet authority until delegation is changed. D:Proxy and passthrough load balancers differ in how client connections and addresses are handled. That is relevant to a different intervention. For the stated situation, the required action is: Coordinate authoritative record import and delegation cutover at the domain registrar. The governing reason is: Creating a DNS zone does not transfer internet authority until delegation is changed.
Question 314An application uses a managed database through a public endpoint even though its architecture mandates private producer access. After this change — Plan the correct private services access or Private Service Connect design for the specific managed offering. — which observation would best demonstrate that it worked? Internal hospital names resolve from cloud VMs and retain the intended private answers. A dry-run expansion confirms the required range capacity and future secondary range plan. A test client reaches the intended service privately without an unintended public path. An end-to-end bulk transfer reaches the target rate without saturated tunnel paths. ExplanationCorrect Answer C:A test client reaches the intended service privately without an unintended public path. The measured result matches the intended correction rather than a dashboard-only status. Managed-service private connectivity is service-dependent and not the same as internet routing. Incorrect Answers A:A hybrid namespace needs an explicit recursive resolution path across the cloud and datacenter boundary. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test client reaches the intended service privately without an unintended public path. B:Cluster scalability is bounded by usable Pod CIDRs and ranges independently of node count. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test client reaches the intended service privately without an unintended public path. D:Connectivity selection depends on throughput, availability and security constraints, not only tunnel setup ease. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: A test client reaches the intended service privately without an unintended public path.
Question 315A cluster uses the Gateway controller but its service backends lack the required network endpoint group readiness and health-check behavior. After this change — Validate supported Service, Gateway and NEG configuration and allow health check traffic. — which observation would best demonstrate that it worked? Cluster creation completes in the service project without broad host project ownership. A staged rollout shows expected spokes and destination paths without warning events. Gateway routes lead to healthy Pods with an authorized response from a synthetic client. The pipeline deploys an approved VM using the selected shared subnet without host-project ownership. ExplanationCorrect Answer C:Gateway routes lead to healthy Pods with an authorized response from a synthetic client. This verifies the live traffic or policy outcome. Validate supported Service, Gateway and NEG configuration and allow health check traffic. Otherwise, incorrect endpoint readiness can take healthy Pods out of service. Incorrect Answers A: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: Gateway routes lead to healthy Pods with an authorized response from a synthetic client. B:Centralized network scaling requires visibility into effective propagation and filter decisions. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Gateway routes lead to healthy Pods with an authorized response from a synthetic client. D:Service project automation must authenticate to both its workload project and permitted host network resources. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Gateway routes lead to healthy Pods with an authorized response from a synthetic client.
Question 316A newly provisioned Cloud VPN gateway shows no traffic but engineers investigate VM firewalls before examining tunnel phase state. What is the most direct consequence of leaving the problem uncorrected? Rollout-time connection resets can lead to lost customer orders. Changing unrelated firewall rules can add risk without repairing the broken transport. Unclear scope can lead to needless application changes. Unobserved BGP flapping can cause prolonged intermittent hybrid outages. ExplanationCorrect Answer B:Changing unrelated firewall rules can add risk without repairing the broken transport. The failure can produce the stated harm even when other components appear healthy. Application reachability depends on a working tunnel and routes before higher-layer firewall decisions. Remedy: Verify VPN negotiation and route availability before changing workload security policy. Incorrect Answers A:Health checks do not necessarily prove connection continuity during planned backend changes. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Changing unrelated firewall rules can add risk without repairing the broken transport. C:End-to-end latency symptoms require distinguishing infrastructure trends from application or client effects. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Changing unrelated firewall rules can add risk without repairing the broken transport. D:Routing session availability needs timely control-plane monitoring beyond periodic manual inspection. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Changing unrelated firewall rules can add risk without repairing the broken transport.
Question 317A documentation site moves a Cloud Run service behind Cloud CDN but its backend service is not configured to reach the serverless origin. The team proposes: Use a supported serverless network endpoint group and compatible external HTTP frontend. Which networking principle explains why this change is appropriate? Serverless CDN integration requires the correct backend and ingress design. Private DNS visibility depends on authorized network association, not merely organization ownership. Proxy and passthrough load balancers differ in how client connections and addresses are handled. Backend affinity is an explicit load-balancer behavior, not a guaranteed property of every HTTP request. ExplanationCorrect Answer A:Serverless CDN integration requires the correct backend and ingress design. Under these conditions, the remedy follows from the principle: Use a supported serverless network endpoint group and compatible external HTTP frontend. Confirm: A cached page reaches the Cloud Run origin on a miss and later generates cache hits. Incorrect Answers B:Private DNS visibility depends on authorized network association, not merely organization ownership. This does not establish the proposed intervention. The governing principle here is: Serverless CDN integration requires the correct backend and ingress design. Apply it by: Use a supported serverless network endpoint group and compatible external HTTP frontend. C:Proxy and passthrough load balancers differ in how client connections and addresses are handled. This does not establish the proposed intervention. The governing principle here is: Serverless CDN integration requires the correct backend and ingress design. Apply it by: Use a supported serverless network endpoint group and compatible external HTTP frontend. D:Backend affinity is an explicit load-balancer behavior, not a guaranteed property of every HTTP request. This does not establish the proposed intervention. The governing principle here is: Serverless CDN integration requires the correct backend and ingress design. Apply it by: Use a supported serverless network endpoint group and compatible external HTTP frontend.
Question 318A Kubernetes platform deploys external-dns against Cloud DNS but grants it broad organization-wide DNS administration. What is the most direct consequence of leaving the problem uncorrected? Old delegation can leave users on retired endpoints even after migration. Overbroad DNS automation privileges can redirect unrelated production names. Long-lived unversioned binaries can leave users downloading vulnerable releases. A dormant failover pool can leave a nominally redundant service unavailable. ExplanationCorrect Answer B:Overbroad DNS automation privileges can redirect unrelated production names. The scenario identifies the cause of this exposure. Automated DNS record management should operate at the least practical privilege. An appropriate control is: Restrict its service identity to the specific zone and record-change permissions required. Incorrect Answers A:Creating a DNS zone does not transfer internet authority until delegation is changed. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Overbroad DNS automation privileges can redirect unrelated production names. C:Cache immutability should align with an object's versioning and security update requirements. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Overbroad DNS automation privileges can redirect unrelated production names. D:Backend selection uses observed serving health, not simply a VM power state. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: Overbroad DNS automation privileges can redirect unrelated production names.
Question 319A deployment creates a managed instance group backend but never configures health checks for a newly published load balancer. Which Google Cloud networking change should the engineer make first? Attach an appropriate health check and allow it to reach the backend service. Configure supported inbound DNS forwarding policies and on-premises resolver targets. Use a supported serverless network endpoint group and compatible external HTTP frontend. Restrict its service identity to the specific zone and record-change permissions required. ExplanationCorrect Answer A:Attach an appropriate health check and allow it to reach the backend service. Load balancing requires an observable backend health state before distributing live requests. The evidence to require before closing the incident is: Healthy instances appear in the serving pool and an unhealthy instance is excluded. Incorrect Answers B:Hybrid private DNS requires a reachable inbound resolver path and correct forwarding rules. That is relevant to a different intervention. For the stated situation, the required action is: Attach an appropriate health check and allow it to reach the backend service. The governing reason is: Load balancing requires an observable backend health state before distributing live requests. C:Serverless CDN integration requires the correct backend and ingress design. That is relevant to a different intervention. For the stated situation, the required action is: Attach an appropriate health check and allow it to reach the backend service. The governing reason is: Load balancing requires an observable backend health state before distributing live requests. D:Automated DNS record management should operate at the least practical privilege. That is relevant to a different intervention. For the stated situation, the required action is: Attach an appropriate health check and allow it to reach the backend service. The governing reason is: Load balancing requires an observable backend health state before distributing live requests.
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.