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 30

Question 290

An architecture board reviews a proposed Salesforce integration. Context: A finance firm wants a Salesforce-connected kiosk to let employees approve payments and then end the session. Finding: The kiosk is shared and tokens must not persist across people or long idle periods. Which decision best resolves the concern?

  1. Choose authorization code with PKCE and a system browser with a securely registered redirect.
  2. Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.
  3. Use a supported OAuth authorization-code web-server flow and validate state and redirect URI.
  4. Choose a supported user interactive OAuth flow with PKCE and explicit logout or token cleanup.

Explanation

Correct Answer

D:

Best. The most direct action is to choose a supported user interactive OAuth flow with PKCE and explicit logout or token cleanup. It is supported by the specific finding that the kiosk is shared and tokens must not persist across people or long idle periods. The expected acceptance evidence is: Each employee grants personal scoped access and the next kiosk user sees no prior tokens.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A native mobile app runs on personally owned phones and invokes Salesforce APIs for the signed-in user. Its relevant condition is: The application cannot safely keep a client secret and may be attacked through intercepted redirects. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: Choose a supported user interactive OAuth flow with PKCE and explicit logout or token cleanup.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consumer mobile app requests identity and profile information while also accessing Salesforce data. Its relevant condition is: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: Choose a supported user interactive OAuth flow with PKCE and explicit logout or token cleanup.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-rendered customer portal needs Salesforce to authorize API calls after a customer signs in. Its relevant condition is: The web server can protect a client secret, receive a registered redirect and exchange a one-time code. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: Choose a supported user interactive OAuth flow with PKCE and explicit logout or token cleanup.

Question 291

A design workshop describes this environment: A finance firm wants a Salesforce-connected kiosk to let employees approve payments and then end the session. Which concrete observation should be documented as the most decisive issue?

  1. The web server can protect a client secret, receive a registered redirect and exchange a one-time code.
  2. The API must honor the employee's current permissions and a browser approval step is available.
  3. The kiosk is shared and tokens must not persist across people or long idle periods.
  4. The design equates an OAuth access token with a login identity proof and has no signed identity claims.

Explanation

Correct Answer

C:

Best. The decisive observation is: The kiosk is shared and tokens must not persist across people or long idle periods. This is why the design response should be: Choose a supported user interactive OAuth flow with PKCE and explicit logout or token cleanup.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-rendered customer portal needs Salesforce to authorize API calls after a customer signs in. Its relevant condition is: The web server can protect a client secret, receive a registered redirect and exchange a one-time code. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: The kiosk is shared and tokens must not persist across people or long idle periods.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise app needs to act on behalf of a specific employee when reading Salesforce task data. Its relevant condition is: The API must honor the employee's current permissions and a browser approval step is available. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: The kiosk is shared and tokens must not persist across people or long idle periods.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consumer mobile app requests identity and profile information while also accessing Salesforce data. Its relevant condition is: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: The kiosk is shared and tokens must not persist across people or long idle periods.

Question 292

An architect must create an acceptance test after choosing: Choose a supported user interactive OAuth flow with PKCE and explicit logout or token cleanup. For the situation A finance firm wants a Salesforce-connected kiosk to let employees approve payments and then end the session. Which result most directly proves success?

  1. The service obtains time-limited API authorization without interactive user login or stored password.
  2. A trusted service obtains a token without storing a personal employee password.
  3. Each employee grants personal scoped access and the next kiosk user sees no prior tokens.
  4. The portal obtains user-scoped tokens without receiving the customer's Salesforce password.

Explanation

Correct Answer

C:

Best. The verification target is: Each employee grants personal scoped access and the next kiosk user sees no prior tokens. It tests whether the chosen approach—Choose a supported user interactive OAuth flow with PKCE and explicit logout or token cleanup.—actually resolves the specific finding: The kiosk is shared and tokens must not persist across people or long idle periods.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A headless scheduled analytics job reads Salesforce records nightly without a person present. Its relevant condition is: The service holds an approved signing certificate and the Salesforce client app is preauthorized. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: Each employee grants personal scoped access and the next kiosk user sees no prior tokens.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. Its relevant condition is: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: Each employee grants personal scoped access and the next kiosk user sees no prior tokens.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-rendered customer portal needs Salesforce to authorize API calls after a customer signs in. Its relevant condition is: The web server can protect a client secret, receive a registered redirect and exchange a one-time code. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: Each employee grants personal scoped access and the next kiosk user sees no prior tokens.

Question 293

An incident scenario concerns this architecture: A finance firm wants a Salesforce-connected kiosk to let employees approve payments and then end the session. The team has discovered: The kiosk is shared and tokens must not persist across people or long idle periods. Which project risk requires explicit mitigation?

  1. An implicit browser token is used where a secure server-side exchange is readily available.
  2. An unattended service is designed to require a human to click an authorization link every night.
  3. A token issued for one resource is accepted as proof of the person's identity elsewhere.
  4. A shared device inherits the previous employee's refresh token and transaction rights.

