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 34

Question 330

An integration architect receives this requirement: A web application uses Salesforce OAuth refresh tokens to maintain approved user sessions. A technical discovery also finds: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. Which response most directly addresses the present constraint?

  1. Treat bearer tokens as credentials, protect storage, minimize lifetime and enable token revocation.
  2. Move confidential app credentials to a trusted backend and select PKCE for public clients.
  3. Set issuer, subject, audience, expiry and signature according to the registered target authorization server.
  4. Apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout.

Explanation

Correct Answer

D:

Best. The most direct action is to apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout. It is supported by the specific finding that the app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The expected acceptance evidence is: The application renews access only for current approved users and destroys tokens at session termination.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting client stores OAuth access tokens in a database without encryption. Its relevant condition is: Tokens can be stolen from backups and used until expiry even if a password is changed. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: Apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A developer includes client secrets in front-end JavaScript for a customer self-service portal. Its relevant condition is: Anyone loading the page can inspect the embedded secret and use it from another device. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: Apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A backend integration sends a signed JWT to obtain a Salesforce access token. Its relevant condition is: The JWT has the correct private key but an audience string for a different Salesforce login host. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: Apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout.

Question 331

Consider the following hypothetical Salesforce initiative: A web application uses Salesforce OAuth refresh tokens to maintain approved user sessions. Which evidence would most strongly explain the current integration weakness?

  1. Archived logs retain usable bearer tokens after normal application traffic has ended.
  2. The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding.
  3. The JWT has the correct private key but an audience string for a different Salesforce login host.
  4. An attacker may trick a browser into completing an unrelated authorization transaction.

Explanation

Correct Answer

B:

Best. The decisive observation is: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. This is why the design response should be: Apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An integration logs full Authorization headers to simplify debugging of API failures. Its relevant condition is: Archived logs retain usable bearer tokens after normal application traffic has ended. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A backend integration sends a signed JWT to obtain a Salesforce access token. Its relevant condition is: The JWT has the correct private key but an audience string for a different Salesforce login host. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An API client uses OAuth authorization codes but omits the state parameter. Its relevant condition is: An attacker may trick a browser into completing an unrelated authorization transaction. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding.

Question 332

Review this change: Apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout. It addresses a project where A web application uses Salesforce OAuth refresh tokens to maintain approved user sessions. Which result should appear in integration acceptance evidence?

  1. The application renews access only for current approved users and destroys tokens at session termination.
  2. The browser performs its supported login flow without exposing shared secrets in delivered code.
  3. Only authorization responses associated with the expected initiating browser are accepted.
  4. The token endpoint issues access only for the intended Salesforce org and preauthorized subject.

Explanation

Correct Answer

A:

Best. The verification target is: The application renews access only for current approved users and destroys tokens at session termination. It tests whether the chosen approach—Apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout.—actually resolves the specific finding: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A developer includes client secrets in front-end JavaScript for a customer self-service portal. Its relevant condition is: Anyone loading the page can inspect the embedded secret and use it from another device. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: The application renews access only for current approved users and destroys tokens at session termination.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An API client uses OAuth authorization codes but omits the state parameter. Its relevant condition is: An attacker may trick a browser into completing an unrelated authorization transaction. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: The application renews access only for current approved users and destroys tokens at session termination.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A backend integration sends a signed JWT to obtain a Salesforce access token. Its relevant condition is: The JWT has the correct private key but an audience string for a different Salesforce login host. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: The application renews access only for current approved users and destroys tokens at session termination.

Question 333

Suppose the integration design proceeds without correcting this issue: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. In the environment A web application uses Salesforce OAuth refresh tokens to maintain approved user sessions. What should the risk register emphasize?

  1. A disconnected partner continues syncing data through an unrevoked refresh token.
  2. A deleted employee's refresh token silently recreates API access for months.
  3. One copied JavaScript bundle exposes the application credential for all customers.
  4. OAuth login CSRF links a victim session to an attacker's authorization result.

Explanation

Correct Answer

B:

Best. The most direct failure is: A deleted employee's refresh token silently recreates API access for months. It is a consequence of the documented condition: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. A mitigation is: Apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner wants users to revoke a connected app's access without changing their Salesforce password. Its relevant condition is: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: A deleted employee's refresh token silently recreates API access for months.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A developer includes client secrets in front-end JavaScript for a customer self-service portal. Its relevant condition is: Anyone loading the page can inspect the embedded secret and use it from another device. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: A deleted employee's refresh token silently recreates API access for months.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An API client uses OAuth authorization codes but omits the state parameter. Its relevant condition is: An attacker may trick a browser into completing an unrelated authorization transaction. The present case instead turns on: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The direct answer here is: A deleted employee's refresh token silently recreates API access for months.

Question 334

An architecture board reviews a proposed Salesforce integration. Context: A backend integration sends a signed JWT to obtain a Salesforce access token. Finding: The JWT has the correct private key but an audience string for a different Salesforce login host. Which decision best resolves the concern?

  1. Revoke outstanding grants or tokens, inspect active sessions and correlate subsequent API events.
  2. Set issuer, subject, audience, expiry and signature according to the registered target authorization server.
  3. Apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout.
  4. Move confidential app credentials to a trusted backend and select PKCE for public clients.

