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 31

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.

Question 301

A project manager declines to address this finding: The proposed connected-app grant includes broad administrative and object-changing permissions. The related project is: A partner scheduling app only needs to read a limited set of Salesforce appointment records. Which consequence most directly follows?

  1. An overbroad app scope is mistaken for permission to all confidential business data.
  2. A valid OAuth token becomes sufficient to bypass the organization's device restrictions.
  3. App registration scopes become a false justification for granting system administrator access.
  4. An excessive refresh permission persists beyond the business session's lifetime.

Explanation

Correct Answer

A:

Best. The most direct failure is: An overbroad app scope is mistaken for permission to all confidential business data. It is a consequence of the documented condition: The proposed connected-app grant includes broad administrative and object-changing permissions. A mitigation is: Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.

Incorrect Answers

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 proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: An overbroad app scope is mistaken for permission to all confidential business data.

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: The proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: An overbroad app scope is mistaken for permission to all confidential business data.

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: The proposed connected-app grant includes broad administrative and object-changing permissions. The direct answer here is: An overbroad app scope is mistaken for permission to all confidential business data.

Question 302

An architecture board reviews a proposed Salesforce integration. Context: A financial services team must block unknown external apps from gaining access to Salesforce. Finding: The connected-app policy currently lets users self-authorize any requesting OAuth client. Which decision best resolves the concern?

  1. Require approved application governance, permitted users and explicit authorization policy as appropriate.
  2. Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries.
  3. Apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario.
  4. Register exact valid callback URLs in the connected-app configuration and test the correct tenant.

Explanation

Correct Answer

A:

Best. The most direct action is to require approved application governance, permitted users and explicit authorization policy as appropriate. It is supported by the specific finding that the connected-app policy currently lets users self-authorize any requesting OAuth client. The expected acceptance evidence is: Only authorized client applications obtain tokens and app access is auditable.

Incorrect Answers

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 connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: Require approved application governance, permitted users and explicit authorization policy as appropriate.

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 connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: Require approved application governance, permitted users and explicit authorization policy as appropriate.

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 connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: Require approved application governance, permitted users and explicit authorization policy as appropriate.

Question 303

A design workshop describes this environment: A financial services team must block unknown external apps from gaining access to Salesforce. Which concrete observation should be documented as the most decisive issue?

  1. The app registration lists only a development callback address while production uses another host.
  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 connected-app policy currently lets users self-authorize any requesting OAuth client.

Explanation

Correct Answer

D:

Best. The decisive observation is: The connected-app policy currently lets users self-authorize any requesting OAuth client. This is why the design response should be: Require approved application governance, permitted users and explicit authorization policy as appropriate.

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 connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: The connected-app policy currently lets users self-authorize any requesting OAuth client.

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 connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: The connected-app policy currently lets users self-authorize any requesting OAuth client.

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: The connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: The connected-app policy currently lets users self-authorize any requesting OAuth client.

Question 304

An architect must create an acceptance test after choosing: Require approved application governance, permitted users and explicit authorization policy as appropriate. For the situation A financial services team must block unknown external apps from gaining access to Salesforce. Which result most directly proves success?

  1. Authorized report queries work but sensitive objects and record edits remain denied.
  2. Salesforce redirects authorization results solely to approved application destinations.
  3. Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.
  4. Only authorized client applications obtain tokens and app access is auditable.

Explanation

Correct Answer

D:

Best. The verification target is: Only authorized client applications obtain tokens and app access is auditable. It tests whether the chosen approach—Require approved application governance, permitted users and explicit authorization policy as appropriate.—actually resolves the specific finding: The connected-app policy currently lets users self-authorize any requesting OAuth client.

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 connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: Only authorized client applications obtain tokens and app access is auditable.

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: The connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: Only authorized client applications obtain tokens and app access is auditable.

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 connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: Only authorized client applications obtain tokens and app access is auditable.

Question 305

An incident scenario concerns this architecture: A financial services team must block unknown external apps from gaining access to Salesforce. The team has discovered: The connected-app policy currently lets users self-authorize any requesting OAuth client. Which project risk requires explicit mitigation?

  1. A wildcard redirect exposes an authorization code to an attacker-controlled host.
  2. A phishing app persuades an employee to grant API access without corporate review.
  3. App registration scopes become a false justification for granting system administrator access.
  4. An excessive refresh permission persists beyond the business session's lifetime.

Explanation

Correct Answer

B:

Best. The most direct failure is: A phishing app persuades an employee to grant API access without corporate review. It is a consequence of the documented condition: The connected-app policy currently lets users self-authorize any requesting OAuth client. A mitigation is: Require approved application governance, permitted users and explicit authorization policy as appropriate.

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 connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: A phishing app persuades an employee to grant API access without corporate review.

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: The connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: A phishing app persuades an employee to grant API access without corporate review.

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: The connected-app policy currently lets users self-authorize any requesting OAuth client. The direct answer here is: A phishing app persuades an employee to grant API access without corporate review.

