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 29

Question 280

A solution review asks whether this control is effective: Choose authorization code with PKCE and a system browser with a securely registered redirect. The business setting is: A native mobile app runs on personally owned phones and invokes Salesforce APIs for the signed-in user. What should a demonstrable successful outcome be?

  1. The service obtains time-limited API authorization without interactive user login or stored password.
  2. The app verifies user identity via a signed ID token and constrains API permissions separately.
  3. A user approves the device through a separate browser and the device receives scoped tokens.
  4. The user grants limited API access and the app never exposes a reusable shared secret.

Explanation

Correct Answer

D:

Best. The verification target is: The user grants limited API access and the app never exposes a reusable shared secret. It tests whether the chosen approach—Choose authorization code with PKCE and a system browser with a securely registered redirect.—actually resolves the specific finding: The application cannot safely keep a client secret and may be attacked through intercepted redirects.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A headless scheduled analytics job reads Salesforce records nightly without a person present. Its relevant condition is: The service holds an approved signing certificate and the Salesforce client app is preauthorized. The present case instead turns on: The application cannot safely keep a client secret and may be attacked through intercepted redirects. The direct answer here is: The user grants limited API access and the app never exposes a reusable shared secret.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consumer mobile app requests identity and profile information while also accessing Salesforce data. Its relevant condition is: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The present case instead turns on: The application cannot safely keep a client secret and may be attacked through intercepted redirects. The direct answer here is: The user grants limited API access and the app never exposes a reusable shared secret.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Its relevant condition is: The device has a limited interface but can present a short activation code and poll with rate limits. The present case instead turns on: The application cannot safely keep a client secret and may be attacked through intercepted redirects. The direct answer here is: The user grants limited API access and the app never exposes a reusable shared secret.

Question 281

A Salesforce integration initiative faces this situation: A native mobile app runs on personally owned phones and invokes Salesforce APIs for the signed-in user. The critical observation is: The application cannot safely keep a client secret and may be attacked through intercepted redirects. What failure is most likely if it is ignored?

  1. A user-agent flow is used for automated jobs with no browser or resource owner present.
  2. An implicit browser token is used where a secure server-side exchange is readily available.
  3. A shared device inherits the previous employee's refresh token and transaction rights.
  4. A bundled client secret is treated as confidential merely because it is shipped inside an app binary.

Explanation

Correct Answer

D:

Best. The most direct failure is: A bundled client secret is treated as confidential merely because it is shipped inside an app binary. It is a consequence of the documented condition: The application cannot safely keep a client secret and may be attacked through intercepted redirects. A mitigation is: Choose authorization code with PKCE and a system browser with a securely registered redirect.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. Its relevant condition is: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The present case instead turns on: The application cannot safely keep a client secret and may be attacked through intercepted redirects. The direct answer here is: A bundled client secret is treated as confidential merely because it is shipped inside an app binary.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-rendered customer portal needs Salesforce to authorize API calls after a customer signs in. Its relevant condition is: The web server can protect a client secret, receive a registered redirect and exchange a one-time code. The present case instead turns on: The application cannot safely keep a client secret and may be attacked through intercepted redirects. The direct answer here is: A bundled client secret is treated as confidential merely because it is shipped inside an app binary.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A finance firm wants a Salesforce-connected kiosk to let employees approve payments and then end the session. Its relevant condition is: The kiosk is shared and tokens must not persist across people or long idle periods. The present case instead turns on: The application cannot safely keep a client secret and may be attacked through intercepted redirects. The direct answer here is: A bundled client secret is treated as confidential merely because it is shipped inside an app binary.

Question 282

An integration architect receives this requirement: An enterprise app needs to act on behalf of a specific employee when reading Salesforce task data. A technical discovery also finds: The API must honor the employee's current permissions and a browser approval step is available. Which response most directly addresses the present constraint?

  1. Use a supported OAuth authorization-code web-server flow and validate state and redirect URI.
  2. Evaluate the OAuth device authorization flow supported for its client and user-interaction model.
  3. Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.
  4. Use a user-delegated supported OAuth authorization-code flow with minimal task scope.

Explanation

Correct Answer

D:

Best. The most direct action is to use a user-delegated supported OAuth authorization-code flow with minimal task scope. It is supported by the specific finding that the API must honor the employee's current permissions and a browser approval step is available. The expected acceptance evidence is: Every API request executes with authorized employee context and consent expectations.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-rendered customer portal needs Salesforce to authorize API calls after a customer signs in. Its relevant condition is: The web server can protect a client secret, receive a registered redirect and exchange a one-time code. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: Use a user-delegated supported OAuth authorization-code flow with minimal task scope.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Its relevant condition is: The device has a limited interface but can present a short activation code and poll with rate limits. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: Use a user-delegated supported OAuth authorization-code flow with minimal task scope.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consumer mobile app requests identity and profile information while also accessing Salesforce data. Its relevant condition is: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: Use a user-delegated supported OAuth authorization-code flow with minimal task scope.

Question 283

Consider the following hypothetical Salesforce initiative: An enterprise app needs to act on behalf of a specific employee when reading Salesforce task data. Which evidence would most strongly explain the current integration weakness?

  1. The device has a limited interface but can present a short activation code and poll with rate limits.
  2. The service holds an approved signing certificate and the Salesforce client app is preauthorized.
  3. The kiosk is shared and tokens must not persist across people or long idle periods.
  4. The API must honor the employee's current permissions and a browser approval step is available.

Explanation

Correct Answer

D:

Best. The decisive observation is: The API must honor the employee's current permissions and a browser approval step is available. This is why the design response should be: Use a user-delegated supported OAuth authorization-code flow with minimal task scope.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Its relevant condition is: The device has a limited interface but can present a short activation code and poll with rate limits. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: The API must honor the employee's current permissions and a browser approval step is available.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A headless scheduled analytics job reads Salesforce records nightly without a person present. Its relevant condition is: The service holds an approved signing certificate and the Salesforce client app is preauthorized. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: The API must honor the employee's current permissions and a browser approval step is available.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A finance firm wants a Salesforce-connected kiosk to let employees approve payments and then end the session. Its relevant condition is: The kiosk is shared and tokens must not persist across people or long idle periods. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: The API must honor the employee's current permissions and a browser approval step is available.

Question 284

Review this change: Use a user-delegated supported OAuth authorization-code flow with minimal task scope. It addresses a project where An enterprise app needs to act on behalf of a specific employee when reading Salesforce task data. Which result should appear in integration acceptance evidence?

  1. Each employee grants personal scoped access and the next kiosk user sees no prior tokens.
  2. A trusted service obtains a token without storing a personal employee password.
  3. Every API request executes with authorized employee context and consent expectations.
  4. A user approves the device through a separate browser and the device receives scoped tokens.

Explanation

Correct Answer

C:

Best. The verification target is: Every API request executes with authorized employee context and consent expectations. It tests whether the chosen approach—Use a user-delegated supported OAuth authorization-code flow with minimal task scope.—actually resolves the specific finding: The API must honor the employee's current permissions and a browser approval step is available.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A finance firm wants a Salesforce-connected kiosk to let employees approve payments and then end the session. Its relevant condition is: The kiosk is shared and tokens must not persist across people or long idle periods. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: Every API request executes with authorized employee context and consent expectations.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. Its relevant condition is: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: Every API request executes with authorized employee context and consent expectations.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Its relevant condition is: The device has a limited interface but can present a short activation code and poll with rate limits. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: Every API request executes with authorized employee context and consent expectations.

Question 285

Suppose the integration design proceeds without correcting this issue: The API must honor the employee's current permissions and a browser approval step is available. In the environment An enterprise app needs to act on behalf of a specific employee when reading Salesforce task data. What should the risk register emphasize?

  1. A user-agent flow is used for automated jobs with no browser or resource owner present.
  2. A shared device inherits the previous employee's refresh token and transaction rights.
  3. A bundled client secret is treated as confidential merely because it is shipped inside an app binary.
  4. A broad machine token replaces employee context and exposes unrelated coworkers' tasks.

Explanation

Correct Answer

D:

Best. The most direct failure is: A broad machine token replaces employee context and exposes unrelated coworkers' tasks. It is a consequence of the documented condition: The API must honor the employee's current permissions and a browser approval step is available. A mitigation is: Use a user-delegated supported OAuth authorization-code flow with minimal task scope.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. Its relevant condition is: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: A broad machine token replaces employee context and exposes unrelated coworkers' tasks.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A finance firm wants a Salesforce-connected kiosk to let employees approve payments and then end the session. Its relevant condition is: The kiosk is shared and tokens must not persist across people or long idle periods. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: A broad machine token replaces employee context and exposes unrelated coworkers' tasks.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A native mobile app runs on personally owned phones and invokes Salesforce APIs for the signed-in user. Its relevant condition is: The application cannot safely keep a client secret and may be attacked through intercepted redirects. The present case instead turns on: The API must honor the employee's current permissions and a browser approval step is available. The direct answer here is: A broad machine token replaces employee context and exposes unrelated coworkers' tasks.

Question 286

An architecture board reviews a proposed Salesforce integration. Context: A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. Finding: The vendor needs application-owned credentials rather than human interactive authorization at runtime. Which decision best resolves the concern?

  1. Use a user-delegated supported OAuth authorization-code flow with minimal task scope.
  2. Use a supported JWT bearer flow with signed assertions and a dedicated approved integration user.
  3. Assess a current supported client-credentials flow using a designated integration user and scoped access.
  4. Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.

Explanation

Correct Answer

C:

Best. The most direct action is to assess a current supported client-credentials flow using a designated integration user and scoped access. It is supported by the specific finding that the vendor needs application-owned credentials rather than human interactive authorization at runtime. The expected acceptance evidence is: A trusted service obtains a token without storing a personal employee password.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise app needs to act on behalf of a specific employee when reading Salesforce task data. Its relevant condition is: The API must honor the employee's current permissions and a browser approval step is available. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: Assess a current supported client-credentials flow using a designated integration user and scoped access.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A headless scheduled analytics job reads Salesforce records nightly without a person present. Its relevant condition is: The service holds an approved signing certificate and the Salesforce client app is preauthorized. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: Assess a current supported client-credentials flow using a designated integration user and scoped access.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consumer mobile app requests identity and profile information while also accessing Salesforce data. Its relevant condition is: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: Assess a current supported client-credentials flow using a designated integration user and scoped access.

Question 287

A design workshop describes this environment: A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. Which concrete observation should be documented as the most decisive issue?

  1. The web server can protect a client secret, receive a registered redirect and exchange a one-time code.
  2. The API must honor the employee's current permissions and a browser approval step is available.
  3. The application cannot safely keep a client secret and may be attacked through intercepted redirects.
  4. The vendor needs application-owned credentials rather than human interactive authorization at runtime.

Explanation

Correct Answer

D:

Best. The decisive observation is: The vendor needs application-owned credentials rather than human interactive authorization at runtime. This is why the design response should be: Assess a current supported client-credentials flow using a designated integration user and scoped access.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-rendered customer portal needs Salesforce to authorize API calls after a customer signs in. Its relevant condition is: The web server can protect a client secret, receive a registered redirect and exchange a one-time code. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: The vendor needs application-owned credentials rather than human interactive authorization at runtime.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise app needs to act on behalf of a specific employee when reading Salesforce task data. Its relevant condition is: The API must honor the employee's current permissions and a browser approval step is available. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: The vendor needs application-owned credentials rather than human interactive authorization at runtime.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A native mobile app runs on personally owned phones and invokes Salesforce APIs for the signed-in user. Its relevant condition is: The application cannot safely keep a client secret and may be attacked through intercepted redirects. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: The vendor needs application-owned credentials rather than human interactive authorization at runtime.

Question 288

An architect must create an acceptance test after choosing: Assess a current supported client-credentials flow using a designated integration user and scoped access. For the situation A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. Which result most directly proves success?

  1. A trusted service obtains a token without storing a personal employee password.
  2. The app verifies user identity via a signed ID token and constrains API permissions separately.
  3. The user grants limited API access and the app never exposes a reusable shared secret.
  4. A user approves the device through a separate browser and the device receives scoped tokens.

Explanation

Correct Answer

A:

Best. The verification target is: A trusted service obtains a token without storing a personal employee password. It tests whether the chosen approach—Assess a current supported client-credentials flow using a designated integration user and scoped access.—actually resolves the specific finding: The vendor needs application-owned credentials rather than human interactive authorization at runtime.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consumer mobile app requests identity and profile information while also accessing Salesforce data. Its relevant condition is: The design equates an OAuth access token with a login identity proof and has no signed identity claims. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: A trusted service obtains a token without storing a personal employee password.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A native mobile app runs on personally owned phones and invokes Salesforce APIs for the signed-in user. Its relevant condition is: The application cannot safely keep a client secret and may be attacked through intercepted redirects. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: A trusted service obtains a token without storing a personal employee password.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Its relevant condition is: The device has a limited interface but can present a short activation code and poll with rate limits. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: A trusted service obtains a token without storing a personal employee password.

Question 289

An incident scenario concerns this architecture: A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. The team has discovered: The vendor needs application-owned credentials rather than human interactive authorization at runtime. Which project risk requires explicit mitigation?

  1. A broad machine token replaces employee context and exposes unrelated coworkers' tasks.
  2. A bundled client secret is treated as confidential merely because it is shipped inside an app binary.
  3. A user-agent flow is used for automated jobs with no browser or resource owner present.
  4. An unattended service is designed to require a human to click an authorization link every night.

Explanation

Correct Answer

C:

Best. The most direct failure is: A user-agent flow is used for automated jobs with no browser or resource owner present. It is a consequence of the documented condition: The vendor needs application-owned credentials rather than human interactive authorization at runtime. A mitigation is: Assess a current supported client-credentials flow using a designated integration user and scoped access.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise app needs to act on behalf of a specific employee when reading Salesforce task data. Its relevant condition is: The API must honor the employee's current permissions and a browser approval step is available. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: A user-agent flow is used for automated jobs with no browser or resource owner present.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A native mobile app runs on personally owned phones and invokes Salesforce APIs for the signed-in user. Its relevant condition is: The application cannot safely keep a client secret and may be attacked through intercepted redirects. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: A user-agent flow is used for automated jobs with no browser or resource owner present.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A headless scheduled analytics job reads Salesforce records nightly without a person present. Its relevant condition is: The service holds an approved signing certificate and the Salesforce client app is preauthorized. The present case instead turns on: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The direct answer here is: A user-agent flow is used for automated jobs with no browser or resource owner present.

Question 290

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

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

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

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

B:

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

C:

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

Certified Platform Identity and Access Management Architect Practice Tests