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 to perform Layer 7 intrusion detection and prevention and URL filtering across two projects (proj-app-a and proj-app-b) in the same organization. Both projects contain standalone VPC networks (vpc-a and vpc-b) with the following configuration:
us-central1-a and us-central1-b.How should you architect the firewall endpoints, associations, and firewall policy rules to intercept and inspect Layer 7 traffic?
us-central1-a, associate both vpc-a and vpc-b to this endpoint, create an organization-level security profile group, set both VPC networks to BEFORE_CLASSIC_FIREWALL enforcement order, and attach regional network firewall policies in us-central1 with apply_security_profile_group rules to each VPC.Regional network firewall policies group Layer 3 and Layer 4 firewall rules scoped to a single Google Cloud region within a project's VPC networks. Meanwhile, a firewall endpoint is a strictly zonal inspection resource designed to intercept and inspect traffic only for workloads located in that same zone.
allow, deny, and goto_next actions. They do not support the apply_security_profile_group action required to redirect traffic to a firewall endpoint.us-central1-b workloads unprotected: Because firewall endpoints are zonal rather than regional, a single endpoint in us-central1-a cannot inspect workloads running in us-central1-b. Traffic in us-central1-b will receive no Layer 7 inspection if no endpoint is associated in that zone.apply_security_profile_group action.apply_security_profile_group falls back to allow rather than inspecting traffic across zones.This approach would only work if all workloads in both VPC networks ran exclusively in us-central1-a and the rules were placed in global network firewall policies (or hierarchical firewall policies) instead of regional network firewall policies.
A common misconception is treating firewall endpoints as regional appliances because Cloud NGFW policies can be regional. In practice, Layer 7 interception always depends on zonal endpoint placement paired with global or hierarchical firewall policies.
us-central1-a and one in us-central1-b), create endpoint associations inside a centralized security billing project for both VPCs, configure an organization-level security profile group, leave both VPC networks at AFTER_CLASSIC_FIREWALL enforcement order, and attach global network firewall policies with apply_security_profile_group rules to each VPC.AFTER_CLASSIC_FIREWALL Order DoBy default, creating a firewall endpoint without jumbo frame support configures a maximum supported packet size of 1,460 bytes. Additionally, VPC networks using the AFTER_CLASSIC_FIREWALL enforcement order evaluate traditional VPC firewall rules before evaluating global and regional network firewall policies.
vpc-a and vpc-b use an MTU of 8,500 bytes, which exceeds the 1,460-byte limit of a non-jumbo-frame endpoint, the firewall endpoints will not perform threat prevention or URL filtering for those VPC networks.proj-app-a and proj-app-b), not in a separate security billing project.AFTER_CLASSIC_FIREWALL, existing VPC firewall allow rules match traffic first and immediately stop rule evaluation, preventing packets from ever reaching the global network firewall policy's apply_security_profile_group rule.allow or deny) matches a packet, Cloud NGFW halts evaluation and never proceeds to lower-precedence network firewall policies.This configuration would only be valid if the VPC networks used a standard 1,460-byte MTU, the associations were created inside proj-app-a and proj-app-b, there were no overlapping classic VPC allow rules, and the enforcement order was updated to BEFORE_CLASSIC_FIREWALL.
proj-app-a (one in us-central1-a and one in us-central1-b), associate both vpc-a and vpc-b with these endpoints, create a project-level security profile group in proj-app-a, and reference that security profile group using apply_security_profile_group rules inside an organization-level hierarchical firewall policy.Project-level firewall endpoints and project-level security profile groups allow project administrators to deploy Cloud NGFW Layer 7 inspection without organization-level endpoint permissions. Hierarchical firewall policies apply consistent firewall rules across an entire organization or folder hierarchy.
proj-app-a is unsupported.vpc-b to project-scoped resources inside proj-app-a undermines clean multi-project governance.This would be partially aligned if the team used organization-level endpoints and an organization-level security profile group, or if project teams used global network firewall policies (which can reference project-level security profile groups across projects) instead of a hierarchical firewall policy.
us-central1-a and one in us-central1-b), create project-level endpoint associations in both proj-app-a and proj-app-b for each zone, configure an organization-level security profile group, set both VPC networks to BEFORE_CLASSIC_FIREWALL enforcement order, and attach global network firewall policies with apply_security_profile_group rules to each VPC.Cloud NGFW Enterprise performs deep Layer 7 packet inspection by transparently redirecting matched VPC traffic to managed firewall endpoints using Google Cloud's packet intercept technology. Firewall endpoints are zonal inspection appliances that evaluate decrypted or cleartext application payloads against security profiles bundled inside a security profile group, without requiring changes to existing VPC routing tables.
us-central1-a and one in us-central1-b covers both vpc-a and vpc-b across all active workload zones while keeping inspection traffic strictly intra-zonal for lower latency and zero cross-zonal data transfer costs.proj-app-a and proj-app-b links each VPC network to the shared organization-level endpoints in the corresponding zones.apply_security_profile_group action.BEFORE_CLASSIC_FIREWALL ensures global network firewall policy rules are evaluated before legacy VPC firewall allow rules terminate evaluation.vpc-a and vpc-b.URL_FILTERING and THREAT_PREVENTION profiles in one security profile group evaluates domains and threat signatures in a single pass.This design uses the exact minimum number of endpoints required for zonal locality (two total rather than four), complies with project-level association ownership, supports jumbo frames, and guarantees apply_security_profile_group rules execute prior to classic VPC firewall rules.
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