Explanation

Correct Answer

D:

Best. The most direct failure is: A shared device inherits the previous employee's refresh token and transaction rights. It is a consequence of the documented condition: The kiosk is shared and tokens must not persist across people or long idle periods. A mitigation is: Choose a supported user interactive OAuth flow with PKCE and explicit logout or token cleanup.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-rendered customer portal needs Salesforce to authorize API calls after a customer signs in. Its relevant condition is: The web server can protect a client secret, receive a registered redirect and exchange a one-time code. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: A shared device inherits the previous employee's refresh token and transaction rights.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A headless scheduled analytics job reads Salesforce records nightly without a person present. Its relevant condition is: The service holds an approved signing certificate and the Salesforce client app is preauthorized. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: A shared device inherits the previous employee's refresh token and transaction rights.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consumer mobile app requests identity and profile information while also accessing Salesforce data. Its relevant condition is: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The present case instead turns on: The kiosk is shared and tokens must not persist across people or long idle periods. The direct answer here is: A shared device inherits the previous employee's refresh token and transaction rights.

Question 294

An architecture board reviews a proposed Salesforce integration. Context: A consumer mobile app requests identity and profile information while also accessing Salesforce data. Finding: The design equates an OAuth access token with a login identity proof and has no signed identity claims. Which decision best resolves the concern?

  1. Limit approved connected-app scopes and refresh-token policy to the actual portal requirement.
  2. Evaluate the OAuth device authorization flow supported for its client and user-interaction model.
  3. Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.
  4. Use a supported OAuth authorization-code web-server flow and validate state and redirect URI.

Explanation

Correct Answer

C:

Best. The most direct action is to add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization. It is supported by the specific finding that the design equates an OAuth access token with a login identity proof and has no signed identity claims. The expected acceptance evidence is: The app verifies user identity via a signed ID token and constrains API permissions separately.

Incorrect Answers

A:

Not best for this scenario. This option is associated with another type of requirement: A Salesforce org provides identity to an external analytics portal that requests both profile and report access. Its relevant condition is: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Its relevant condition is: The device has a limited interface but can present a short activation code and poll with rate limits. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-rendered customer portal needs Salesforce to authorize API calls after a customer signs in. Its relevant condition is: The web server can protect a client secret, receive a registered redirect and exchange a one-time code. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.

Question 295

A design workshop describes this environment: A consumer mobile app requests identity and profile information while also accessing Salesforce data. Which concrete observation should be documented as the most decisive issue?

  1. The API must honor the employee's current permissions and a browser approval step is available.
  2. The vendor needs application-owned credentials rather than human interactive authorization at runtime.
  3. The design equates an OAuth access token with a login identity proof and has no signed identity claims.
  4. The device has a limited interface but can present a short activation code and poll with rate limits.

Explanation

Correct Answer

C:

Best. The decisive observation is: The design equates an OAuth access token with a login identity proof and has no signed identity claims. This is why the design response should be: Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise app needs to act on behalf of a specific employee when reading Salesforce task data. Its relevant condition is: The API must honor the employee's current permissions and a browser approval step is available. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: The design equates an OAuth access token with a login identity proof and has no signed identity claims.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. Its relevant condition is: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: The design equates an OAuth access token with a login identity proof and has no signed identity claims.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Its relevant condition is: The device has a limited interface but can present a short activation code and poll with rate limits. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: The design equates an OAuth access token with a login identity proof and has no signed identity claims.

Question 296

An architect must create an acceptance test after choosing: Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization. For the situation A consumer mobile app requests identity and profile information while also accessing Salesforce data. Which result most directly proves success?

  1. The app verifies user identity via a signed ID token and constrains API permissions separately.
  2. The service obtains time-limited API authorization without interactive user login or stored password.
  3. A user approves the device through a separate browser and the device receives scoped tokens.
  4. The portal obtains user-scoped tokens without receiving the customer's Salesforce password.

Explanation

Correct Answer

A:

Best. The verification target is: The app verifies user identity via a signed ID token and constrains API permissions separately. It tests whether the chosen approach—Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.—actually resolves the specific finding: The design equates an OAuth access token with a login identity proof and has no signed identity claims.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A headless scheduled analytics job reads Salesforce records nightly without a person present. Its relevant condition is: The service holds an approved signing certificate and the Salesforce client app is preauthorized. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: The app verifies user identity via a signed ID token and constrains API permissions separately.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Its relevant condition is: The device has a limited interface but can present a short activation code and poll with rate limits. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: The app verifies user identity via a signed ID token and constrains API permissions separately.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-rendered customer portal needs Salesforce to authorize API calls after a customer signs in. Its relevant condition is: The web server can protect a client secret, receive a registered redirect and exchange a one-time code. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: The app verifies user identity via a signed ID token and constrains API permissions separately.

Question 297

