Salesforce Certified Platform Identity and Access Management Architect Practice Test 28
Question 270
An architecture board reviews a proposed Salesforce integration. Context: A headless scheduled analytics job reads Salesforce records nightly without a person present. Finding: The service holds an approved signing certificate and the Salesforce client app is preauthorized. Which decision best resolves the concern?
- Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.
- Choose authorization code with PKCE and a system browser with a securely registered redirect.
- Choose a supported user interactive OAuth flow with PKCE and explicit logout or token cleanup.
- Use a supported JWT bearer flow with signed assertions and a dedicated approved integration user.
Explanation
Correct Answer
D:Best. The most direct action is to use a supported JWT bearer flow with signed assertions and a dedicated approved integration user. It is supported by the specific finding that the service holds an approved signing certificate and the Salesforce client app is preauthorized. The expected acceptance evidence is: The service obtains time-limited API authorization without interactive user login or stored password.
Incorrect Answers
A: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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: Use a supported JWT bearer flow with signed assertions and a dedicated approved integration user.
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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: Use a supported JWT bearer flow with signed assertions and a dedicated approved integration user.
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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: Use a supported JWT bearer flow with signed assertions and a dedicated approved integration user.
Question 271
A design workshop describes this environment: A headless scheduled analytics job reads Salesforce records nightly without a person present. Which concrete observation should be documented as the most decisive issue?
- The device has a limited interface but can present a short activation code and poll with rate limits.
- The web server can protect a client secret, receive a registered redirect and exchange a one-time code.
- The design equates an OAuth access token with a login identity proof and has no signed identity claims.
- The service holds an approved signing certificate and the Salesforce client app is preauthorized.
Explanation
Correct Answer
D:Best. The decisive observation is: The service holds an approved signing certificate and the Salesforce client app is preauthorized. This is why the design response should be: Use a supported JWT bearer flow with signed assertions and a dedicated approved integration user.
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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: The service holds an approved signing certificate and the Salesforce client app is preauthorized.
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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: The service holds an approved signing certificate and the Salesforce client app is preauthorized.
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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: The service holds an approved signing certificate and the Salesforce client app is preauthorized.
Question 272
An architect must create an acceptance test after choosing: Use a supported JWT bearer flow with signed assertions and a dedicated approved integration user. For the situation A headless scheduled analytics job reads Salesforce records nightly without a person present. Which result most directly proves success?
- The portal obtains user-scoped tokens without receiving the customer's Salesforce password.
- Each employee grants personal scoped access and the next kiosk user sees no prior tokens.
- The user grants limited API access and the app never exposes a reusable shared secret.
- The service obtains time-limited API authorization without interactive user login or stored password.
Explanation
Correct Answer
D:Best. The verification target is: The service obtains time-limited API authorization without interactive user login or stored password. It tests whether the chosen approach—Use a supported JWT bearer flow with signed assertions and a dedicated approved integration user.—actually resolves the specific finding: The service holds an approved signing certificate and the Salesforce client app is preauthorized.
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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: The service obtains time-limited API authorization without interactive user login or stored password.
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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: The service obtains time-limited API authorization without interactive user login or stored 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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: The service obtains time-limited API authorization without interactive user login or stored password.
Question 273
An incident scenario concerns this architecture: A headless scheduled analytics job reads Salesforce records nightly without a person present. The team has discovered: The service holds an approved signing certificate and the Salesforce client app is preauthorized. Which project risk requires explicit mitigation?
- A token issued for one resource is accepted as proof of the person's identity elsewhere.
- A user-agent flow is used for automated jobs with no browser or resource owner present.
- A bundled client secret is treated as confidential merely because it is shipped inside an app binary.
- An unattended service is designed to require a human to click an authorization link every night.
Explanation
Correct Answer
D:Best. The most direct failure is: An unattended service is designed to require a human to click an authorization link every night. It is a consequence of the documented condition: The service holds an approved signing certificate and the Salesforce client app is preauthorized. A mitigation is: Use a supported JWT bearer flow with signed assertions and a dedicated approved integration user.
Incorrect Answers
A: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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: An unattended service is designed to require a human to click an authorization link every night.
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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: An unattended service is designed to require a human to click an authorization link every night.
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 service holds an approved signing certificate and the Salesforce client app is preauthorized. The direct answer here is: An unattended service is designed to require a human to click an authorization link every night.
Question 274
An architecture board reviews a proposed Salesforce integration. Context: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Finding: The device has a limited interface but can present a short activation code and poll with rate limits. Which decision best resolves the concern?
- Use a user-delegated supported OAuth authorization-code flow with minimal task scope.
- Assess a current supported client-credentials flow using a designated integration user and scoped access.
- Add appropriately validated OpenID Connect identity claims alongside OAuth resource authorization.
- Evaluate the OAuth device authorization flow supported for its client and user-interaction model.
Explanation
Correct Answer
D:Best. The most direct action is to evaluate the OAuth device authorization flow supported for its client and user-interaction model. It is supported by the specific finding that the device has a limited interface but can present a short activation code and poll with rate limits. The expected acceptance evidence is: A user approves the device through a separate browser and the device receives scoped tokens.
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 device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: Evaluate the OAuth device authorization flow supported for its client and user-interaction model.
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 device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: Evaluate the OAuth device authorization flow supported for its client and user-interaction model.
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 device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: Evaluate the OAuth device authorization flow supported for its client and user-interaction model.
Question 275
A design workshop describes this environment: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Which concrete observation should be documented as the most decisive issue?
- The device has a limited interface but can present a short activation code and poll with rate limits.
- The vendor needs application-owned credentials rather than human interactive authorization at runtime.
- The kiosk is shared and tokens must not persist across people or long idle periods.
- The design equates an OAuth access token with a login identity proof and has no signed identity claims.
Explanation
Correct Answer
A:Best. The decisive observation is: The device has a limited interface but can present a short activation code and poll with rate limits. This is why the design response should be: Evaluate the OAuth device authorization flow supported for its client and user-interaction model.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. Its relevant condition is: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The present case instead turns on: The device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: The device has a limited interface but can present a short activation code and poll with rate limits.
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 device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: The device has a limited interface but can present a short activation code and poll with rate limits.
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 device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: The device has a limited interface but can present a short activation code and poll with rate limits.
Question 276
An architect must create an acceptance test after choosing: Evaluate the OAuth device authorization flow supported for its client and user-interaction model. For the situation A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Which result most directly proves success?
- A user approves the device through a separate browser and the device receives scoped tokens.
- A trusted service obtains a token without storing a personal employee password.
- The service obtains time-limited API authorization without interactive user login or stored password.
- The user grants limited API access and the app never exposes a reusable shared secret.
Explanation
Correct Answer
A:Best. The verification target is: A user approves the device through a separate browser and the device receives scoped tokens. It tests whether the chosen approach—Evaluate the OAuth device authorization flow supported for its client and user-interaction model.—actually resolves the specific finding: The device has a limited interface but can present a short activation code and poll with rate limits.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A machine-to-machine integration is upgrading from legacy stored passwords to supported Salesforce OAuth. Its relevant condition is: The vendor needs application-owned credentials rather than human interactive authorization at runtime. The present case instead turns on: The device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: A user approves the device through a separate browser and the device receives scoped tokens.
C: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 device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: A user approves the device through a separate browser and the device receives scoped tokens.
D: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 device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: A user approves the device through a separate browser and the device receives scoped tokens.
Question 277
An incident scenario concerns this architecture: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. The team has discovered: The device has a limited interface but can present a short activation code and poll with rate limits. Which project risk requires explicit mitigation?
- A user-agent flow is used for automated jobs with no browser or resource owner present.
- The TV embeds a Salesforce username and password because its own keyboard is limited.
- An implicit browser token is used where a secure server-side exchange is readily available.
- A broad machine token replaces employee context and exposes unrelated coworkers' tasks.
Explanation
Correct Answer
B:Best. The most direct failure is: The TV embeds a Salesforce username and password because its own keyboard is limited. It is a consequence of the documented condition: The device has a limited interface but can present a short activation code and poll with rate limits. A mitigation is: Evaluate the OAuth device authorization flow supported for its client and user-interaction model.
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 device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: The TV embeds a Salesforce username and password because its own keyboard is limited.
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 device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: The TV embeds a Salesforce username and password because its own keyboard is limited.
D: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 device has a limited interface but can present a short activation code and poll with rate limits. The direct answer here is: The TV embeds a Salesforce username and password because its own keyboard is limited.
Question 278
Salesforce and its partners face the following situation: A native mobile app runs on personally owned phones and invokes Salesforce APIs for the signed-in user. The integration review notes: The application cannot safely keep a client secret and may be attacked through intercepted redirects. Which architectural step should take priority?
- Use a user-delegated supported OAuth authorization-code flow with minimal task scope.
- Assess a current supported client-credentials flow using a designated integration user and scoped access.
- Choose authorization code with PKCE and a system browser with a securely registered redirect.
- Choose a supported user interactive OAuth flow with PKCE and explicit logout or token cleanup.
Explanation
Correct Answer
C:Best. The most direct action is to choose authorization code with PKCE and a system browser with a securely registered redirect. It is supported by the specific finding that the application cannot safely keep a client secret and may be attacked through intercepted redirects. The expected acceptance evidence is: The user grants limited API access and the app never exposes a reusable shared secret.
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 application cannot safely keep a client secret and may be attacked through intercepted redirects. The direct answer here is: Choose authorization code with PKCE and a system browser with a securely registered redirect.
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 application cannot safely keep a client secret and may be attacked through intercepted redirects. The direct answer here is: Choose authorization code with PKCE and a system browser with a securely registered redirect.
D: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: Choose authorization code with PKCE and a system browser with a securely registered redirect.
Question 279
An implementation team investigates this scenario: A native mobile app runs on personally owned phones and invokes Salesforce APIs for the signed-in user. Which finding would most directly justify a change to the integration architecture?
- The web server can protect a client secret, receive a registered redirect and exchange a one-time code.
- The service holds an approved signing certificate and the Salesforce client app is preauthorized.
- The application cannot safely keep a client secret and may be attacked through intercepted redirects.
- The kiosk is shared and tokens must not persist across people or long idle periods.
Explanation
Correct Answer
C:Best. The decisive observation is: The application cannot safely keep a client secret and may be attacked through intercepted redirects. This is why the design response should be: 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 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: The application cannot safely keep a client secret and may be attacked through intercepted redirects.
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 application cannot safely keep a client secret and may be attacked through intercepted redirects. The direct answer here is: The application cannot safely keep a client secret and may be attacked through intercepted redirects.
D: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: The application cannot safely keep a client secret and may be attacked through intercepted redirects.
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?
- The service obtains time-limited API authorization without interactive user login or stored password.
- The app verifies user identity via a signed ID token and constrains API permissions separately.
- A user approves the device through a separate browser and the device receives scoped tokens.
- 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.