cert
cert-1
cert-2

Pass Salesforce Certified Platform Identity and Access Management Architect Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
Certified Platform Identity and Access Management Architect Exam - Verified By Experts
Certified Platform Identity and Access Management Architect Premium File

Certified Platform Identity and Access Management Architect Premium File

$69.99
$76.99
  • Premium File 58 Questions & Answers. Last Update: Nov 17, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 10 downloads in the last 7 days
block-screenshots
Salesforce Certified Platform Identity and Access Management Architect Practice Test 2

Question 10

An architect must create an acceptance test after choosing: Use OpenID Connect identity claims for authentication and OAuth scopes for resource authorization. For the situation An internal finance portal needs evidence of a user's identity in addition to API access authorization. Which result most directly proves success?

  1. Only Salesforce-issued identity claims intended for this client establish user authentication.
  2. The mobile client obtains limited tokens after user consent without learning the account password.
  3. Employees sign in once through the IdP and Salesforce validates its signed assertion for an existing identity.
  4. The portal verifies issuer, audience and nonce of an ID token and separately authorizes API access.

Explanation

Correct Answer

D:

Best. The verification target is: The portal verifies issuer, audience and nonce of an ID token and separately authorizes API access. It tests whether the chosen approach—Use OpenID Connect identity claims for authentication and OAuth scopes for resource authorization.—actually resolves the specific finding: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity.

Incorrect Answers

A:

Not best for this scenario. This option is associated with another type of requirement: A partner SaaS app signs in users using Salesforce as its OpenID Connect identity provider. Its relevant condition is: The app checks the user email claim but ignores the token signature, issuer and nonce. The present case instead turns on: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The direct answer here is: The portal verifies issuer, audience and nonce of an ID token and separately authorizes API access.

B:

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 design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The direct answer here is: The portal verifies issuer, audience and nonce of an ID token and separately authorizes API access.

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 design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The direct answer here is: The portal verifies issuer, audience and nonce of an ID token and separately authorizes API access.

Question 11

An incident scenario concerns this architecture: An internal finance portal needs evidence of a user's identity in addition to API access authorization. The team has discovered: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. Which project risk requires explicit mitigation?

  1. A fragment-delivered bearer token persists in browser history or is exposed to another kiosk user.
  2. The team confuses a delegated password callout with assertion-based single sign-on.
  3. An ordinary bearer access token is accepted as an unverified identity assertion.
  4. Treating a SAML assertion as an OAuth API token leaves the SSO flow incorrectly designed.

Explanation

Correct Answer

C:

Best. The most direct failure is: An ordinary bearer access token is accepted as an unverified identity assertion. It is a consequence of the documented condition: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. A mitigation is: Use OpenID Connect identity claims for authentication and OAuth scopes for resource authorization.

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 design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The direct answer here is: An ordinary bearer access token is accepted as an unverified identity assertion.

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 design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The direct answer here is: An ordinary bearer access token is accepted as an unverified identity assertion.

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 design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The direct answer here is: An ordinary bearer access token is accepted as an unverified identity assertion.

Question 12

An integration architect receives this requirement: A legacy call center previously relied on delegated password validation against an internal service. A technical discovery also finds: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. Which response most directly addresses the present constraint?

  1. Compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow.
  2. Use OpenID Connect identity claims for authentication and OAuth scopes for resource authorization.
  3. Use supported external-user registration and provisioning with identity matching and approved license checks.
  4. Configure Salesforce as SAML service provider and have the trusted corporate IdP authenticate users.

Explanation

Correct Answer

A:

Best. The most direct action is to compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow. It is supported by the specific finding that the new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The expected acceptance evidence is: The design uses a browser federation exchange and avoids repeated password handling by Salesforce.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An internal finance portal needs evidence of a user's identity in addition to API access authorization. Its relevant condition is: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The present case instead turns on: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: Compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow.

C:

Not best for this scenario. This option is associated with another type of requirement: A public membership site expects tens of thousands of new identity records each month. Its relevant condition is: Manually provisioning every member is infeasible and site users must be linked to the correct customer contacts. The present case instead turns on: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: Compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow.

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 new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: Compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow.

Question 13

