Question 710An engineer creates a Cloud Router BGP session but assigns a link-local address outside the planned peering subnet. After this change — Use the supported link-local peering address pair on the correct attachment or VPN interface. — which observation would best demonstrate that it worked? Both sides reach their peering IPs and the BGP session transitions to established. The partner learns only intended prefixes and a denied subnet remains unreachable. A path audit identifies the active supported encryption for the required segments. Both endpoints exchange the target application flow without selector-mismatch logs. ExplanationCorrect Answer A:Both sides reach their peering IPs and the BGP session transitions to established. The relevant control is operating as intended. BGP control-plane transport must have valid directly reachable neighbor addresses. An unresolved issue would mean: Invalid peering addresses can leave the physical connection carrying no routes. Incorrect Answers B:BGP advertisement scope should follow actual ownership and route policy rather than convenience summaries. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Both sides reach their peering IPs and the BGP session transitions to established. C:Dedicated network transport is not automatically an authenticated encrypted data channel. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Both sides reach their peering IPs and the BGP session transitions to established. D:An established security association does not prove the intended destination subnet is usable. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: Both sides reach their peering IPs and the BGP session transitions to established.
Question 711A cloud network connects two VPCs using independent Classic VPN gateways while the requirement demands automatic managed failover. Which Google Cloud networking change should the engineer make first? Complete the supported redundant VPN tunnel and interface pairing over the Interconnect topology. Evaluate a supported HA VPN design and configure redundant tunnels and dynamic routing if appropriate. Configure explicit supported custom-learned route controls with an approved route policy. Design resilient router-appliance capacity and validated routing failover across independent instances. ExplanationCorrect Answer B:Evaluate a supported HA VPN design and configure redundant tunnels and dynamic routing if appropriate. Classic and HA VPN differ in available availability and routing behavior. The evidence to require before closing the incident is: A controlled gateway-interface failure preserves the authorized cross-VPC application path. Incorrect Answers A:Encrypting a hybrid interconnect can introduce its own tunnel-level redundancy dependencies. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate a supported HA VPN design and configure redundant tunnels and dynamic routing if appropriate. The governing reason is: Classic and HA VPN differ in available availability and routing behavior. C:Custom learned routes change route visibility but must remain constrained to verified destinations. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate a supported HA VPN design and configure redundant tunnels and dynamic routing if appropriate. The governing reason is: Classic and HA VPN differ in available availability and routing behavior. D:High availability requires appliance placement and health beyond a logical hub configuration. That is relevant to a different intervention. For the stated situation, the required action is: Evaluate a supported HA VPN design and configure redundant tunnels and dynamic routing if appropriate. The governing reason is: Classic and HA VPN differ in available availability and routing behavior.
Question 712A project deploys a regional firewall policy but its organization requires the same control across all production regions. The team proposes: Use an appropriately scoped global or hierarchical Cloud NGFW policy for the shared control. Which networking principle explains why this change is appropriate? Volumetric and application-layer attacks require correctly placed controls at different layers. Mirrored packets carry potentially sensitive payloads and require a separately controlled observation path. Policy scope determines which regions and networks inherit an enforcement requirement. Cloud NAT performs translation; it does not replace application-aware web proxy controls. ExplanationCorrect Answer C:Policy scope determines which regions and networks inherit an enforcement requirement. That is why the proposed change is suitable: Use an appropriately scoped global or hierarchical Cloud NGFW policy for the shared control. A direct check is: Tests in two separate regions produce the same intended deny verdict. Incorrect Answers A:Volumetric and application-layer attacks require correctly placed controls at different layers. This does not establish the proposed intervention. The governing principle here is: Policy scope determines which regions and networks inherit an enforcement requirement. Apply it by: Use an appropriately scoped global or hierarchical Cloud NGFW policy for the shared control. B:Mirrored packets carry potentially sensitive payloads and require a separately controlled observation path. This does not establish the proposed intervention. The governing principle here is: Policy scope determines which regions and networks inherit an enforcement requirement. Apply it by: Use an appropriately scoped global or hierarchical Cloud NGFW policy for the shared control. 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: Policy scope determines which regions and networks inherit an enforcement requirement. Apply it by: Use an appropriately scoped global or hierarchical Cloud NGFW policy for the shared control.
Question 713An e-commerce client sees intermittent resets only during a backend rollout but health checks remain green. Which Google Cloud networking change should the engineer make first? Use Firewall Insights and flow logs for rule-level verdicts while treating topology as an aggregate traffic view. Inspect load-balancer connection draining, rollout pace and backend session behavior. Enable suitable Cloud VPN logs and correlate negotiation failures with tunnel metrics. Correlate Network Topology paths, Performance Dashboard and load-balancer metrics for the affected service. ExplanationCorrect Answer B:Inspect load-balancer connection draining, rollout pace and backend session behavior. This addresses the underlying network dependency. Health checks do not necessarily prove connection continuity during planned backend changes. Confirm the change by checking: A staged backend drain preserves active sessions across the deployment. Incorrect Answers A:Topology visualization and packet-level firewall diagnostics answer different questions. That is relevant to a different intervention. For the stated situation, the required action is: Inspect load-balancer connection draining, rollout pace and backend session behavior. The governing reason is: Health checks do not necessarily prove connection continuity during planned backend changes. C:A tunnel-up percentage alone cannot explain negotiation errors or peer configuration drift. That is relevant to a different intervention. For the stated situation, the required action is: Inspect load-balancer connection draining, rollout pace and backend session behavior. The governing reason is: Health checks do not necessarily prove connection continuity during planned backend changes. D:Observed network latency can include routing, load-balancing and endpoint contributions. That is relevant to a different intervention. For the stated situation, the required action is: Inspect load-balancer connection draining, rollout pace and backend session behavior. The governing reason is: Health checks do not necessarily prove connection continuity during planned backend changes.
Question 714A firewall team configures an egress rule but mistakenly sets ingress direction and the application still reaches a forbidden internet endpoint. After this change — Correct the rule direction and match criteria under the actual effective policy order. — which observation would best demonstrate that it worked? Only the authorized GKE workload identity establishes the test connection. A controlled suspicious flow creates an observable event at the approved integration endpoint. The prohibited outbound connection is blocked and the approved egress path remains usable. A safe SQL-injection test receives the expected policy verdict on the active storefront. ExplanationCorrect Answer C:The prohibited outbound connection is blocked and the approved egress path remains usable. The measured result matches the intended correction rather than a dashboard-only status. Ingress and egress are different policy enforcement directions and cannot be used interchangeably. Incorrect Answers A:Cloud network microsegmentation requires target selectors that actually represent the running workload. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The prohibited outbound connection is blocked and the approved egress path remains usable. B:Out-of-band security integration is a detection workflow distinct from the traffic-forwarding data plane. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The prohibited outbound connection is blocked and the approved egress path remains usable. D:WAF configuration has no effect unless the intended load-balancer edge or backend enforcement point uses it. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The prohibited outbound connection is blocked and the approved egress path remains usable.
Question 715A cloud network connects two VPCs using independent Classic VPN gateways while the requirement demands automatic managed failover. The team proposes: Evaluate a supported HA VPN design and configure redundant tunnels and dynamic routing if appropriate. Which networking principle explains why this change is appropriate? Classic and HA VPN differ in available availability and routing behavior. BFD can accelerate failure detection when peers support compatible session parameters. Partner Interconnect provisioning differs by whether the provider terminates Layer 2 or Layer 3 routing. Hybrid network transit depends on explicitly supported spoke types and topology configuration. ExplanationCorrect Answer A:Classic and HA VPN differ in available availability and routing behavior. The distinction connects the symptoms to the proposed engineering work. Evaluate a supported HA VPN design and configure redundant tunnels and dynamic routing if appropriate. Evidence: A controlled gateway-interface failure preserves the authorized cross-VPC application path. Incorrect Answers B:BFD can accelerate failure detection when peers support compatible session parameters. This does not establish the proposed intervention. The governing principle here is: Classic and HA VPN differ in available availability and routing behavior. Apply it by: Evaluate a supported HA VPN design and configure redundant tunnels and dynamic routing if appropriate. C:Partner Interconnect provisioning differs by whether the provider terminates Layer 2 or Layer 3 routing. This does not establish the proposed intervention. The governing principle here is: Classic and HA VPN differ in available availability and routing behavior. Apply it by: Evaluate a supported HA VPN design and configure redundant tunnels and dynamic routing if appropriate. D:Hybrid network transit depends on explicitly supported spoke types and topology configuration. This does not establish the proposed intervention. The governing principle here is: Classic and HA VPN differ in available availability and routing behavior. Apply it by: Evaluate a supported HA VPN design and configure redundant tunnels and dynamic routing if appropriate.
Question 716An internal Application Load Balancer serves only regional clients but the application must now be reached from authorized remote regions. After this change — Enable the supported global access capability or choose an appropriate global internal design. — which observation would best demonstrate that it worked? An approved cross-region client reaches the service without opening an internet path. A test request arrives at the legacy backend with the intended rewritten path. A validating resolver accepts genuine records and rejects a deliberately invalid signature. A two-user test never receives another user's personalized API payload. ExplanationCorrect Answer A:An approved cross-region client reaches the service without opening an internet path. The evidence tests the actual dependency: Regional internal load-balancer reachability is not automatically universal across every network location. An uncorrected condition risks: Missing global access behavior can strand legitimate internal users. Incorrect Answers B:HTTP path transformations are proxy-level functions that must match the chosen load-balancer class. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An approved cross-region client reaches the service without opening an internet path. 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 approved cross-region client reaches the service without opening an internet path. D:Shared edge caching must honor response sensitivity and cacheability rules. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: An approved cross-region client reaches the service without opening an internet path.
Question 717A company combines Cloud NGFW and third-party appliances but assumes a single service-level firewall permit also enforces appliance inspection. What is the most direct consequence of leaving the problem uncorrected? Legacy selectors can fail open or block legitimate modern workloads. A routing bypass can avoid external inspection despite an apparent permit policy. Uncontrolled mirroring can leak protected network content. Missing egress translation can silently prevent security patch downloads. ExplanationCorrect Answer B:A routing bypass can avoid external inspection despite an apparent permit policy. The preventable impact is tied to this traffic or trust boundary. Design supported traffic insertion and document both firewall and network appliance control points. Verify: A test flow is permitted only when it traverses both required enforcement points. Incorrect Answers A:Cloud network microsegmentation requires target selectors that actually represent the running workload. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A routing bypass can avoid external inspection despite an apparent permit policy. C:Mirrored packets carry potentially sensitive payloads and require a separately controlled observation path. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A routing bypass can avoid external inspection despite an apparent permit policy. D:Private instances need explicit translation or proxy connectivity for outbound internet service access. That does not describe the principal exposure from the stated failure. The direct avoidable risk is: A routing bypass can avoid external inspection despite an apparent permit policy.
Question 718A company writes a VPC ingress allow rule for an application but a higher-priority hierarchical deny policy still blocks it. After this change — Inspect the effective hierarchical firewall rule order and narrow the authorized exception at the appropriate level. — which observation would best demonstrate that it worked? A pre/post test matrix yields the same intended decisions for approved and disallowed workloads. The effective-policy trace identifies the intended allowed or denied application flow. A concurrency test maintains expected external connections without port-allocation drops. Approved clients continue to access the app while a controlled disallowed request is blocked. ExplanationCorrect Answer B:The effective-policy trace identifies the intended allowed or denied application flow. The relevant control is operating as intended. Higher-level firewall policies can supersede local VPC rules under their evaluation semantics. An unresolved issue would mean: Ignoring inherited policy can trigger repeated ineffective local firewall changes. Incorrect Answers A:Network firewall migrations must preserve actual effective authorization rather than just rule names. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The effective-policy trace identifies the intended allowed or denied application flow. C:Outbound NAT connection scale depends on available ports and address allocation behavior. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The effective-policy trace identifies the intended allowed or denied application flow. D:Priority and match scoping decide which HTTP requests experience a security rule. This relates to a separate check and does not verify the specified repair. The relevant acceptance evidence is: The effective-policy trace identifies the intended allowed or denied application flow.
Question 719A hybrid operator uses an NCC router appliance as a redundant transit device but deploys only one VM instance in one zone. Which Google Cloud networking change should the engineer make first? Align the supported traffic selectors and routing configuration with the actual protected prefixes. Reconcile attachment capacity settings and approved utilization against the actual traffic forecast. Design resilient router-appliance capacity and validated routing failover across independent instances. Use the supported link-local peering address pair on the correct attachment or VPN interface. ExplanationCorrect Answer C:Design resilient router-appliance capacity and validated routing failover across independent instances. High availability requires appliance placement and health beyond a logical hub configuration. The evidence to require before closing the incident is: Removing one router appliance does not interrupt permitted intersite connectivity. Incorrect Answers A:An established security association does not prove the intended destination subnet is usable. That is relevant to a different intervention. For the stated situation, the required action is: Design resilient router-appliance capacity and validated routing failover across independent instances. The governing reason is: High availability requires appliance placement and health beyond a logical hub configuration. B: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: Design resilient router-appliance capacity and validated routing failover across independent instances. The governing reason is: High availability requires appliance placement and health beyond a logical hub configuration. D:BGP control-plane transport must have valid directly reachable neighbor addresses. That is relevant to a different intervention. For the stated situation, the required action is: Design resilient router-appliance capacity and validated routing failover across independent instances. The governing reason is: High availability requires appliance placement and health beyond a logical hub configuration.
Question 720A global application uses a simple DNS A record but must direct customers toward geographically appropriate healthy regions. The team proposes: Choose an applicable Cloud DNS geolocation or failover routing policy with health evidence. Which networking principle explains why this change is appropriate? Proxy and passthrough load balancers differ in how client connections and addresses are handled. DNS response policies can direct clients based on location and health, within DNS caching limits. Shared edge caching must honor response sensitivity and cacheability rules. Backend affinity is an explicit load-balancer behavior, not a guaranteed property of every HTTP request. ExplanationCorrect Answer B:DNS response policies can direct clients based on location and health, within DNS caching limits. That is why the proposed change is suitable: Choose an applicable Cloud DNS geolocation or failover routing policy with health evidence. A direct check is: Regional clients receive the intended answers and a failing target is excluded after evaluation. Incorrect Answers A: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: DNS response policies can direct clients based on location and health, within DNS caching limits. Apply it by: Choose an applicable Cloud DNS geolocation or failover routing policy with health evidence. C:Shared edge caching must honor response sensitivity and cacheability rules. This does not establish the proposed intervention. The governing principle here is: DNS response policies can direct clients based on location and health, within DNS caching limits. Apply it by: Choose an applicable Cloud DNS geolocation or failover routing policy with health evidence. 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: DNS response policies can direct clients based on location and health, within DNS caching limits. Apply it by: Choose an applicable Cloud DNS geolocation or failover routing policy with health evidence.