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 33

Question 320

An architect must create an acceptance test after choosing: Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries. For the situation A sales analytics provider requests both the api and full data privileges for a small reporting use case. Which result most directly proves success?

  1. Salesforce redirects authorization results solely to approved application destinations.
  2. Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.
  3. A user approves the device through a separate browser and the device receives scoped tokens.
  4. Authorized report queries work but sensitive objects and record edits remain denied.

Explanation

Correct Answer

D:

Best. The verification target is: Authorized report queries work but sensitive objects and record edits remain denied. It tests whether the chosen approach—Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries.—actually resolves the specific finding: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls.

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 team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: Authorized report queries work but sensitive objects and record edits remain denied.

B:

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 team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: Authorized report queries work but sensitive objects and record edits remain denied.

C:

Not best for this scenario. This option is associated with another type of requirement: 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 team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: Authorized report queries work but sensitive objects and record edits remain denied.

Question 321

An incident scenario concerns this architecture: A sales analytics provider requests both the api and full data privileges for a small reporting use case. The team has discovered: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. Which project risk requires explicit mitigation?

  1. A valid OAuth token becomes sufficient to bypass the organization's device restrictions.
  2. App registration scopes become a false justification for granting system administrator access.
  3. One permissive connected-app setting exposes data in subsidiaries that never approved it.
  4. A wildcard redirect exposes an authorization code to an attacker-controlled host.

Explanation

Correct Answer

B:

Best. The most direct failure is: App registration scopes become a false justification for granting system administrator access. It is a consequence of the documented condition: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. A mitigation is: Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries.

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 team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: App registration scopes become a false justification for granting system administrator access.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A vendor-built Salesforce connected app is being rolled out across subsidiaries. Its relevant condition is: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The present case instead turns on: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: App registration scopes become a false justification for granting system administrator access.

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 team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: App registration scopes become a false justification for granting system administrator access.

Question 322

In this fictional project, A vendor-built Salesforce connected app is being rolled out across subsidiaries. The project team has uncovered that Each subsidiary needs approved policy settings and independent review of scopes and permitted users. Which action is best supported by those facts?

  1. Use controlled application approvals, least privilege, token policy and per-org deployment documentation.
  2. Limit approved connected-app scopes and refresh-token policy to the actual portal requirement.
  3. Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.
  4. Apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario.

Explanation

Correct Answer

A:

Best. The most direct action is to use controlled application approvals, least privilege, token policy and per-org deployment documentation. It is supported by the specific finding that Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The expected acceptance evidence is: The same vendor app is only usable by explicitly approved populations under each org's policy.

Incorrect Answers

B:

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: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: Use controlled application approvals, least privilege, token policy and per-org deployment documentation.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner scheduling app only needs to read a limited set of Salesforce appointment records. Its relevant condition is: The proposed connected-app grant includes broad administrative and object-changing permissions. The present case instead turns on: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: Use controlled application approvals, least privilege, token policy and per-org deployment documentation.

D:

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: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: Use controlled application approvals, least privilege, token policy and per-org deployment documentation.

Question 323

An enterprise review begins with this business situation: A vendor-built Salesforce connected app is being rolled out across subsidiaries. Which technical or process signal best identifies the obstacle?

  1. The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session.
  2. A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations.
  3. The team assumes an OAuth scope can replace all Salesforce profile and sharing controls.
  4. Each subsidiary needs approved policy settings and independent review of scopes and permitted users.

Explanation

Correct Answer

D:

Best. The decisive observation is: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. This is why the design response should be: Use controlled application approvals, least privilege, token policy and per-org deployment documentation.

Incorrect Answers

A:

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: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: Each subsidiary needs approved policy settings and independent review of scopes and permitted users.

B:

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: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: Each subsidiary needs approved policy settings and independent review of scopes and permitted users.

C:

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: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: Each subsidiary needs approved policy settings and independent review of scopes and permitted users.

Question 324

The team adopts this approach: Use controlled application approvals, least privilege, token policy and per-org deployment documentation. The original project scenario is: A vendor-built Salesforce connected app is being rolled out across subsidiaries. Which verification outcome best demonstrates that it worked?

  1. The same vendor app is only usable by explicitly approved populations under each org's policy.
  2. Salesforce redirects authorization results solely to approved application destinations.
  3. The partner reads approved appointments while other object modifications fail in negative tests.
  4. Identity claims and report access work while unnecessary offline privileges are unavailable.

Explanation

Correct Answer

A:

Best. The verification target is: The same vendor app is only usable by explicitly approved populations under each org's policy. It tests whether the chosen approach—Use controlled application approvals, least privilege, token policy and per-org deployment documentation.—actually resolves the specific finding: Each subsidiary needs approved policy settings and independent review of scopes and permitted users.

Incorrect Answers

B:

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: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: The same vendor app is only usable by explicitly approved populations under each org's policy.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner scheduling app only needs to read a limited set of Salesforce appointment records. Its relevant condition is: The proposed connected-app grant includes broad administrative and object-changing permissions. The present case instead turns on: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: The same vendor app is only usable by explicitly approved populations under each org's policy.

D:

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: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: The same vendor app is only usable by explicitly approved populations under each org's policy.

Question 325

A project manager declines to address this finding: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The related project is: A vendor-built Salesforce connected app is being rolled out across subsidiaries. Which consequence most directly follows?

  1. App registration scopes become a false justification for granting system administrator access.
  2. A phishing app persuades an employee to grant API access without corporate review.
  3. One permissive connected-app setting exposes data in subsidiaries that never approved it.
  4. A valid OAuth token becomes sufficient to bypass the organization's device restrictions.