Consider the following hypothetical Salesforce initiative: A legacy call center previously relied on delegated password validation against an internal service. Which evidence would most strongly explain the current integration weakness?

  1. The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions.
  2. The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP.
  3. The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity.
  4. The app can redirect through the system browser and securely complete a modern OAuth authorization-code flow.

Explanation

Correct Answer

B:

Best. The decisive observation is: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. This is why the design response should be: Compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A dashboard requires short-lived login sessions across multiple Salesforce orgs with consistent identity claims. Its relevant condition is: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The present case instead turns on: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An internal finance portal needs evidence of a user's identity in addition to API access authorization. Its relevant condition is: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The present case instead turns on: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP.

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 new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP.

Question 14

Review this change: Compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow. It addresses a project where A legacy call center previously relied on delegated password validation against an internal service. Which result should appear in integration acceptance evidence?

  1. The portal verifies issuer, audience and nonce of an ID token and separately authorizes API access.
  2. The design uses a browser federation exchange and avoids repeated password handling by Salesforce.
  3. Each org accepts only the protocol and trusted assertions configured for its federation endpoint.
  4. The shared-device workflow uses an authorization code and protects against intercepted-code misuse.

Explanation

Correct Answer

B:

Best. The verification target is: The design uses a browser federation exchange and avoids repeated password handling by Salesforce. It tests whether the chosen approach—Compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow.—actually resolves the specific finding: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An internal finance portal needs evidence of a user's identity in addition to API access authorization. Its relevant condition is: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The present case instead turns on: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: The design uses a browser federation exchange and avoids repeated password handling by Salesforce.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A dashboard requires short-lived login sessions across multiple Salesforce orgs with consistent identity claims. Its relevant condition is: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The present case instead turns on: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: The design uses a browser federation exchange and avoids repeated password handling by Salesforce.

D:

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 new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: The design uses a browser federation exchange and avoids repeated password handling by Salesforce.

Question 15

Suppose the integration design proceeds without correcting this issue: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. In the environment A legacy call center previously relied on delegated password validation against an internal service. What should the risk register emphasize?

  1. A fragment-delivered bearer token persists in browser history or is exposed to another kiosk user.
  2. The team confuses a delegated password callout with assertion-based single sign-on.
  3. An ordinary bearer access token is accepted as an unverified identity assertion.
  4. The app collects and stores Salesforce passwords or exposes a reusable embedded client secret.

Explanation

Correct Answer

B:

Best. The most direct failure is: The team confuses a delegated password callout with assertion-based single sign-on. It is a consequence of the documented condition: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. A mitigation is: Compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow.

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 new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: The team confuses a delegated password callout with assertion-based single sign-on.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An internal finance portal needs evidence of a user's identity in addition to API access authorization. Its relevant condition is: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The present case instead turns on: The new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: The team confuses a delegated password callout with assertion-based single sign-on.

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 new requirement is browser-based SSO and centralized conditional access managed by the enterprise IdP. The direct answer here is: The team confuses a delegated password callout with assertion-based single sign-on.

Question 16

Salesforce and its partners face the following situation: A tablet app is installed on shared devices that can open a system browser but should not store user credentials. The integration review notes: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. Which architectural step should take priority?

  1. Document protocol-specific assertion or token validation, trust keys, issuer and audience requirements.
  2. Evaluate authorization code plus PKCE with a trusted external authorization server and documented Salesforce support.
  3. Use OpenID Connect identity claims for authentication and OAuth scopes for resource authorization.
  4. Compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow.

Explanation

Correct Answer

B:

Best. The most direct action is to evaluate authorization code plus PKCE with a trusted external authorization server and documented Salesforce support. It is supported by the specific finding that the team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The expected acceptance evidence is: The shared-device workflow uses an authorization code and protects against intercepted-code misuse.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A dashboard requires short-lived login sessions across multiple Salesforce orgs with consistent identity claims. Its relevant condition is: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The present case instead turns on: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: Evaluate authorization code plus PKCE with a trusted external authorization server and documented Salesforce support.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An internal finance portal needs evidence of a user's identity in addition to API access authorization. Its relevant condition is: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The present case instead turns on: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: Evaluate authorization code plus PKCE with a trusted external authorization server and documented Salesforce support.

