Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization runs Java workloads across multiple isolated VPC networks in separate Google Cloud projects. You must enforce centralized internet egress control without peering the workload VPCs to a central security VPC.
Your solution must meet these requirements:
https.proxyHost and https.proxyPort).Which Secure Web Proxy deployment model and policy configuration should you implement?
HTTPS via.prod.securegateway.goog:443 in a public Cloud Storage bucket, enforce the PAC URL through the Google Admin console, and configure an authorization policy on the gateway.A Proxy Auto-Configuration (PAC) file (pac_config.js) containing a FindProxyForURL function pointing to HTTPS via.prod.securegateway.goog:443 is the legacy client-routing mechanism for Chrome Enterprise Premium Security Gateway. It is designed to route corporate Chrome browser traffic to external SaaS applications for Zero Trust access evaluation.
via.prod.securegateway.goog:443 is the endpoint for Chrome Enterprise Premium Security Gateway, not a VPC-hosted Secure Web Proxy instance in your host project.https.proxyHost/https.proxyPort properties or a gRPC ProxyDetector, rather than browser-enforced PAC scripts.Cache-Control header must be set to no-cache so browsers fetch updated routing rules.roles/beyondcorp.serviceDiscoveryUser) to replace legacy PAC files.The requirement were to secure corporate end-user Chrome browser access to SaaS applications using a legacy Chrome Enterprise Premium Security Gateway setup prior to migrating to Service Discovery.
Always distinguish user-to-SaaS browser proxies (Chrome Enterprise Premium Security Gateway) from workload-to-internet VPC egress proxies (Secure Web Proxy with explicit proxy, PSC service attachment, or next hop mode).
Next hop mode configures Google Cloud VPC routing so that outbound traffic is automatically steered to a Secure Web Proxy (SWP) instance without configuring explicit proxy settings on individual workloads. A gateway security policy is a primary SWP policy model designed for standard web egress control using service accounts, secure tags, destination hostnames, and ports.
https.proxyHost and https.proxyPort.The workloads resided in a single VPC (or peered architecture), explicit client proxy configuration were prohibited, and access control relied on secure tags or service accounts via a gateway security policy instead of frontend mTLS.
When workloads require frontend mTLS for strong cryptographic client verification, Certificate Manager stores the trust anchors and intermediate CAs, while an authorization policy enforces identity-based egress rules.
Private Service Connect (PSC) service attachment mode exposes a centrally managed Secure Web Proxy (SWP) instance in a security VPC to isolated consumer VPCs without VPC Network Peering. Pairing it with an authorization policy enables cryptographic frontend mTLS identity verification and granular outbound access control.
https.proxyHost and https.proxyPort (or a gRPC ProxyDetector) to target the local PSC endpoint IP, establishing TLS-encrypted proxy tunnels directly to the central SWP./23 proxy-only subnet (--purpose=REGIONAL_MANAGED_PROXY) ensures scalable IP allocation for outbound NAT and proxy connections.Compared to next hop mode (which requires VPC routing/peering) or Chrome Enterprise Premium PAC files (built for browser-to-SaaS access), PSC service attachment mode with an authorization policy is the only architecture that centralizes SWP in a host project, avoids peering, supports explicit Java proxy clients, and enforces frontend mTLS with service rate limiting.
Explicit proxy routing mode directs clients to send HTTP(S) CONNECT or web requests straight to a Secure Web Proxy (SWP) endpoint configured in the workload environment. However, attempting to deploy SWP inside service projects and attach two primary policy types violates core SWP architectural constraints.
--purpose=PRIVATE) and a proxy-only subnet (--purpose=REGIONAL_MANAGED_PROXY, recommended /23).No single-host centralization were required, each VPC were in an independent standalone project (not a service project), and each gateway attached only an authorization policy plus a service rate limiting policy.
To centralize SWP in one host project while serving isolated VPCs without peering, Private Service Connect (PSC) service attachments provide scalable cross-VPC and cross-project consumption.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated