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 is deploying Cloud Next Generation Firewall (Cloud NGFW) Enterprise across multiple projects with VPC networks configured with an 8,896-byte MTU and workloads in us-central1-a and us-central1-b. You must meet these requirements:
Host headers for internet-bound wildcard domain filtering (*.example.com).Which configuration should you implement?
THREAT_PREVENTION (with a Critical-severity override set to ALERT) and URL_FILTERING security profiles inside an organization-level security profile group. Keep each VPC MTU at 8,896 bytes, deploy organization-level firewall endpoints with jumbo frame support in both zones without TLS inspection, and reference FQDN objects with *.example.com and the security profile group in a hierarchical firewall policy integrated with Security Command Center.This configuration places organization-level security profiles in a hierarchical firewall policy and deploys endpoints in both zones, but leaves the VPC MTU at 8,896 bytes, omits TLS inspection, applies a Critical-severity override, and relies on FQDN objects for wildcard domain filtering.
Host headers remain unread: Without a TLS inspection policy, Cloud NGFW cannot decrypt HTTPS message headers and relies solely on the plaintext Server Name Indication (SNI) sent during clientHello, failing the requirement to inspect encrypted HTTP Host headers.ALERT stops blocking for every Critical-severity threat signature rather than isolating the single false-positive signature ID.THREAT_PREVENTION profiles, signature overrides take precedence over severity overrides and are designed for single-signature exceptions.Using FQDN objects without TLS inspection would be appropriate if the organization only needed Cloud NGFW Standard-tier IP-based domain filtering and did not require Layer 7 IPS or HTTP header inspection—and if IPS were enabled, the VPC MTU would still have to be reduced to 8,500 bytes or less.
apply_security_profile_group action pointing to an organization-level security profile group with a signature ID override. Set each VPC MTU to 1,500 bytes, deploy firewall endpoints without jumbo frame support in both zones without TLS inspection, and configure Cloud IDS with Packet Mirroring to block threats inline and forward findings to Security Command Center and Google SecOps.This configuration attempts to invoke Cloud NGFW Enterprise features from traditional VPC firewall rules, pairs non-jumbo firewall endpoints with a 1,500-byte VPC MTU, omits TLS inspection, and relies on Cloud IDS for inline threat blocking.
apply_security_profile_group—and Cloud NGFW Standard features like Google Threat Intelligence are only available through firewall policies (hierarchical or global network firewall policies), not legacy VPC firewall rules.Host header inspection: Omitting TLS inspection prevents Cloud NGFW from decrypting HTTPS headers to evaluate the HTTP Host header.Deploying Cloud IDS with Packet Mirroring would be appropriate when you need out-of-band intrusion detection and visibility into intra-subnet VM-to-VM traffic without altering traffic paths, rather than inline prevention and hierarchical URL filtering.
THREAT_PREVENTION and URL_FILTERING security profiles in a central security project and attach them to a regional network firewall policy with Google Threat Intelligence rules. Deploy one firewall endpoint with jumbo frame support in us-central1-a, lower each VPC MTU to 8,500 bytes, attach a TLS inspection policy, and enable Cloud Armor Adaptive Protection to stream findings to Security Command Center.This configuration attempts to centralize Layer 7 threat inspection using project-level security profiles, a regional network firewall policy, a single zonal firewall endpoint, and Google Cloud Armor Adaptive Protection.
us-central1-a leaves workloads in us-central1-b completely uninspected, and firewall rules targeting 0.0.0.0/0 will simply allow traffic in zones lacking an attached endpoint.Using project-level security profiles with a global (rather than regional) network firewall policy would be appropriate when managing application-specific Layer 7 inspection within a single project or across projects without an organization-wide hierarchical firewall policy, provided firewall endpoints exist in every active workload zone.
THREAT_PREVENTION (with a signature ID override set to ALLOW) and URL_FILTERING security profiles inside one organization-level security profile group. Lower each VPC MTU to 8,500 bytes, deploy organization-level firewall endpoints with jumbo frame support in us-central1-a and us-central1-b with a TLS inspection policy, reference the group in a hierarchical firewall policy alongside Google Threat Intelligence rules using 0.0.0.0/0 and INTERNET context, and integrate findings with Security Command Center and Google SecOps.Cloud Next Generation Firewall (Cloud NGFW) Enterprise provides distributed Layer 7 deep packet inspection—including intrusion detection and prevention (IPS), URL filtering, and TLS inspection—using Google-managed zonal firewall endpoints, security profiles, and security profile groups.
THREAT_PREVENTION and URL_FILTERING security profiles inside an organization-level security profile group enables a single hierarchical firewall policy to enforce both services across all projects and VPCs. Firewall policies can combine Google Threat Intelligence (Standard tier) rules with Enterprise apply_security_profile_group rules in the same policy.us-central1-a and us-central1-b ensures no zone bypasses Layer 7 inspection. Lowering the VPC MTU from 8,896 bytes to 8,500 bytes keeps packets within the endpoint's maximum supported limit so IPS inspection runs reliably.Host header alongside SNI. Setting the rule destination to 0.0.0.0/0 with the INTERNET network context enables Layer 7 wildcard domain matching (*.example.com) strictly for internet-bound traffic.ALLOW in the THREAT_PREVENTION profile suppresses the single false positive because signature overrides take precedence over severity overrides, leaving all other Critical-severity protections intact.This is the only configuration that respects every Cloud NGFW architectural boundary: organization-level resource scoping for hierarchical policies, complete zonal endpoint placement, strict VPC MTU alignment (8,500 bytes), TLS header decryption for wildcard URL inspection, signature-level exception precedence, and native SIEM/posture integration.
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