An incident scenario concerns this architecture: A consumer mobile app requests identity and profile information while also accessing Salesforce data. The team has discovered: The design equates an OAuth access token with a login identity proof and has no signed identity claims. Which project risk requires explicit mitigation?

  1. A token issued for one resource is accepted as proof of the person's identity elsewhere.
  2. A user-agent flow is used for automated jobs with no browser or resource owner present.
  3. A broad machine token replaces employee context and exposes unrelated coworkers' tasks.
  4. The TV embeds a Salesforce username and password because its own keyboard is limited.

Explanation

Correct Answer

A:

Best. The most direct failure is: A token issued for one resource is accepted as proof of the person's identity elsewhere. It is a consequence of the documented condition: The design equates an OAuth access token with a login identity proof and has no signed identity claims. A mitigation is: Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. Its relevant condition is: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: A token issued for one resource is accepted as proof of the person's identity elsewhere.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise app needs to act on behalf of a specific employee when reading Salesforce task data. Its relevant condition is: The API must honor the employee's current permissions and a browser approval step is available. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: A token issued for one resource is accepted as proof of the person's identity elsewhere.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Its relevant condition is: The device has a limited interface but can present a short activation code and poll with rate limits. The present case instead turns on: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The direct answer here is: A token issued for one resource is accepted as proof of the person's identity elsewhere.

Question 298

In this fictional project, A partner scheduling app only needs to read a limited set of Salesforce appointment records. The project team has uncovered that The proposed connected-app grant includes broad administrative and object-changing permissions. Which action is best supported by those facts?

  1. Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries.
  2. Require approved application governance, permitted users and explicit authorization policy as appropriate.
  3. Limit approved connected-app scopes and refresh-token policy to the actual portal requirement.
  4. Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.

Explanation

Correct Answer

D:

Best. The most direct action is to configure minimum OAuth scopes and an integration user's restricted object, field and record permissions. It is supported by the specific finding that the proposed connected-app grant includes broad administrative and object-changing permissions. The expected acceptance evidence is: The partner reads approved appointments while other object modifications fail in negative tests.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A sales analytics provider requests both the api and full data privileges for a small reporting use case. Its relevant condition is: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The present case instead turns on: The proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services team must block unknown external apps from gaining access to Salesforce. Its relevant condition is: The connected-app policy currently lets users self-authorize any requesting OAuth client. The present case instead turns on: The proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A Salesforce org provides identity to an external analytics portal that requests both profile and report access. Its relevant condition is: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The present case instead turns on: The proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.

Question 299

An enterprise review begins with this business situation: A partner scheduling app only needs to read a limited set of Salesforce appointment records. Which technical or process signal best identifies the obstacle?

  1. A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations.
  2. The team assumes an OAuth scope can replace all Salesforce profile and sharing controls.
  3. The proposed connected-app grant includes broad administrative and object-changing permissions.
  4. The app registration lists only a development callback address while production uses another host.

Explanation

Correct Answer

C:

Best. The decisive observation is: The proposed connected-app grant includes broad administrative and object-changing permissions. This is why the design response should be: Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A corporate mobile app must access Salesforce but only when installed on managed and approved devices. Its relevant condition is: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The present case instead turns on: The proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: The proposed connected-app grant includes broad administrative and object-changing permissions.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A sales analytics provider requests both the api and full data privileges for a small reporting use case. Its relevant condition is: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The present case instead turns on: The proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: The proposed connected-app grant includes broad administrative and object-changing permissions.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external payroll application requires an OAuth redirect after a user signs into Salesforce. Its relevant condition is: The app registration lists only a development callback address while production uses another host. The present case instead turns on: The proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: The proposed connected-app grant includes broad administrative and object-changing permissions.

Question 300

The team adopts this approach: Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions. The original project scenario is: A partner scheduling app only needs to read a limited set of Salesforce appointment records. Which verification outcome best demonstrates that it worked?

  1. Salesforce redirects authorization results solely to approved application destinations.
  2. Authorized report queries work but sensitive objects and record edits remain denied.
  3. Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.
  4. The partner reads approved appointments while other object modifications fail in negative tests.

Explanation

Correct Answer

D:

Best. The verification target is: The partner reads approved appointments while other object modifications fail in negative tests. It tests whether the chosen approach—Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.—actually resolves the specific finding: The proposed connected-app grant includes broad administrative and object-changing permissions.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external payroll application requires an OAuth redirect after a user signs into Salesforce. Its relevant condition is: The app registration lists only a development callback address while production uses another host. The present case instead turns on: The proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: The partner reads approved appointments while other object modifications fail in negative tests.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A sales analytics provider requests both the api and full data privileges for a small reporting use case. Its relevant condition is: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The present case instead turns on: The proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: The partner reads approved appointments while other object modifications fail in negative tests.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A corporate mobile app must access Salesforce but only when installed on managed and approved devices. Its relevant condition is: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The present case instead turns on: The proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: The partner reads approved appointments while other object modifications fail in negative tests.

Certified Platform Identity and Access Management Architect Practice Tests