D:

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 team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: Evaluate authorization code plus PKCE with a trusted external authorization server and documented Salesforce support.

Question 17

An implementation team investigates this scenario: A tablet app is installed on shared devices that can open a system browser but should not store user credentials. Which finding would most directly justify a change to the integration architecture?

  1. The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions.
  2. The app can redirect through the system browser and securely complete a modern OAuth authorization-code flow.
  3. The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment.
  4. The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity.

Explanation

Correct Answer

C:

Best. The decisive observation is: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. This is why the design response should be: Evaluate authorization code plus PKCE with a trusted external authorization server and documented Salesforce support.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A dashboard requires short-lived login sessions across multiple Salesforce orgs with consistent identity claims. Its relevant condition is: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The present case instead turns on: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment.

B:

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 team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An internal finance portal needs evidence of a user's identity in addition to API access authorization. Its relevant condition is: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The present case instead turns on: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment.

Question 18

A solution review asks whether this control is effective: Evaluate authorization code plus PKCE with a trusted external authorization server and documented Salesforce support. The business setting is: A tablet app is installed on shared devices that can open a system browser but should not store user credentials. What should a demonstrable successful outcome be?

  1. The portal verifies issuer, audience and nonce of an ID token and separately authorizes API access.
  2. The design uses a browser federation exchange and avoids repeated password handling by Salesforce.
  3. The shared-device workflow uses an authorization code and protects against intercepted-code misuse.
  4. Employees sign in once through the IdP and Salesforce validates its signed assertion for an existing identity.

Explanation

Correct Answer

C:

Best. The verification target is: The shared-device workflow uses an authorization code and protects against intercepted-code misuse. It tests whether the chosen approach—Evaluate authorization code plus PKCE with a trusted external authorization server and documented Salesforce support.—actually resolves the specific finding: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An internal finance portal needs evidence of a user's identity in addition to API access authorization. Its relevant condition is: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The present case instead turns on: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: The shared-device workflow uses an authorization code and protects against intercepted-code misuse.

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 team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: The shared-device workflow uses an authorization code and protects against intercepted-code misuse.

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 team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: The shared-device workflow uses an authorization code and protects against intercepted-code misuse.

Question 19

A Salesforce integration initiative faces this situation: A tablet app is installed on shared devices that can open a system browser but should not store user credentials. The critical observation is: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. What failure is most likely if it is ignored?

  1. A SAML assertion is erroneously sent to an OIDC token verifier without signature and audience checks.
  2. An ordinary bearer access token is accepted as an unverified identity assertion.
  3. A fragment-delivered bearer token persists in browser history or is exposed to another kiosk user.
  4. The team confuses a delegated password callout with assertion-based single sign-on.

Explanation

Correct Answer

C:

Best. The most direct failure is: A fragment-delivered bearer token persists in browser history or is exposed to another kiosk user. It is a consequence of the documented condition: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. A mitigation is: Evaluate authorization code plus PKCE with a trusted external authorization server and documented Salesforce support.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A dashboard requires short-lived login sessions across multiple Salesforce orgs with consistent identity claims. Its relevant condition is: The architect's draft assumes OIDC and SAML exchange the same token formats and metadata conventions. The present case instead turns on: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: A fragment-delivered bearer token persists in browser history or is exposed to another kiosk user.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An internal finance portal needs evidence of a user's identity in addition to API access authorization. Its relevant condition is: The design uses OAuth access tokens as if they were universally proof of the person's authenticated identity. The present case instead turns on: The team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: A fragment-delivered bearer token persists in browser history or is exposed to another kiosk user.

D:

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 team proposes an obsolete implicit-flow pattern where access tokens are returned directly in a redirect fragment. The direct answer here is: A fragment-delivered bearer token persists in browser history or is exposed to another kiosk user.

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?

  1. Evaluate authorization code plus PKCE with a trusted external authorization server and documented Salesforce support.
  2. Document protocol-specific assertion or token validation, trust keys, issuer and audience requirements.
  3. Compare delegated authentication with modern federation, then prefer a suitable supported SAML or OIDC flow.
  4. 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.

Certified Platform Identity and Access Management Architect Practice Tests