Question 306

In this fictional project, A Salesforce org provides identity to an external analytics portal that requests both profile and report access. The project team has uncovered that The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. Which action is best supported by those facts?

  1. Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.
  2. Register exact valid callback URLs in the connected-app configuration and test the correct tenant.
  3. Require approved application governance, permitted users and explicit authorization policy as appropriate.
  4. Limit approved connected-app scopes and refresh-token policy to the actual portal requirement.

Explanation

Correct Answer

D:

Best. The most direct action is to limit approved connected-app scopes and refresh-token policy to the actual portal requirement. It is supported by the specific finding that the portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The expected acceptance evidence is: Identity claims and report access work while unnecessary offline privileges are unavailable.

Incorrect Answers

A:

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: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: Limit approved connected-app scopes and refresh-token policy to the actual portal requirement.

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: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: Limit approved connected-app scopes and refresh-token policy to the actual portal requirement.

C:

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 portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: Limit approved connected-app scopes and refresh-token policy to the actual portal requirement.

Question 307

An enterprise review begins with this business situation: A Salesforce org provides identity to an external analytics portal that requests both profile and report access. 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. The app registration lists only a development callback address while production uses another host.
  3. Each subsidiary needs approved policy settings and independent review of scopes and permitted users.
  4. The team assumes an OAuth scope can replace all Salesforce profile and sharing controls.

Explanation

Correct Answer

A:

Best. The decisive observation is: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. This is why the design response should be: Limit approved connected-app scopes and refresh-token policy to the actual portal requirement.

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: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session.

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 portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session.

D:

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 portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session.

Question 308

The team adopts this approach: Limit approved connected-app scopes and refresh-token policy to the actual portal requirement. The original project scenario is: A Salesforce org provides identity to an external analytics portal that requests both profile and report access. Which verification outcome best demonstrates that it worked?

  1. Identity claims and report access work while unnecessary offline privileges are unavailable.
  2. Salesforce redirects authorization results solely to approved application destinations.
  3. Only authorized client applications obtain tokens and app access is auditable.
  4. Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.

Explanation

Correct Answer

A:

Best. The verification target is: Identity claims and report access work while unnecessary offline privileges are unavailable. It tests whether the chosen approach—Limit approved connected-app scopes and refresh-token policy to the actual portal requirement.—actually resolves the specific finding: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session.

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: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: Identity claims and report access work while unnecessary offline privileges are unavailable.

C:

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 portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: Identity claims and report access work while unnecessary offline privileges are unavailable.

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: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: Identity claims and report access work while unnecessary offline privileges are unavailable.

Question 309

A project manager declines to address this finding: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The related project is: A Salesforce org provides identity to an external analytics portal that requests both profile and report access. Which consequence most directly follows?

  1. An excessive refresh permission persists beyond the business session's lifetime.
  2. App registration scopes become a false justification for granting system administrator access.
  3. An overbroad app scope is mistaken for permission to all confidential business data.
  4. A wildcard redirect exposes an authorization code to an attacker-controlled host.

Explanation

Correct Answer

A:

Best. The most direct failure is: An excessive refresh permission persists beyond the business session's lifetime. It is a consequence of the documented condition: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. A mitigation is: Limit approved connected-app scopes and refresh-token policy to the actual portal requirement.

Incorrect Answers

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 portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: An excessive refresh permission persists beyond the business session's lifetime.

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: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: An excessive refresh permission persists beyond the business session's lifetime.

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 portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The direct answer here is: An excessive refresh permission persists beyond the business session's lifetime.

Question 310

An integration architect receives this requirement: An external payroll application requires an OAuth redirect after a user signs into Salesforce. A technical discovery also finds: The app registration lists only a development callback address while production uses another host. Which response most directly addresses the present constraint?

  1. Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.
  2. Use controlled application approvals, least privilege, token policy and per-org deployment documentation.
  3. Register exact valid callback URLs in the connected-app configuration and test the correct tenant.
  4. Apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario.

Explanation

Correct Answer

C:

Best. The most direct action is to register exact valid callback URLs in the connected-app configuration and test the correct tenant. It is supported by the specific finding that the app registration lists only a development callback address while production uses another host. The expected acceptance evidence is: Salesforce redirects authorization results solely to approved application destinations.

Incorrect Answers

A:

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: The app registration lists only a development callback address while production uses another host. The direct answer here is: Register exact valid callback URLs in the connected-app configuration and test the correct tenant.

B:

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 app registration lists only a development callback address while production uses another host. The direct answer here is: Register exact valid callback URLs in the connected-app configuration and test the correct tenant.

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: The app registration lists only a development callback address while production uses another host. The direct answer here is: Register exact valid callback URLs in the connected-app configuration and test the correct tenant.

Certified Platform Identity and Access Management Architect Practice Tests