User-ID and App-ID are complementary technologies for user- and application-aware security. - Option A (Correct): User-ID integrates with identity sources (like SAML providers via CIE or GlobalProtect agent) to obtain the username associated with the IP address that the remote user is assigned by Prisma Access. This mapping is then used in policy. - Option B (Correct): App-ID identifies the application by examining traffic characteristics, protocol decoding, and behavioral analysis, independent of the static port, providing the 'what' of the session. - Option C (Correct): Security Policy rules are the point where User-ID (who), App-ID (what), and traditional Layer 3/4/zone information (where) are combined to create highly specific rules like "Allow Marketing users access to Salesforce App when going from Mobile-Users zone to Public zone." - Option D (Incorrect): App-ID identification and User-ID mapping are often parallel processes during session setup. User-ID maps the source IP to a user; App-ID identifies the application based on the flow characteristics. Neither strictly requires the other to complete first, although both are needed for policies that combine them. - Option E (Incorrect): While decryption significantly enhances App-ID accuracy, especially for distinguishing different applications on the same encrypted port (like various SaaS apps on 443), App-ID can often identify applications using methods like SNI inspection, certificate common names, and behavioral analysis even without full decryption.