Question 240
Before approving a proposed shortcut for the following case—Prisma SD-WAN branches use local host identity labels that drift from organization-wide directory records—which risk should be considered first?
Explanation
Correct Answer
The controlling risk is that reusing a group name in separate systems does not guarantee it identifies the same users. In the reported setting—prisma SD-WAN branches use local host identity labels that drift from organization-wide directory records—the team needs to review supported Cloud Identity Engine features for Prisma SD-WAN and local enforcement scope and then design consistent identity mapping and enforceable branch identity policy with CIE where supported. The expected safe result is that a branch user identity change is reflected in the applicable monitored access policy.
Incorrect Answers
The distinct use case for this response is “A mobile-user deployment has correct Prisma Access routing but SAML users are not assigned to expected policy groups”. The expected safe result is that the test remote user receives identity-scoped access while other groups remain restricted. The present case instead calls for “Reusing a group name in separate systems does not guarantee it identifies the same users”.
This can be appropriate when an enterprise wants to standardize identity policy across NGFW, Prisma Access and Prisma SD-WAN without a universal trust blanket, but it does not isolate the distinguishing requirement here: Prisma SD-WAN branches use local host identity labels that drift from organization-wide directory records. The correct risk decision is reusing a group name in separate systems does not guarantee it identifies the same users.
Applying this option would direct attention to nGFW Security policy refers to cloud-directory groups yet firewalls report unknown users during branch login testing. In the reported design—prisma SD-WAN branches use local host identity labels that drift from organization-wide directory records—the needed risk statement is reusing a group name in separate systems does not guarantee it identifies the same users.