Question 330
Original unofficial Palo Alto Networks NetSec-Architect scenario: A firewall fleet consumes groups from a stale directory source and has access policies tied to memberships deleted months ago. Which test result best demonstrates that the design meets its requirement?
Explanation
Correct Answer
Original fictional security architecture situation: A firewall fleet consumes groups from a stale directory source and has access policies tied to memberships deleted months ago. Governing principle: NGFW policy accuracy depends on current directory context as well as rule syntax. The most defensible design response is: Integrate the supported CIE user/group directory source and validate mapping freshness at the NGFW enforcement points. Validation: A removed test user no longer matches the retired privileged group on the firewall. Sustained assurance: Monitor directory-to-NGFW mapping latency and remove unused group references
Incorrect Answers
The suggested “The same approved employee receives consistent access policy from two test regions.” tests a different architectural concern: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. Here, a firewall fleet consumes groups from a stale directory source and has access policies tied to memberships deleted months ago. NGFW policy accuracy depends on current directory context as well as rule syntax.
“Group membership updates from the isolated directory reach the cloud mapping through the approved agent path.” concerns the separate design topic: recommend cloud identity engine on-prem agent and cloud-directory sync choices. It would not fix the described weakness: a firewall fleet consumes groups from a stale directory source and has access policies tied to memberships deleted months ago. NGFW policy accuracy depends on current directory context as well as rule syntax.
This alternative is linked to the architecture category: recommend cloud identity engine on-prem agent and cloud-directory sync choices. The actual problem is that a firewall fleet consumes groups from a stale directory source and has access policies tied to memberships deleted months ago; the controlling distinction is: NGFW policy accuracy depends on current directory context as well as rule syntax.