Question 520
A compliance officer requests who signed in and whether authentication used challenged or verified methods. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Correlate Login History, identity verification and licensed event monitoring where available. Verification: Inspect event timestamps, user IDs, error categories, device/session context and audit retention. Boundary: Availability and retention of enhanced event data depend on current product entitlements and configuration” addresses the access-design responsibilities in a compliance officer requests who signed in and whether authentication used challenged or verified methods Test against inspect event timestamps, user IDs, error categories, device/session context and audit retention; availability and retention of enhanced event data depend on current product entitlements and configuration.
Incorrect Answers
“Action: Correlate Login History, identity verification and licensed event monitoring where available. Verification: Compare new permissions, active sessions, app policies and denied legacy actions. Boundary: A second password or another knowledge-only challenge is not automatically an independent MFA factor” may apply to a related identity task, but it does not establish inspect event timestamps, user IDs, error categories, device/session context and audit retention for a compliance officer requests who signed in and whether authentication used challenged or verified methods The controlling boundary is: Availability and retention of enhanced event data depend on current product entitlements and configuration.
“Action: Require supported multifactor authentication and a tested recovery strategy appropriate to user risk. Verification: Inspect event timestamps, user IDs, error categories, device/session context and audit retention. Boundary: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged” may apply to a related identity task, but it does not establish inspect event timestamps, user IDs, error categories, device/session context and audit retention for a compliance officer requests who signed in and whether authentication used challenged or verified methods The controlling boundary is: Availability and retention of enhanced event data depend on current product entitlements and configuration.
“Action: Preserve Setup Audit Trail and relevant configuration-change evidence with approved retention. Verification: Test revoked session, refresh-token rejection, user activity records and alternate devices. Boundary: Availability and retention of enhanced event data depend on current product entitlements and configuration” may apply to a related identity task, but it does not establish inspect event timestamps, user IDs, error categories, device/session context and audit retention for a compliance officer requests who signed in and whether authentication used challenged or verified methods The controlling boundary is: Availability and retention of enhanced event data depend on current product entitlements and configuration.