Explanation

Correct Answer

C:

Best. The most direct failure is: One permissive connected-app setting exposes data in subsidiaries that never approved it. It is a consequence of the documented condition: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. A mitigation is: Use controlled application approvals, least privilege, token policy and per-org deployment documentation.

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: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: One permissive connected-app setting exposes data in subsidiaries that never approved it.

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: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: One permissive connected-app setting exposes data in subsidiaries that never approved it.

D:

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: Each subsidiary needs approved policy settings and independent review of scopes and permitted users. The direct answer here is: One permissive connected-app setting exposes data in subsidiaries that never approved it.

Question 326

An architecture board reviews a proposed Salesforce integration. Context: An external reporting client stores OAuth access tokens in a database without encryption. Finding: Tokens can be stolen from backups and used until expiry even if a password is changed. Which decision best resolves the concern?

  1. Treat bearer tokens as credentials, protect storage, minimize lifetime and enable token revocation.
  2. Bind login initiation to the callback using state and appropriate PKCE or anti-forgery validation.
  3. Redact authentication headers and retain only safe correlation data with controlled diagnostic access.
  4. Implement supported OAuth token revocation and application disconnect handling for authorized users.

Explanation

Correct Answer

A:

Best. The most direct action is to treat bearer tokens as credentials, protect storage, minimize lifetime and enable token revocation. It is supported by the specific finding that Tokens can be stolen from backups and used until expiry even if a password is changed. The expected acceptance evidence is: Stolen raw backups do not expose reusable token strings, and an incident can invalidate issued tokens.

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Treat bearer tokens as credentials, protect storage, minimize lifetime and enable token revocation.

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Treat bearer tokens as credentials, protect storage, minimize lifetime and enable token revocation.

D:

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Treat bearer tokens as credentials, protect storage, minimize lifetime and enable token revocation.

Question 327

A design workshop describes this environment: An external reporting client stores OAuth access tokens in a database without encryption. Which concrete observation should be documented as the most decisive issue?

  1. Tokens can be stolen from backups and used until expiry even if a password is changed.
  2. The app lacks a plan for secure refresh-token storage, rotation policy and account offboarding.
  3. Anyone loading the page can inspect the embedded secret and use it from another device.
  4. The JWT has the correct private key but an audience string for a different Salesforce login host.

Explanation

Correct Answer

A:

Best. The decisive observation is: Tokens can be stolen from backups and used until expiry even if a password is changed. This is why the design response should be: Treat bearer tokens as credentials, protect storage, minimize lifetime and enable token revocation.

Incorrect Answers

B:

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Tokens can be stolen from backups and used until expiry even if a password is changed.

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Tokens can be stolen from backups and used until expiry even if a password is changed.

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Tokens can be stolen from backups and used until expiry even if a password is changed.

Question 328

An architect must create an acceptance test after choosing: Treat bearer tokens as credentials, protect storage, minimize lifetime and enable token revocation. For the situation An external reporting client stores OAuth access tokens in a database without encryption. Which result most directly proves success?

  1. Only authorization responses associated with the expected initiating browser are accepted.
  2. All identified app access paths are closed and follow-up events confirm containment.
  3. Stolen raw backups do not expose reusable token strings, and an incident can invalidate issued tokens.
  4. Revoked tokens can no longer be used for Salesforce API calls after the expected invalidation.

Explanation

Correct Answer

C:

Best. The verification target is: Stolen raw backups do not expose reusable token strings, and an incident can invalidate issued tokens. It tests whether the chosen approach—Treat bearer tokens as credentials, protect storage, minimize lifetime and enable token revocation.—actually resolves the specific finding: Tokens can be stolen from backups and used until expiry even if a password is changed.

Incorrect Answers

A:

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Stolen raw backups do not expose reusable token strings, and an incident can invalidate issued tokens.

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Stolen raw backups do not expose reusable token strings, and an incident can invalidate issued tokens.

D:

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Stolen raw backups do not expose reusable token strings, and an incident can invalidate issued tokens.

Question 329

An incident scenario concerns this architecture: An external reporting client stores OAuth access tokens in a database without encryption. The team has discovered: Tokens can be stolen from backups and used until expiry even if a password is changed. Which project risk requires explicit mitigation?

  1. Policy changes block new consent while previously issued bearer tokens continue to work.
  2. A correctly signed JWT is reused against an unapproved token endpoint.
  3. One copied JavaScript bundle exposes the application credential for all customers.
  4. Long-lived bearer tokens become a direct route to CRM API data without password verification.

Explanation

Correct Answer

D:

Best. The most direct failure is: Long-lived bearer tokens become a direct route to CRM API data without password verification. It is a consequence of the documented condition: Tokens can be stolen from backups and used until expiry even if a password is changed. A mitigation is: Treat bearer tokens as credentials, protect storage, minimize lifetime and enable token revocation.

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Long-lived bearer tokens become a direct route to CRM API data without password verification.

B:

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Long-lived bearer tokens become a direct route to CRM API data without password verification.

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: Tokens can be stolen from backups and used until expiry even if a password is changed. The direct answer here is: Long-lived bearer tokens become a direct route to CRM API data without password verification.

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.

Certified Platform Identity and Access Management Architect Practice Tests