Pass Google Professional Cloud Network Engineer Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Google Professional Cloud Network Engineer Practice Test 79
Question 780
At fictional Elmcrest Services, the observed incident is: An enterprise mandates authenticated outbound web filtering but an application reaches the internet over a permitted direct path that avoids its Secure Web Proxy policies. The diagnostic finding is: Network routes and access logs show outbound HTTPS connections without corresponding proxy identity or policy evaluation records. Which action AND separate measurable verification best address this case?
Explanation
Correct Answer
Secure Web Proxy controls outbound web access only when workloads actually route requests through the enforced proxy path. The action is to use a supported Secure Web Proxy integration and enforce appropriate egress constraints for the workload environment; the independent test is that approved destinations traverse the authorized web proxy and a prohibited endpoint request is rejected and logged.
Incorrect Answers
Action: Recalculate NAT port capacity and revise supported address assignments and endpoint allocation for the measured concurrency. Independent proof: The stress test completes representative public API calls without source-port exhaustion and audit logs show stable NAT behavior. It misses the relevant dependency because secure Web Proxy controls outbound web access only when workloads actually route requests through the enforced proxy path. Instead verify that approved destinations traverse the authorized web proxy and a prohibited endpoint request is rejected and logged.
The proposed pair addresses Action: Evaluate supported dynamic port allocation, per-endpoint minimum and maximum port settings, and destination patterns before changing capacity. Independent proof: A realistic burst completes outbound requests while the NAT logs record no allocation starvation at planned fleet scale. Here network routes and access logs show outbound HTTPS connections without corresponding proxy identity or policy evaluation records. The bounded response is use a supported Secure Web Proxy integration and enforce appropriate egress constraints for the workload environment with proof that approved destinations traverse the authorized web proxy and a prohibited endpoint request is rejected and logged.
The alternative action and test—Action: Review supported rate-limit keys, thresholds, preview behavior and user-based alternatives to distinguish abusive from legitimate demand. Independent proof: Load tests admit intended user activity while a controlled abusive request pattern still reaches the documented limit—would measure a different issue. This case requires use a supported Secure Web Proxy integration and enforce appropriate egress constraints for the workload environment and confirmation that approved destinations traverse the authorized web proxy and a prohibited endpoint request is rejected and logged.
Question 781
At fictional Eastpoint Health, the cloud network security engineering team protects workloads and outbound web access. A Google Cloud network issue is reported: A pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. The decisive observation is: Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Which scoped engineering response is most appropriate?
Explanation
Correct Answer
Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing. The case-specific correction is to design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology. Preserve this constraint during the change: Load-balancer availability alone cannot guarantee state synchronization or asymmetric-session support of every appliance.
Incorrect Answers
Another possible response is to configure supported Cloud IDS attachment and Packet Mirroring coverage for the intended traffic sources and confirm privacy requirements. The case evidence instead shows that packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
Review the applicable hierarchy and obtain an approved scoped exception or redesign the authorized access path. This does not address the reported incident: a pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. The case-specific correction is to design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology.
One alternative would be to recalculate NAT port capacity and revise supported address assignments and endpoint allocation for the measured concurrency. The observed evidence instead shows that packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. The more relevant correction is to design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology.
Question 782
The cloud network security engineering team at fictional Eastpoint Health investigates: A pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. Which particular observation would most directly distinguish the network cause before changing production resources?
Explanation
Correct Answer
Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. That observation distinguishes the reported incident because stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing. The appropriate response is to design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology.
Incorrect Answers
Deployment inventory shows key workload subnet traffic does not reach any configured mirroring source or inspected endpoint. It does not account for the observation packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance in the reported situation.
One proposed finding is cloud NAT telemetry indicates port allocation errors and the configured manual NAT address pool is smaller than planned simultaneous connection demand. This would indicate another failure; here packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
The alternative observation, policy inspection shows the expected secure tag binding is missing while the VM has only a network tag with a similar string, concerns a different dependency. This incident is distinguished by packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
Question 783
In fictional Eastpoint Health, operators encountered: A pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. Evidence: Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. They propose: Design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology. Which independent result best confirms the change works?
Explanation
Correct Answer
Verify the change by checking that a new connection and its return packets use the required inspection path and controlled failover behaves as documented. The original clue was packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. The test is meaningful because stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
Incorrect Answers
Even verifying a controlled supported detection test yields expected inspection telemetry while excluded unrelated networks remain outside scope leaves the reported failure unproven. An acceptance test must show that a new connection and its return packets use the required inspection path and controlled failover behaves as documented.
The alternative outcome is a controlled attack simulation is mitigated and known good application requests remain serviceable. It may validate a separate setting, but not the required action: design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology. The required observation is a new connection and its return packets use the required inspection path and controlled failover behaves as documented.
The tagged workload follows the expected access policy and a similarly named unbound network tag provides no accidental privilege. The evidence relevant to this incident is packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Confirm the corresponding recovery result: A new connection and its return packets use the required inspection path and controlled failover behaves as documented.
Question 784
At fictional Eastpoint Health, the cloud network security engineering team reviews: A pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. Evidence: Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Which Google Cloud networking design principle best explains the required correction?
Explanation
Correct Answer
The underlying rule is that stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing. Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. A suitable correction is to design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology.
Incorrect Answers
Network intrusion detection depends on correct traffic visibility and supported mirror/inspection topology, not just a provisioned service. The decisive observation, packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance, requires a different explanation: Stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
A different principle is: public Cloud NAT enables outbound address translation but is bounded by source-port and per-endpoint allocation limits. The causal link actually supported by packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance is stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
Network firewall capabilities depend on enabled service tier and its underlying inspection integration. However, it does not explain packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. The applicable principle is that stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
Question 785
At fictional Eastpoint Health, the observed incident is: A pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. The diagnostic finding is: Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Which action AND separate measurable verification best address this case?
Explanation
Correct Answer
The underlying clue is packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Correct it by design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology and confirm that a new connection and its return packets use the required inspection path and controlled failover behaves as documented.
Incorrect Answers
Action: Configure supported Cloud IDS attachment and Packet Mirroring coverage for the intended traffic sources and confirm privacy requirements. Independent proof: A controlled supported detection test yields expected inspection telemetry while excluded unrelated networks remain outside scope. The pair does not resolve the observed packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Use design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology and verify a new connection and its return packets use the required inspection path and controlled failover behaves as documented.
The alternate plan combines Action: Evaluate supported Cloud Armor Adaptive Protection and DDoS response rules with staged enforcement and preserved legitimate access. Independent proof: A controlled attack simulation is mitigated and known good application requests remain serviceable. The identified fault is packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Closing it requires a new connection and its return packets use the required inspection path and controlled failover behaves as documented.
The alternative proposal is Action: Evaluate supported dynamic port allocation, per-endpoint minimum and maximum port settings, and destination patterns before changing capacity. Independent proof: A realistic burst completes outbound requests while the NAT logs record no allocation starvation at planned fleet scale. It does not address the current evidence: packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. The appropriate action is design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology.
Question 786
At fictional Asterline Telecom, the security perimeter architecture group reviews Cloud Armor, firewall policies and inspection topology. A Google Cloud network issue is reported: A pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. The decisive observation is: Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Which scoped engineering response is most appropriate?
Explanation
Correct Answer
A pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. The clue packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance supports the bounded action: Design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology. Confirm that a new connection and its return packets use the required inspection path and controlled failover behaves as documented. Preserve this constraint during the change: Load-balancer availability alone cannot guarantee state synchronization or asymmetric-session support of every appliance.
Incorrect Answers
Configure supported Cloud IDS attachment and Packet Mirroring coverage for the intended traffic sources and confirm privacy requirements. It could be useful for another problem, but it does not change packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. The response needs to design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology.
An alternative action is review the applicable hierarchy and obtain an approved scoped exception or redesign the authorized access path. This incident instead involves packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Confirm the scoped change through a new connection and its return packets use the required inspection path and controlled failover behaves as documented.
Review supported rate-limit keys, thresholds, preview behavior and user-based alternatives to distinguish abusive from legitimate demand. That would not correct the reported packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. The supported response is to design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology.
Question 787
The security perimeter architecture group at fictional Asterline Telecom investigates: A pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. Which particular observation would most directly distinguish the network cause before changing production resources?
Explanation
Correct Answer
Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing. This finding supports the targeted response: Design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology.
Incorrect Answers
Deployment inventory shows key workload subnet traffic does not reach any configured mirroring source or inspected endpoint. That finding does not isolate the reported issue: a pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. The determining evidence is packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance.
That alternative instead describes security action logs show many valid sessions from a shared egress address exceeding an overly broad rate-key threshold. The actual diagnostic record shows packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance instead. The difference matters because stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
Even if service entitlement and policy configuration show only lower-tier capabilities, without supported Enterprise layer-7 inspection configuration, it would not establish the cause here. Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. The case-specific correction is to design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology.
Question 788
In fictional Asterline Telecom, operators encountered: A pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. Evidence: Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. They propose: Design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology. Which independent result best confirms the change works?
Explanation
Correct Answer
A new connection and its return packets use the required inspection path and controlled failover behaves as documented. This measures whether the response corrected packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance rather than merely completing a configuration step.
Incorrect Answers
A test that a controlled supported detection test yields expected inspection telemetry while excluded unrelated networks remain outside scope would not demonstrate closure of this condition. The needed proof is a new connection and its return packets use the required inspection path and controlled failover behaves as documented.
A controlled attack simulation is mitigated and known good application requests remain serviceable. That does not demonstrate the case-specific success condition: a new connection and its return packets use the required inspection path and controlled failover behaves as documented. Stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
A realistic burst completes outbound requests while the NAT logs record no allocation starvation at planned fleet scale. That result does not test the original problem, identified by packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Recovery must show that a new connection and its return packets use the required inspection path and controlled failover behaves as documented.
Question 789
At fictional Asterline Telecom, the security perimeter architecture group reviews: A pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. Evidence: Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Which Google Cloud networking design principle best explains the required correction?
Explanation
Correct Answer
Stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing. The reported symptom arises where packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Address it through design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology.
Incorrect Answers
A proposed explanation is network intrusion detection depends on correct traffic visibility and supported mirror/inspection topology, not just a provisioned service. The present evidence is packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance, which instead follows from stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
Cloud Armor edge and backend enforcement stages have distinct capabilities and should match the risk being addressed. This describes another relationship, not the cause of a pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. Stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
The rule public Cloud NAT enables outbound address translation but is bounded by source-port and per-endpoint allocation limits does not account for packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. This case is governed by stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
Question 790
At fictional Asterline Telecom, the observed incident is: A pair of third-party firewall appliances is placed behind an internal next-hop load balancer and application flows intermittently fail on the return path. The diagnostic finding is: Packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. Which action AND separate measurable verification best address this case?
Explanation
Correct Answer
Design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology. Validation requires a new connection and its return packets use the required inspection path and controlled failover behaves as documented rather than relying on a successful configuration save. Stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing.
Incorrect Answers
Action: Configure supported Cloud IDS attachment and Packet Mirroring coverage for the intended traffic sources and confirm privacy requirements. Independent proof: A controlled supported detection test yields expected inspection telemetry while excluded unrelated networks remain outside scope. It misses the relevant dependency because stateful network appliance insertion needs coherent forward-and-return paths alongside healthy next-hop routing. Instead verify that a new connection and its return packets use the required inspection path and controlled failover behaves as documented.
The proposed pair addresses Action: Evaluate supported dynamic port allocation, per-endpoint minimum and maximum port settings, and destination patterns before changing capacity. Independent proof: A realistic burst completes outbound requests while the NAT logs record no allocation starvation at planned fleet scale. Here packet traces show forward packets crossing one inspection appliance and reverse packets returning through a different stateful instance. The bounded response is design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology with proof that a new connection and its return packets use the required inspection path and controlled failover behaves as documented.
The alternative action and test—Action: Use a supported Secure Web Proxy integration and enforce appropriate egress constraints for the workload environment. Independent proof: Approved destinations traverse the authorized web proxy and a prohibited endpoint request is rejected and logged—would measure a different issue. This case requires design supported symmetric packet forwarding and load-balancer appliance health/affinity behavior for the approved inspection topology and confirmation that a new connection and its return packets use the required inspection path and controlled failover behaves as documented.
Professional Cloud Network Engineer Practice Tests
- Google Professional Cloud Network Engineer Practice Test 77 - 10 Questions (Last Reviewed 31-Oct-2026)
- Google Professional Cloud Network Engineer Practice Test 78 - 10 Questions (Last Reviewed 30-Oct-2026)
- Google Professional Cloud Network Engineer Practice Test 79 - 10 Questions (Last Reviewed 29-Oct-2026)
- Google Professional Cloud Network Engineer Practice Test 80 - 10 Questions (Last Reviewed 28-Oct-2026)
