Question 790
A Zero Trust architecture review has identified: A GCP organization uses several VPCs and needs centralized security for shared services without disrupting native route constraints. Which discovery step would support a defensible decision?
Explanation
Correct Answer
Investigating review Google Cloud topology, supported NGFW insertion options and regional load balancer behavior directly addresses the architecture concern: A GCP organization uses several VPCs and needs centralized security for shared services without disrupting native route constraints. If supported by the evidence, the target design would design supported GCP firewall insertion and routing with explicit service-region resilience. A later proof of effectiveness is that test services pass through intended inspection and remain available after a zone event.
Incorrect Answers
The option applies in “an Azure hub-and-spoke environment routes internet egress around NGFWs because subnet user-defined routes are missing”. The technical acceptance test is: controlled spoke internet traffic is inspected and return paths are consistent. That evidence does not directly establish “Review Google Cloud topology, supported NGFW insertion options and regional load balancer behavior” for the scenario at hand.
This choice targets the separate scenario “an AWS application spans many VPCs and requires centralized east-west traffic inspection without manual per-instance firewall rules”. A later proof of effectiveness is that pilot VPC traffic traverses inspection symmetrically and permitted applications retain availability. The more relevant answer here is “Review Google Cloud topology, supported NGFW insertion options and regional load balancer behavior”.
The distinct use case for this response is “A customer hosts private apps in OCI with tight latency SLOs but designs egress inspection using unsupported cloud-specific appliance assumptions”. The technical acceptance test is: oCI app traffic is inspected on documented paths while latency and failure targets are met. The present case instead calls for “Review Google Cloud topology, supported NGFW insertion options and regional load balancer behavior”.