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 migrating legacy VPC firewall rules to Cloud Next Generation Firewall (Cloud NGFW) Enterprise tier for a multi-tier application. Your current VPC firewall configuration includes:
1000 (one allow and one deny) targeting web VMs via network tagsallow rule permitting traffic from a source service account (web-sa) to a target service account (app-sa)During migration, you must preserve existing traffic behavior while enabling stateful Layer 7 threat prevention (anti-spyware and vulnerability protection) on traffic reaching the application tier.
How should you map these VPC firewall rule constructs to Cloud NGFW policy constructs?
web-sa as the ingress source service account, apply apply_security_profile_group, and add matching egress rules because Cloud NGFW policies evaluate traffic statelessly.This design leverages a hierarchical firewall policy for Layer 7 inspection while attempting to retain legacy network tags, source service accounts, and manual return-traffic egress rules under the assumption that NGFW policies are stateless.
web-sa).allow or apply_security_profile_group) matches a new connection, Cloud NGFW records a connection tracking table entry that automatically permits and inspects return egress traffic.apply_security_profile_group for Layer 7 inspection.RDMA_ROCE_POLICY), not regular VPC networks.You replaced legacy network tags and web-sa with secure tags, omitted redundant return-traffic egress rules (relying on Cloud NGFW stateful connection tracking), and resolved duplicate rule priorities.
Engineers sometimes confuse regular VPC Cloud NGFW policies with RoCE VPC firewall policies. While RoCE policies are stateless and ingress-only, regular VPC Cloud NGFW policies maintain full stateful connection tracking across both L3/L4 filtering and L7 packet interception.
1000 for conflicting rules so deny takes precedence, preserve web-sa as the ingress source service account, and use apply_security_profile_group for Layer 7 threat inspection.This configuration attempts to translate VPC firewall rule behaviors directly into a regional network firewall policy without accounting for key structural differences in Cloud NGFW policy rules, priority constraints, and Layer 7 inspection support.
0 to 2,147,483,547) within a policy. You cannot assign priority 1000 to two rules in the same policy.apply_security_profile_group action used to intercept traffic for Cloud NGFW Enterprise threat prevention cannot be used in regional network firewall policies or regional system firewall policies.allow, deny, and goto_next).0) evaluates first and stops evaluation on match (unless goto_next is used).You were using a global network firewall policy (or hierarchical policy) with unique priorities (deny assigned a lower integer than allow), replaced web-sa with a secure tag as the source, and applied apply_security_profile_group in that global policy.
A common misconception during migration is assuming regional network firewall policies support all Enterprise features. In Cloud NGFW, Layer 7 security profiles (apply_security_profile_group) are restricted to global network firewall policies and hierarchical firewall policies.
deny rule a lower integer than the allow rule, map network tags and web-sa to IAM-governed secure tags, and use apply_security_profile_group referencing a threat-prevention security profile group.A global network firewall policy is a Cloud NGFW container resource that consolidates stateful Layer 3/Layer 4 filtering and Cloud NGFW Enterprise Layer 7 deep packet inspection into a single, IAM-governed policy applied across all regions of associated VPC networks.
0 to 2,147,483,547), resolving the duplicate priority 1000 rules by assigning a lower integer (higher priority) to the deny rule preserves the original VPC behavior where deny overrides allow at the same priority.web-sa and legacy network tags to IAM-governed secure tags provides zero-trust, identity-aware source and target matching. (Target service accounts like app-sa can either remain as target service accounts or also be migrated to secure tags.)apply_security_profile_group transparently intercepts matched application-tier connections to a zonal firewall endpoint using a threat-prevention security profile, scanning for anti-spyware, vulnerability protection, and antivirus signatures while creating a stateful connection tracking table entry so return traffic is also inspected.This mapping accurately translates every legacy VPC construct into its native Cloud NGFW equivalent while unlocking Enterprise Layer 7 threat prevention—capabilities unavailable in VPC firewall rules or regional network firewall policies.
65535, map network tags to secure tags, configure the allow rule to also invoke goto_next, and chain traffic into a regional network firewall policy for apply_security_profile_group inspection.This approach assumes that firewall policy rules use the VPC firewall priority ceiling (65535), that a single rule can combine allow with goto_next, and that a regional network firewall policy can execute Layer 7 threat inspection.
allow action immediately permits the connection and stops evaluating all subsequent rules; it cannot be combined with goto_next to chain evaluation into another policy.goto_next rule, regional policies do not support the apply_security_profile_group action.65535 reflects legacy VPC firewall rule limits rather than the expanded Cloud NGFW policy range of 0 to 2,147,483,547.allow, deny, goto_next, or apply_security_profile_group.apply_security_profile_group matches traffic in a global or hierarchical policy, it intercepts the packets to a firewall endpoint and stops further rule evaluation—the security profile itself decides whether to allow or drop packets.allow and then pass traffic to a lower-level policy for additional Layer 7 inspection.The apply_security_profile_group action were configured directly within the global network firewall policy (without allow + goto_next chaining) and source service accounts were explicitly mapped to secure tags.
Understanding how allow, goto_next, and apply_security_profile_group terminate or continue evaluation is critical when migrating rules. Only goto_next delegates evaluation downstream, while apply_security_profile_group replaces allow for inspected flows.
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