Salesforce Certified Platform Identity and Access Management Architect Practice Test 32
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?
- Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.
- Use controlled application approvals, least privilege, token policy and per-org deployment documentation.
- Register exact valid callback URLs in the connected-app configuration and test the correct tenant.
- 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.
Question 311
Consider the following hypothetical Salesforce initiative: An external payroll application requires an OAuth redirect after a user signs into Salesforce. Which evidence would most strongly explain the current integration weakness?
- The team assumes an OAuth scope can replace all Salesforce profile and sharing controls.
- The proposed connected-app grant includes broad administrative and object-changing permissions.
- Each subsidiary needs approved policy settings and independent review of scopes and permitted users.
- The app registration lists only a development callback address while production uses another host.
Explanation
Correct Answer
D:Best. The decisive observation is: The app registration lists only a development callback address while production uses another host. This is why the design response should be: Register exact valid callback URLs in the connected-app configuration and test the correct tenant.
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 app registration lists only a development callback address while production uses another host. The direct answer here is: The app registration lists only a development callback address while production uses another host.
B: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: The app registration lists only a development callback address while production uses another host.
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 app registration lists only a development callback address while production uses another host. The direct answer here is: The app registration lists only a development callback address while production uses another host.
Question 312
Review this change: Register exact valid callback URLs in the connected-app configuration and test the correct tenant. It addresses a project where An external payroll application requires an OAuth redirect after a user signs into Salesforce. Which result should appear in integration acceptance evidence?
- The same vendor app is only usable by explicitly approved populations under each org's policy.
- Salesforce redirects authorization results solely to approved application destinations.
- Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.
- Only authorized client applications obtain tokens and app access is auditable.
Explanation
Correct Answer
B:Best. The verification target is: Salesforce redirects authorization results solely to approved application destinations. It tests whether the chosen approach—Register exact valid callback URLs in the connected-app configuration and test the correct tenant.—actually resolves the specific finding: The app registration lists only a development callback address while production uses another host.
Incorrect Answers
A: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: Salesforce redirects authorization results solely to approved application destinations.
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 app registration lists only a development callback address while production uses another host. The direct answer here is: Salesforce redirects authorization results solely to approved application destinations.
D: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 app registration lists only a development callback address while production uses another host. The direct answer here is: Salesforce redirects authorization results solely to approved application destinations.
Question 313
Suppose the integration design proceeds without correcting this issue: The app registration lists only a development callback address while production uses another host. In the environment An external payroll application requires an OAuth redirect after a user signs into Salesforce. What should the risk register emphasize?
- An excessive refresh permission persists beyond the business session's lifetime.
- A phishing app persuades an employee to grant API access without corporate review.
- An overbroad app scope is mistaken for permission to all confidential business data.
- A wildcard redirect exposes an authorization code to an attacker-controlled host.
Explanation
Correct Answer
D:Best. The most direct failure is: A wildcard redirect exposes an authorization code to an attacker-controlled host. It is a consequence of the documented condition: The app registration lists only a development callback address while production uses another host. A mitigation is: Register exact valid callback URLs in the connected-app configuration and test the correct tenant.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A Salesforce org provides identity to an external analytics portal that requests both profile and report access. Its relevant condition is: The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session. The present case instead turns on: The app registration lists only a development callback address while production uses another host. The direct answer here is: A wildcard redirect exposes an authorization code to an attacker-controlled host.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services team must block unknown external apps from gaining access to Salesforce. Its relevant condition is: The connected-app policy currently lets users self-authorize any requesting OAuth client. The present case instead turns on: The app registration lists only a development callback address while production uses another host. The direct answer here is: A wildcard redirect exposes an authorization code to an attacker-controlled host.
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 app registration lists only a development callback address while production uses another host. The direct answer here is: A wildcard redirect exposes an authorization code to an attacker-controlled host.
Question 314
An integration architect receives this requirement: A corporate mobile app must access Salesforce but only when installed on managed and approved devices. A technical discovery also finds: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. Which response most directly addresses the present constraint?
- Require approved application governance, permitted users and explicit authorization policy as appropriate.
- Apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario.
- Limit approved connected-app scopes and refresh-token policy to the actual portal requirement.
- Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.
Explanation
Correct Answer
B:Best. The most direct action is to apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario. It is supported by the specific finding that A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The expected acceptance evidence is: Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.
Incorrect Answers
A: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: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: Apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario.
C: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: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: Apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario.
D: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: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: Apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario.
Question 315
Consider the following hypothetical Salesforce initiative: A corporate mobile app must access Salesforce but only when installed on managed and approved devices. Which evidence would most strongly explain the current integration weakness?
- Each subsidiary needs approved policy settings and independent review of scopes and permitted users.
- The connected-app policy currently lets users self-authorize any requesting OAuth client.
- The portal asks for offline refresh and broad scopes that are not necessary for its short-lived session.
- A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations.
Explanation
Correct Answer
D:Best. The decisive observation is: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. This is why the design response should be: Apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario.
Incorrect Answers
A: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: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services team must block unknown external apps from gaining access to Salesforce. Its relevant condition is: The connected-app policy currently lets users self-authorize any requesting OAuth client. The present case instead turns on: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations.
C: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: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations.
Question 316
Review this change: Apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario. It addresses a project where A corporate mobile app must access Salesforce but only when installed on managed and approved devices. Which result should appear in integration acceptance evidence?
- Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.
- Authorized report queries work but sensitive objects and record edits remain denied.
- The same vendor app is only usable by explicitly approved populations under each org's policy.
- Identity claims and report access work while unnecessary offline privileges are unavailable.
Explanation
Correct Answer
A:Best. The verification target is: Approved managed sessions gain intended access while untrusted sessions are challenged or blocked. It tests whether the chosen approach—Apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario.—actually resolves the specific finding: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations.
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: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.
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: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.
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: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.
Question 317
Suppose the integration design proceeds without correcting this issue: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. In the environment A corporate mobile app must access Salesforce but only when installed on managed and approved devices. What should the risk register emphasize?
- A phishing app persuades an employee to grant API access without corporate review.
- One permissive connected-app setting exposes data in subsidiaries that never approved it.
- A valid OAuth token becomes sufficient to bypass the organization's device restrictions.
- An overbroad app scope is mistaken for permission to all confidential business data.
Explanation
Correct Answer
C:Best. The most direct failure is: A valid OAuth token becomes sufficient to bypass the organization's device restrictions. It is a consequence of the documented condition: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. A mitigation is: Apply documented connected-app IP, policy, permitted-user and assurance controls appropriate to the scenario.
Incorrect Answers
A: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: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: A valid OAuth token becomes sufficient to bypass the organization's device restrictions.
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: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: A valid OAuth token becomes sufficient to bypass the organization's device restrictions.
D: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: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The direct answer here is: A valid OAuth token becomes sufficient to bypass the organization's device restrictions.
Question 318
An architecture board reviews a proposed Salesforce integration. Context: A sales analytics provider requests both the api and full data privileges for a small reporting use case. Finding: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. Which decision best resolves the concern?
- Require approved application governance, permitted users and explicit authorization policy as appropriate.
- Configure minimum OAuth scopes and an integration user's restricted object, field and record permissions.
- Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries.
- 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 restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries. It is supported by the specific finding that the team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The expected acceptance evidence is: Authorized report queries work but sensitive objects and record edits remain denied.
Incorrect Answers
A: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 team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries.
B: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 team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries.
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 team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries.
Question 319
A design workshop describes this environment: A sales analytics provider requests both the api and full data privileges for a small reporting use case. 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 proposed connected-app grant includes broad administrative and object-changing permissions.
- The team assumes an OAuth scope can replace all Salesforce profile and sharing controls.
- A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations.
Explanation
Correct Answer
C:Best. The decisive observation is: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. This is why the design response should be: Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries.
Incorrect Answers
A:Not best for this scenario. This option is associated with another type of requirement: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Its relevant condition is: The device has a limited interface but can present a short activation code and poll with rate limits. The present case instead turns on: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls.
B: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 team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls.
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 team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls.
Question 320
An architect must create an acceptance test after choosing: Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries. For the situation A sales analytics provider requests both the api and full data privileges for a small reporting use case. Which result most directly proves success?
- Salesforce redirects authorization results solely to approved application destinations.
- Approved managed sessions gain intended access while untrusted sessions are challenged or blocked.
- A user approves the device through a separate browser and the device receives scoped tokens.
- Authorized report queries work but sensitive objects and record edits remain denied.
Explanation
Correct Answer
D:Best. The verification target is: Authorized report queries work but sensitive objects and record edits remain denied. It tests whether the chosen approach—Restrict scope and ensure the underlying integration user's permissions and sharing enforce resource boundaries.—actually resolves the specific finding: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external payroll application requires an OAuth redirect after a user signs into Salesforce. Its relevant condition is: The app registration lists only a development callback address while production uses another host. The present case instead turns on: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: Authorized report queries work but sensitive objects and record edits remain denied.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A corporate mobile app must access Salesforce but only when installed on managed and approved devices. Its relevant condition is: A wide-open connected-app policy allows logins from unmanaged devices and unsupported network locations. The present case instead turns on: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: Authorized report queries work but sensitive objects and record edits remain denied.
C:Not best for this scenario. This option is associated with another type of requirement: A smart television cannot conveniently open a full web login page for a Salesforce-connected service. Its relevant condition is: The device has a limited interface but can present a short activation code and poll with rate limits. The present case instead turns on: The team assumes an OAuth scope can replace all Salesforce profile and sharing controls. The direct answer here is: Authorized report queries work but sensitive objects and record edits remain denied.