Explanation

Correct Answer

B:

Best. The most direct action is to set issuer, subject, audience, expiry and signature according to the registered target authorization server. It is supported by the specific finding that the JWT has the correct private key but an audience string for a different Salesforce login host. The expected acceptance evidence is: The token endpoint issues access only for the intended Salesforce org and preauthorized subject.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security response team revokes a malicious connected app but sees continued API activity afterward. Its relevant condition is: The org has not confirmed whether tokens and application sessions were actually invalidated. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: Set issuer, subject, audience, expiry and signature according to the registered target authorization server.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A web application uses Salesforce OAuth refresh tokens to maintain approved user sessions. Its relevant condition is: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: Set issuer, subject, audience, expiry and signature according to the registered target authorization server.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A developer includes client secrets in front-end JavaScript for a customer self-service portal. Its relevant condition is: Anyone loading the page can inspect the embedded secret and use it from another device. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: Set issuer, subject, audience, expiry and signature according to the registered target authorization server.

Question 335

A design workshop describes this environment: A backend integration sends a signed JWT to obtain a Salesforce access token. Which concrete observation should be documented as the most decisive issue?

  1. The JWT has the correct private key but an audience string for a different Salesforce login host.
  2. The org has not confirmed whether tokens and application sessions were actually invalidated.
  3. Anyone loading the page can inspect the embedded secret and use it from another device.
  4. Tokens can be stolen from backups and used until expiry even if a password is changed.

Explanation

Correct Answer

A:

Best. The decisive observation is: The JWT has the correct private key but an audience string for a different Salesforce login host. This is why the design response should be: Set issuer, subject, audience, expiry and signature according to the registered target authorization server.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security response team revokes a malicious connected app but sees continued API activity afterward. Its relevant condition is: The org has not confirmed whether tokens and application sessions were actually invalidated. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: The JWT has the correct private key but an audience string for a different Salesforce login host.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A developer includes client secrets in front-end JavaScript for a customer self-service portal. Its relevant condition is: Anyone loading the page can inspect the embedded secret and use it from another device. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: The JWT has the correct private key but an audience string for a different Salesforce login host.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting client stores OAuth access tokens in a database without encryption. Its relevant condition is: Tokens can be stolen from backups and used until expiry even if a password is changed. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: The JWT has the correct private key but an audience string for a different Salesforce login host.

Question 336

An architect must create an acceptance test after choosing: Set issuer, subject, audience, expiry and signature according to the registered target authorization server. For the situation A backend integration sends a signed JWT to obtain a Salesforce access token. Which result most directly proves success?

  1. The browser performs its supported login flow without exposing shared secrets in delivered code.
  2. Stolen raw backups do not expose reusable token strings, and an incident can invalidate issued tokens.
  3. Revoked tokens can no longer be used for Salesforce API calls after the expected invalidation.
  4. The token endpoint issues access only for the intended Salesforce org and preauthorized subject.

Explanation

Correct Answer

D:

Best. The verification target is: The token endpoint issues access only for the intended Salesforce org and preauthorized subject. It tests whether the chosen approach—Set issuer, subject, audience, expiry and signature according to the registered target authorization server.—actually resolves the specific finding: The JWT has the correct private key but an audience string for a different Salesforce login host.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A developer includes client secrets in front-end JavaScript for a customer self-service portal. Its relevant condition is: Anyone loading the page can inspect the embedded secret and use it from another device. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: The token endpoint issues access only for the intended Salesforce org and preauthorized subject.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting client stores OAuth access tokens in a database without encryption. Its relevant condition is: Tokens can be stolen from backups and used until expiry even if a password is changed. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: The token endpoint issues access only for the intended Salesforce org and preauthorized subject.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner wants users to revoke a connected app's access without changing their Salesforce password. Its relevant condition is: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: The token endpoint issues access only for the intended Salesforce org and preauthorized subject.

Question 337

An incident scenario concerns this architecture: A backend integration sends a signed JWT to obtain a Salesforce access token. The team has discovered: The JWT has the correct private key but an audience string for a different Salesforce login host. Which project risk requires explicit mitigation?

  1. A correctly signed JWT is reused against an unapproved token endpoint.
  2. A person with log-view permission can replay tokens to access Salesforce records.
  3. OAuth login CSRF links a victim session to an attacker's authorization result.
  4. Long-lived bearer tokens become a direct route to CRM API data without password verification.

Explanation

Correct Answer

A:

Best. The most direct failure is: A correctly signed JWT is reused against an unapproved token endpoint. It is a consequence of the documented condition: The JWT has the correct private key but an audience string for a different Salesforce login host. A mitigation is: Set issuer, subject, audience, expiry and signature according to the registered target authorization server.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An integration logs full Authorization headers to simplify debugging of API failures. Its relevant condition is: Archived logs retain usable bearer tokens after normal application traffic has ended. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: A correctly signed JWT is reused against an unapproved token endpoint.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An API client uses OAuth authorization codes but omits the state parameter. Its relevant condition is: An attacker may trick a browser into completing an unrelated authorization transaction. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: A correctly signed JWT is reused against an unapproved token endpoint.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting client stores OAuth access tokens in a database without encryption. Its relevant condition is: Tokens can be stolen from backups and used until expiry even if a password is changed. The present case instead turns on: The JWT has the correct private key but an audience string for a different Salesforce login host. The direct answer here is: A correctly signed JWT is reused against an unapproved token endpoint.

Question 338

In this fictional project, A partner wants users to revoke a connected app's access without changing their Salesforce password. The project team has uncovered that The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. Which action is best supported by those facts?

  1. Implement supported OAuth token revocation and application disconnect handling for authorized users.
  2. Bind login initiation to the callback using state and appropriate PKCE or anti-forgery validation.
  3. Apply minimum refresh scope, protected storage, token lifecycle management and revocation on logout.
  4. Move confidential app credentials to a trusted backend and select PKCE for public clients.

Explanation

Correct Answer

A:

Best. The most direct action is to implement supported OAuth token revocation and application disconnect handling for authorized users. It is supported by the specific finding that the existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The expected acceptance evidence is: Revoked tokens can no longer be used for Salesforce API calls after the expected invalidation.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An API client uses OAuth authorization codes but omits the state parameter. Its relevant condition is: An attacker may trick a browser into completing an unrelated authorization transaction. The present case instead turns on: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The direct answer here is: Implement supported OAuth token revocation and application disconnect handling for authorized users.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A web application uses Salesforce OAuth refresh tokens to maintain approved user sessions. Its relevant condition is: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The present case instead turns on: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The direct answer here is: Implement supported OAuth token revocation and application disconnect handling for authorized users.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A developer includes client secrets in front-end JavaScript for a customer self-service portal. Its relevant condition is: Anyone loading the page can inspect the embedded secret and use it from another device. The present case instead turns on: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The direct answer here is: Implement supported OAuth token revocation and application disconnect handling for authorized users.

Question 339

An enterprise review begins with this business situation: A partner wants users to revoke a connected app's access without changing their Salesforce password. Which technical or process signal best identifies the obstacle?

  1. The org has not confirmed whether tokens and application sessions were actually invalidated.
  2. The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens.
  3. The JWT has the correct private key but an audience string for a different Salesforce login host.
  4. Archived logs retain usable bearer tokens after normal application traffic has ended.

Explanation

Correct Answer

B:

Best. The decisive observation is: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. This is why the design response should be: Implement supported OAuth token revocation and application disconnect handling for authorized users.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security response team revokes a malicious connected app but sees continued API activity afterward. Its relevant condition is: The org has not confirmed whether tokens and application sessions were actually invalidated. The present case instead turns on: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The direct answer here is: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A backend integration sends a signed JWT to obtain a Salesforce access token. Its relevant condition is: The JWT has the correct private key but an audience string for a different Salesforce login host. The present case instead turns on: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The direct answer here is: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An integration logs full Authorization headers to simplify debugging of API failures. Its relevant condition is: Archived logs retain usable bearer tokens after normal application traffic has ended. The present case instead turns on: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The direct answer here is: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens.

Question 340

The team adopts this approach: Implement supported OAuth token revocation and application disconnect handling for authorized users. The original project scenario is: A partner wants users to revoke a connected app's access without changing their Salesforce password. Which verification outcome best demonstrates that it worked?

  1. Revoked tokens can no longer be used for Salesforce API calls after the expected invalidation.
  2. Stolen raw backups do not expose reusable token strings, and an incident can invalidate issued tokens.
  3. Engineers can investigate failed requests without retaining secrets in permanent logs.
  4. The application renews access only for current approved users and destroys tokens at session termination.

Explanation

Correct Answer

A:

Best. The verification target is: Revoked tokens can no longer be used for Salesforce API calls after the expected invalidation. It tests whether the chosen approach—Implement supported OAuth token revocation and application disconnect handling for authorized users.—actually resolves the specific finding: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting client stores OAuth access tokens in a database without encryption. Its relevant condition is: Tokens can be stolen from backups and used until expiry even if a password is changed. The present case instead turns on: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The direct answer here is: Revoked tokens can no longer be used for Salesforce API calls after the expected invalidation.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An integration logs full Authorization headers to simplify debugging of API failures. Its relevant condition is: Archived logs retain usable bearer tokens after normal application traffic has ended. The present case instead turns on: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The direct answer here is: Revoked tokens can no longer be used for Salesforce API calls after the expected invalidation.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A web application uses Salesforce OAuth refresh tokens to maintain approved user sessions. Its relevant condition is: The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding. The present case instead turns on: The existing design assumes deleting a browser cookie also cancels OAuth refresh tokens. The direct answer here is: Revoked tokens can no longer be used for Salesforce API calls after the expected invalidation.

Certified Platform Identity and Access Management Architect Practice Tests