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 (NGFW) Enterprise across multiple VPCs to enforce centralized Layer 7 inspection. The security team defines the following requirements:
12345 due to a known false positive.Which configuration meets these requirements?
This option places both THREAT_PREVENTION and URL_FILTERING profiles inside a project-level Security Profile Group and attempts to enforce it organization-wide via a hierarchical firewall policy rule set at the highest priority (0).
0): Placing a URL filtering rule at priority 0 intercepts traffic before standard Layer 3/Layer 4 allow or deny rules are evaluated, increasing the risk that the URL profile's default action drops or permits unintended traffic.This setup would work for a single VPC's project-level inspection only if the project-level SPG were referenced by a global network firewall policy (rather than a hierarchical policy) with the URL filtering rule placed at a low priority, though it still would not satisfy the requirement for organization-level SPG management.
This approach attempts to combine an organization-level threat prevention profile with a project-level URL filtering profile inside an organization-level Security Profile Group (SPG), and then enforce both through a hierarchical firewall policy.
URL_FILTERING profile to an organization-level group.URL_FILTERING profile inside a hierarchical firewall policy violates architectural best practices because hierarchical rules evaluate broadly across folders or the entire organization, causing the URL profile's default action to unintentionally allow or deny unrelated traffic.allow or deny action.This configuration would be valid only if the URL_FILTERING profile were created at the organization level (matching the SPG scope) and the combined Security Profile Group were applied through a global or regional network firewall policy rather than a hierarchical firewall policy.
This option splits the IPS severity override and the false-positive threat signature exception into two separate THREAT_PREVENTION profiles and attempts to bundle both alongside a URL_FILTERING profile inside a single Security Profile Group.
THREAT_PREVENTION, WILDFIRE_ANALYSIS, and URL_FILTERING). Adding a second THREAT_PREVENTION profile to the same group is not permitted.THREAT_PREVENTION profile, eliminating any need for duplicate profiles.80 and 443, a network context (such as INTERNET), or a low rule priority risks applying the URL filter's default action to non-HTTP(S) and internal east-west traffic.THREAT_PREVENTION profile, specific threat signature ID overrides always take precedence over broader severity-level overrides.This configuration would be valid if both the Critical severity override (DENY) and the signature ID 12345 exception (ALLOW) were consolidated into a single THREAT_PREVENTION profile, paired with the URL_FILTERING profile in the SPG, and applied via a properly scoped global network firewall policy rule.
This configuration combines organization-level security profiles into an organization-level Security Profile Group (SPG) and enforces it through a global network firewall policy using the apply_security_profile_group rule action.
THREAT_PREVENTION profile with a Critical severity override set to DENY and a threat signature override for ID 12345 set to ALLOW leverages Cloud NGFW's evaluation precedence, where signature overrides take precedence over severity overrides.80 and 443, the INTERNET network context, and a low rule priority prevents non-web and internal east-west traffic from triggering the URL profile's default action.INTERNET egress traffic via network contexts keeps rules clean and predictable.Unlike hierarchical policies (which risk overly broad URL matching) or project-level SPGs (which lack organization-level governance), pairing an organization-level SPG with a scoped global network firewall policy satisfies all security, scope, and operational best practices.
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