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 enterprise manages multiple Shared VPC networks across several folders in Google Cloud and is migrating from legacy VPC firewall rules to Cloud Next Generation Firewall (Cloud NGFW) policies. Your security architecture requires:
Which firewall configuration should you implement?
This option uses Cloud NGFW Essentials features—an organization-level hierarchical firewall policy, a global network firewall policy, and secure tags—but misconfigures both the hierarchical rule actions and the network firewall policy enforcement order.
allow rules instead of goto_next in an organization-level hierarchical firewall policy immediately permits matching traffic and stops all subsequent firewall evaluation. As a result, lower-level folder policies, global network firewall policies, and secure tag rules are completely bypassed for that traffic.AFTER_CLASSIC_FIREWALL setting causes Cloud NGFW to evaluate legacy VPC firewall rules before global network firewall policies. During migration, any matching legacy VPC rule (allow or deny) will execute and halt evaluation before the new global network firewall policy is ever reached.AFTER_CLASSIC_FIREWALL evaluation sequence: Cloud NGFW evaluates hierarchical firewall policies, then regional system firewall policies, then VPC firewall rules, and only then global and regional network firewall policies.allow, deny, and apply_security_profile_group are terminal actions that stop further rule matching, whereas goto_next explicitly delegates evaluation to the next policy tier.AFTER_CLASSIC_FIREWALL prevents newly authored tag-based rules from overriding permissive legacy rules until those legacy rules are deleted.You wanted legacy VPC firewall rules to continue overriding new global network firewall policies during migration, and you intended organization-level allow rules to permanently bypass all project-level firewall controls.
This architecture combines Cloud NGFW Essentials capabilities—hierarchical firewall policies, global network firewall policies, secure tags, address groups, and stateful Layer 3 and Layer 4 inspection—without enabling any paid Cloud NGFW Standard or Cloud NGFW Enterprise rule attributes. Because Cloud NGFW billing is determined dynamically by the features referenced in matching rules rather than a separate tier subscription, restricting rules to Essentials attributes keeps data-processing charges for higher tiers at zero.
BEFORE_CLASSIC_FIREWALL evaluates global and regional network firewall policies ahead of legacy VPC firewall rules.0 to 2,147,483,547), support batch updates, and measure quota by rule attribute complexity.By pairing CIDR-based hierarchical firewall policies (since hierarchical policies do not support tags) with tag-based global network firewall policies under BEFORE_CLASSIC_FIREWALL ordering, you achieve centralized governance, zero-trust micro-segmentation, smooth migration precedence, and zero Standard or Enterprise tier fees.
This approach attempts to combine regional network firewall policies with the apply_security_profile_group action for inspection while delegating organization-wide baseline enforcement to VPC firewall rules using network tags.
apply_security_profile_group action is only supported in hierarchical firewall policies and global network firewall policies; it cannot be used in regional network firewall policies or regional system firewall policies.apply_security_profile_group to a firewall endpoint invokes Cloud NGFW Enterprise Layer 7 deep packet inspection (such as IPS, URL filtering, or malware sandboxing), incurring both hourly firewall endpoint charges and per-gigabyte inspection charges.allow, deny, goto_next).You needed zonal Cloud NGFW Enterprise Layer 7 threat prevention (using global network firewall policies rather than regional policies) and did not require immutable organization-wide guardrails or zero tier fees.
This option establishes the correct policy hierarchy and BEFORE_CLASSIC_FIREWALL evaluation order, and it appropriately uses secure tags for micro-segmentation. However, it introduces FQDN objects and Google Threat Intelligence lists into the global network firewall policy rules.
The organization had budget approval for Cloud NGFW Standard north-south traffic processing and specifically needed domain-name filtering or Google-maintained threat actor IP blocklists instead of static address groups and CIDR ranges.
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