Salesforce Certified Platform Identity and Access Management Architect Practice Test 3
Question 20
An integration architect receives this requirement: A dashboard requires short-lived login sessions across multiple Salesforce orgs with consistent identity claims. A technical discovery also finds: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. Which response most directly addresses the present constraint?
- Evaluate authorization code plus PKCE with a trusted external authorization server and documented Salesforce support.
- Document protocol-specific assertion or token validation, trust keys, issuer and audience requirements.
- Compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow.
- Configure Salesforce as SAML service provider and have the trusted corporate IdP authenticate users.
Explanation
Correct Answer
B:Best. The most direct action is to document protocol-specific assertion or token validation, trust keys, issuer and audience requirements. It is supported by the specific finding that the architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The expected acceptance evidence is: Each org accepts only the protocol and trusted assertions configured for its federation endpoint.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A tablet app is installed on shared devices that can open a system browser but should not store user credentials. Its relevant condition is: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: Document protocol-specific assertion or token validation, trust keys, issuer and audience requirements.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A legacy call center previously relied on delegated password validation against an internal service. Its relevant condition is: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: Document protocol-specific assertion or token validation, trust keys, issuer and audience requirements.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A global manufacturer wants its workforce to access Salesforce and several SaaS applications after one corporate sign-in. Its relevant condition is: The existing workforce IdP can issue signed SAML assertions, while Salesforce must consume the authentication. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: Document protocol-specific assertion or token validation, trust keys, issuer and audience requirements.
Question 21
Consider the following hypothetical Salesforce initiative: A dashboard requires short-lived login sessions across multiple Salesforce orgs with consistent identity claims. Which evidence would most strongly explain the current integration weakness?
- The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment.
- The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP.
- The existing workforce IdP can issue signed SAML assertions, while Salesforce must consume the authentication.
- The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions.
Explanation
Correct Answer
D:Best. The decisive observation is: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. This is why the design response should be: Document protocol-specific assertion or token validation, trust keys, issuer and audience requirements.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A tablet app is installed on shared devices that can open a system browser but should not store user credentials. Its relevant condition is: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A legacy call center previously relied on delegated password validation against an internal service. Its relevant condition is: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A global manufacturer wants its workforce to access Salesforce and several SaaS applications after one corporate sign-in. Its relevant condition is: The existing workforce IdP can issue signed SAML assertions, while Salesforce must consume the authentication. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions.
Question 22
Review this change: Document protocol-specific assertion or token validation, trust keys, issuer and audience requirements. It addresses a project where A dashboard requires short-lived login sessions across multiple Salesforce orgs with consistent identity claims. Which result should appear in integration acceptance evidence?
- The design uses a browser federation exchange and avoids repeated password handling by Salesforce.
- Each org accepts only the protocol and trusted assertions configured for its federation endpoint.
- Employees sign in once through the IdP and Salesforce validates its signed assertion for an existing identity.
- The mobile client obtains limited tokens after user consent without learning the account password.
Explanation
Correct Answer
B:Best. The verification target is: Each org accepts only the protocol and trusted assertions configured for its federation endpoint. It tests whether the chosen approach—Document protocol-specific assertion or token validation, trust keys, issuer and audience requirements.—actually resolves the specific finding: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A legacy call center previously relied on delegated password validation against an internal service. Its relevant condition is: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: Each org accepts only the protocol and trusted assertions configured for its federation endpoint.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A global manufacturer wants its workforce to access Salesforce and several SaaS applications after one corporate sign-in. Its relevant condition is: The existing workforce IdP can issue signed SAML assertions, while Salesforce must consume the authentication. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: Each org accepts only the protocol and trusted assertions configured for its federation endpoint.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A mobile field-service app needs to call Salesforce APIs on behalf of an employee without handling the employee password. Its relevant condition is: The app can redirect through the system browser and securely complete a modern OAuth authorization-code flow. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: Each org accepts only the protocol and trusted assertions configured for its federation endpoint.
Question 23
Suppose the integration design proceeds without correcting this issue: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. In the environment A dashboard requires short-lived login sessions across multiple Salesforce orgs with consistent identity claims. What should the risk register emphasize?
- A fragment-delivered bearer token persists in browser history or is exposed to another kiosk user.
- The team confuses a delegated password callout with assertion-based single sign-on.
- A SAML assertion is erroneously sent to an OIDC token verifier without signature and audience checks.
- The app collects and stores Salesforce passwords or exposes a reusable embedded client secret.
Explanation
Correct Answer
C:Best. The most direct failure is: A SAML assertion is erroneously sent to an OIDC token verifier without signature and audience checks. It is a consequence of the documented condition: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. A mitigation is: Document protocol-specific assertion or token validation, trust keys, issuer and audience requirements.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A tablet app is installed on shared devices that can open a system browser but should not store user credentials. Its relevant condition is: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: A SAML assertion is erroneously sent to an OIDC token verifier without signature and audience checks.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A legacy call center previously relied on delegated password validation against an internal service. Its relevant condition is: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: A SAML assertion is erroneously sent to an OIDC token verifier without signature and audience checks.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A mobile field-service app needs to call Salesforce APIs on behalf of an employee without handling the employee password. Its relevant condition is: The app can redirect through the system browser and securely complete a modern OAuth authorization-code flow. The present case instead turns on: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The direct answer here is: A SAML assertion is erroneously sent to an OIDC token verifier without signature and audience checks.
Question 24
An integration architect receives this requirement: A manager asks why a successfully authenticated employee cannot export a confidential Salesforce report. A technical discovery also finds: Login verification succeeds but the employee's permission sets exclude the report's protected data. Which response most directly addresses the present constraint?
- Separate authentication evidence from profile, permission-set and record-level authorization decisions.
- Require individually attributable administrative identities with recorded configuration changes and audit events.
- Apply independent object, field and record-level authorization to the authenticated integration user.
- Enable and retain relevant audit events for admin actions, access and authentication, with approved retention.
Explanation
Correct Answer
A:Best. The most direct action is to separate authentication evidence from profile, permission-set and record-level authorization decisions. It is supported by the specific finding that Login verification succeeds but the employee's permission sets exclude the report's protected data. The expected acceptance evidence is: The user can sign in while an ungranted report export remains correctly denied.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An audit team investigates who changed a connected application's OAuth policy during an incident. Its relevant condition is: Several administrators share a single service account and change logs cannot attribute the edit to one person. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: Separate authentication evidence from profile, permission-set and record-level authorization decisions.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A service integration authenticates with a valid client credential but reads records belonging to unrelated customers. Its relevant condition is: The system treats successful client authentication as unrestricted permission to all Salesforce objects. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: Separate authentication evidence from profile, permission-set and record-level authorization decisions.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regulator requires evidence of privileged approval changes in an Experience Cloud environment. Its relevant condition is: The implementation records only successful logins but not privileged permission updates or resource access. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: Separate authentication evidence from profile, permission-set and record-level authorization decisions.
Question 25
Consider the following hypothetical Salesforce initiative: A manager asks why a successfully authenticated employee cannot export a confidential Salesforce report. Which evidence would most strongly explain the current integration weakness?
- The initial diagram only shows the login screen and omits resource authorization or audit responsibility.
- The implementation records only successful logins but not privileged permission updates or resource access.
- The system treats successful client authentication as unrestricted permission to all Salesforce objects.
- Login verification succeeds but the employee's permission sets exclude the report's protected data.
Explanation
Correct Answer
D:Best. The decisive observation is: Login verification succeeds but the employee's permission sets exclude the report's protected data. This is why the design response should be: Separate authentication evidence from profile, permission-set and record-level authorization decisions.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security architect must explain why user identity, application permission and activity logs are all needed. Its relevant condition is: The initial diagram only shows the login screen and omits resource authorization or audit responsibility. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: Login verification succeeds but the employee's permission sets exclude the report's protected data.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regulator requires evidence of privileged approval changes in an Experience Cloud environment. Its relevant condition is: The implementation records only successful logins but not privileged permission updates or resource access. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: Login verification succeeds but the employee's permission sets exclude the report's protected data.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A service integration authenticates with a valid client credential but reads records belonging to unrelated customers. Its relevant condition is: The system treats successful client authentication as unrestricted permission to all Salesforce objects. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: Login verification succeeds but the employee's permission sets exclude the report's protected data.
Question 26
Review this change: Separate authentication evidence from profile, permission-set and record-level authorization decisions. It addresses a project where A manager asks why a successfully authenticated employee cannot export a confidential Salesforce report. Which result should appear in integration acceptance evidence?
- Suspended identities lose interactive and programmatic access within the documented control window.
- The user can sign in while an ungranted report export remains correctly denied.
- The design identifies who signed in, what the identity may do and how activity is evidenced.
- Investigators can attribute a role grant and subsequent sensitive action to an authorized identity.
Explanation
Correct Answer
B:Best. The verification target is: The user can sign in while an ungranted report export remains correctly denied. It tests whether the chosen approach—Separate authentication evidence from profile, permission-set and record-level authorization decisions.—actually resolves the specific finding: Login verification succeeds but the employee's permission sets exclude the report's protected data.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner identity is suspended at the corporate IdP, but a long-lived Salesforce API token remains usable. Its relevant condition is: The current design treats authentication termination as though it automatically revokes every issued token. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: The user can sign in while an ungranted report export remains correctly denied.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security architect must explain why user identity, application permission and activity logs are all needed. Its relevant condition is: The initial diagram only shows the login screen and omits resource authorization or audit responsibility. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: The user can sign in while an ungranted report export remains correctly denied.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regulator requires evidence of privileged approval changes in an Experience Cloud environment. Its relevant condition is: The implementation records only successful logins but not privileged permission updates or resource access. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: The user can sign in while an ungranted report export remains correctly denied.
Question 27
Suppose the integration design proceeds without correcting this issue: Login verification succeeds but the employee's permission sets exclude the report's protected data. In the environment A manager asks why a successfully authenticated employee cannot export a confidential Salesforce report. What should the risk register emphasize?
- An unidentified shared administrator changes access rules without a reconstructable audit trail.
- A malicious permission increase cannot be correlated with the user who initiated it.
- Security staff weaken login controls rather than correcting a legitimate authorization boundary.
- An attacker continues using an already-issued token after the workforce account is terminated.
Explanation
Correct Answer
C:Best. The most direct failure is: Security staff weaken login controls rather than correcting a legitimate authorization boundary. It is a consequence of the documented condition: Login verification succeeds but the employee's permission sets exclude the report's protected data. A mitigation is: Separate authentication evidence from profile, permission-set and record-level authorization decisions.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An audit team investigates who changed a connected application's OAuth policy during an incident. Its relevant condition is: Several administrators share a single service account and change logs cannot attribute the edit to one person. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: Security staff weaken login controls rather than correcting a legitimate authorization boundary.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regulator requires evidence of privileged approval changes in an Experience Cloud environment. Its relevant condition is: The implementation records only successful logins but not privileged permission updates or resource access. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: Security staff weaken login controls rather than correcting a legitimate authorization boundary.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner identity is suspended at the corporate IdP, but a long-lived Salesforce API token remains usable. Its relevant condition is: The current design treats authentication termination as though it automatically revokes every issued token. The present case instead turns on: Login verification succeeds but the employee's permission sets exclude the report's protected data. The direct answer here is: Security staff weaken login controls rather than correcting a legitimate authorization boundary.
Question 28
Salesforce and its partners face the following situation: An audit team investigates who changed a connected application's OAuth policy during an incident. The integration review notes: Several administrators share a single service account and change logs cannot attribute the edit to one person. Which architectural step should take priority?
- Map authentication, authorization and accountability controls to each identity-dependent operation.
- Require individually attributable administrative identities with recorded configuration changes and audit events.
- Connect user deactivation and session or token revocation to the access lifecycle and monitor the effect.
- Separate authentication evidence from profile, permission-set and record-level authorization decisions.
Explanation
Correct Answer
B:Best. The most direct action is to require individually attributable administrative identities with recorded configuration changes and audit events. It is supported by the specific finding that Several administrators share a single service account and change logs cannot attribute the edit to one person. The expected acceptance evidence is: The review links each sensitive policy edit to a distinct accountable principal and timestamp.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security architect must explain why user identity, application permission and activity logs are all needed. Its relevant condition is: The initial diagram only shows the login screen and omits resource authorization or audit responsibility. The present case instead turns on: Several administrators share a single service account and change logs cannot attribute the edit to one person. The direct answer here is: Require individually attributable administrative identities with recorded configuration changes and audit events.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner identity is suspended at the corporate IdP, but a long-lived Salesforce API token remains usable. Its relevant condition is: The current design treats authentication termination as though it automatically revokes every issued token. The present case instead turns on: Several administrators share a single service account and change logs cannot attribute the edit to one person. The direct answer here is: Require individually attributable administrative identities with recorded configuration changes and audit events.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manager asks why a successfully authenticated employee cannot export a confidential Salesforce report. Its relevant condition is: Login verification succeeds but the employee's permission sets exclude the report's protected data. The present case instead turns on: Several administrators share a single service account and change logs cannot attribute the edit to one person. The direct answer here is: Require individually attributable administrative identities with recorded configuration changes and audit events.
Question 29
An implementation team investigates this scenario: An audit team investigates who changed a connected application's OAuth policy during an incident. Which finding would most directly justify a change to the integration architecture?
- Several administrators share a single service account and change logs cannot attribute the edit to one person.
- The implementation records only successful logins but not privileged permission updates or resource access.
- The system treats successful client authentication as unrestricted permission to all Salesforce objects.
- Login verification succeeds but the employee's permission sets exclude the report's protected data.
Explanation
Correct Answer
A:Best. The decisive observation is: Several administrators share a single service account and change logs cannot attribute the edit to one person. This is why the design response should be: Require individually attributable administrative identities with recorded configuration changes and audit events.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regulator requires evidence of privileged approval changes in an Experience Cloud environment. Its relevant condition is: The implementation records only successful logins but not privileged permission updates or resource access. The present case instead turns on: Several administrators share a single service account and change logs cannot attribute the edit to one person. The direct answer here is: Several administrators share a single service account and change logs cannot attribute the edit to one person.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A service integration authenticates with a valid client credential but reads records belonging to unrelated customers. Its relevant condition is: The system treats successful client authentication as unrestricted permission to all Salesforce objects. The present case instead turns on: Several administrators share a single service account and change logs cannot attribute the edit to one person. The direct answer here is: Several administrators share a single service account and change logs cannot attribute the edit to one person.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manager asks why a successfully authenticated employee cannot export a confidential Salesforce report. Its relevant condition is: Login verification succeeds but the employee's permission sets exclude the report's protected data. The present case instead turns on: Several administrators share a single service account and change logs cannot attribute the edit to one person. The direct answer here is: Several administrators share a single service account and change logs cannot attribute the edit to one person.
Question 30
A solution review asks whether this control is effective: Require individually attributable administrative identities with recorded configuration changes and audit events. The business setting is: An audit team investigates who changed a connected application's OAuth policy during an incident. What should a demonstrable successful outcome be?
- Investigators can attribute a role grant and subsequent sensitive action to an authorized identity.
- The integration can access only approved customer records while out-of-scope reads fail.
- The user can sign in while an ungranted report export remains correctly denied.
- The review links each sensitive policy edit to a distinct accountable principal and timestamp.
Explanation
Correct Answer
D:Best. The verification target is: The review links each sensitive policy edit to a distinct accountable principal and timestamp. It tests whether the chosen approach—Require individually attributable administrative identities with recorded configuration changes and audit events.—actually resolves the specific finding: Several administrators share a single service account and change logs cannot attribute the edit to one person.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regulator requires evidence of privileged approval changes in an Experience Cloud environment. Its relevant condition is: The implementation records only successful logins but not privileged permission updates or resource access. The present case instead turns on: Several administrators share a single service account and change logs cannot attribute the edit to one person. The direct answer here is: The review links each sensitive policy edit to a distinct accountable principal and timestamp.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A service integration authenticates with a valid client credential but reads records belonging to unrelated customers. Its relevant condition is: The system treats successful client authentication as unrestricted permission to all Salesforce objects. The present case instead turns on: Several administrators share a single service account and change logs cannot attribute the edit to one person. The direct answer here is: The review links each sensitive policy edit to a distinct accountable principal and timestamp.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manager asks why a successfully authenticated employee cannot export a confidential Salesforce report. Its relevant condition is: Login verification succeeds but the employee's permission sets exclude the report's protected data. The present case instead turns on: Several administrators share a single service account and change logs cannot attribute the edit to one person. The direct answer here is: The review links each sensitive policy edit to a distinct accountable principal and timestamp.