Question 350
Original unofficial Palo Alto Networks NetSec-Architect scenario: An organization introduces contractor identities in its cloud directory, but network access policies implicitly treat all directory users as employees. Which test result best demonstrates that the design meets its requirement?
Explanation
Correct Answer
Original fictional security architecture situation: An organization introduces contractor identities in its cloud directory, but network access policies implicitly treat all directory users as employees. Governing principle: Directory presence indicates an authenticated principal, not a universal business entitlement. The most defensible design response is: Create explicit identity classes and least-privilege group-policy distinctions for employees, contractors and service users across target platforms. Validation: A contractor test identity receives only the approved limited application set. Sustained assurance: Recertify external identity group scope at contract expiration
Incorrect Answers
The suggested “An attribute inventory shows only approved identity fields used in each enforcement context.” tests a different architectural concern: evaluate cloud identity engine across ngfw, prisma access and prisma sd-wan. Here, an organization introduces contractor identities in its cloud directory, but network access policies implicitly treat all directory users as employees. Directory presence indicates an authenticated principal, not a universal business entitlement.
The proposed design “The access log ties the federated session to the intended contractor identity and policy group.” addresses this related architecture topic: recommend user identification and authentication methods including saml. The actual security gap is that an organization introduces contractor identities in its cloud directory, but network access policies implicitly treat all directory users as employees. Directory presence indicates an authenticated principal, not a universal business entitlement.
“The two test users retain distinct identities and policy group membership after sync.” concerns the separate design topic: recommend cloud identity engine on-prem agent and cloud-directory sync choices. It would not fix the described weakness: an organization introduces contractor identities in its cloud directory, but network access policies implicitly treat all directory users as employees. Directory presence indicates an authenticated principal, not a universal business entitlement.