Salesforce Certified Platform Identity and Access Management Architect Practice Test 23
Question 220
An implementation team investigates this scenario: A consulting firm changes job assignments frequently for employees who use Salesforce through SSO. Which finding would most directly justify a change to the integration architecture?
- A user must be created with the correct Contact association and an appropriate external user license.
- Salesforce can validate the IdP signature but provisioning fails due to account configuration restrictions.
- Their SSO subject identifier stays stable but Salesforce contact-account access must change.
- Their old Salesforce permission sets remain even after directory group membership changes.
Explanation
Correct Answer
D:Best. The decisive observation is: Their old Salesforce permission sets remain even after directory group membership changes. This is why the design response should be: Synchronize role-to-permission mappings during lifecycle changes and schedule access recertification.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An Experience Cloud customer logs in through external SAML federation for the first time. Its relevant condition is: A user must be created with the correct Contact association and an appropriate external user license. The present case instead turns on: Their old Salesforce permission sets remain even after directory group membership changes. The direct answer here is: Their old Salesforce permission sets remain even after directory group membership changes.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A first-login SAML JIT routine tries to assign a profile that has no remaining suitable license capacity. Its relevant condition is: Salesforce can validate the IdP signature but provisioning fails due to account configuration restrictions. The present case instead turns on: Their old Salesforce permission sets remain even after directory group membership changes. The direct answer here is: Their old Salesforce permission sets remain even after directory group membership changes.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner user is moved from one reseller account to another following a contract reassignment. Its relevant condition is: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The present case instead turns on: Their old Salesforce permission sets remain even after directory group membership changes. The direct answer here is: Their old Salesforce permission sets remain even after directory group membership changes.
Question 221
A solution review asks whether this control is effective: Synchronize role-to-permission mappings during lifecycle changes and schedule access recertification. The business setting is: A consulting firm changes job assignments frequently for employees who use Salesforce through SSO. What should a demonstrable successful outcome be?
- The user retains the same identity while access moves only to the new authorized reseller records.
- The user is created or updated with an available permitted license and consistent access profile.
- Existing Salesforce users authenticate with their original permissions and record ownership intact.
- User rights reflect their current approved job and outdated assignments are removed.
Explanation
Correct Answer
D:Best. The verification target is: User rights reflect their current approved job and outdated assignments are removed. It tests whether the chosen approach—Synchronize role-to-permission mappings during lifecycle changes and schedule access recertification.—actually resolves the specific finding: Their old Salesforce permission sets remain even after directory group membership changes.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner user is moved from one reseller account to another following a contract reassignment. Its relevant condition is: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The present case instead turns on: Their old Salesforce permission sets remain even after directory group membership changes. The direct answer here is: User rights reflect their current approved job and outdated assignments are removed.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A first-login SAML JIT routine tries to assign a profile that has no remaining suitable license capacity. Its relevant condition is: Salesforce can validate the IdP signature but provisioning fails due to account configuration restrictions. The present case instead turns on: Their old Salesforce permission sets remain even after directory group membership changes. The direct answer here is: User rights reflect their current approved job and outdated assignments are removed.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An acquired company's Salesforce users already exist, but their new enterprise IdP issues different subject IDs. Its relevant condition is: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The present case instead turns on: Their old Salesforce permission sets remain even after directory group membership changes. The direct answer here is: User rights reflect their current approved job and outdated assignments are removed.
Question 222
A Salesforce integration initiative faces this situation: A consulting firm changes job assignments frequently for employees who use Salesforce through SSO. The critical observation is: Their old Salesforce permission sets remain even after directory group membership changes. What failure is most likely if it is ignored?
- The organization equates shared login method with identical application authorization.
- The old partner relationship continues granting visibility to its former customers.
- SSO proves employee identity but preserves access from a previous privileged role.
- The team disables signature verification rather than resolving a provisioning constraint.
Explanation
Correct Answer
C:Best. The most direct failure is: SSO proves employee identity but preserves access from a previous privileged role. It is a consequence of the documented condition: Their old Salesforce permission sets remain even after directory group membership changes. A mitigation is: Synchronize role-to-permission mappings during lifecycle changes and schedule access recertification.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A large company has sales and support employees authenticating with the same IdP. Its relevant condition is: They should share authentication but have different Salesforce objects, licenses and profiles. The present case instead turns on: Their old Salesforce permission sets remain even after directory group membership changes. The direct answer here is: SSO proves employee identity but preserves access from a previous privileged role.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner user is moved from one reseller account to another following a contract reassignment. Its relevant condition is: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The present case instead turns on: Their old Salesforce permission sets remain even after directory group membership changes. The direct answer here is: SSO proves employee identity but preserves access from a previous privileged role.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A first-login SAML JIT routine tries to assign a profile that has no remaining suitable license capacity. Its relevant condition is: Salesforce can validate the IdP signature but provisioning fails due to account configuration restrictions. The present case instead turns on: Their old Salesforce permission sets remain even after directory group membership changes. The direct answer here is: SSO proves employee identity but preserves access from a previous privileged role.
Question 223
An integration architect receives this requirement: A large company has sales and support employees authenticating with the same IdP. A technical discovery also finds: They should share authentication but have different Salesforce objects, licenses and profiles. Which response most directly addresses the present constraint?
- Synchronize role-to-permission mappings during lifecycle changes and schedule access recertification.
- Update approved contact/account associations and dependent sharing rules under a controlled process.
- Keep common SSO trust while assigning least-privilege profiles, roles and permission sets per job.
- Configure standard or controlled custom JIT with required contact, account and user attributes.
Explanation
Correct Answer
C:Best. The most direct action is to keep common SSO trust while assigning least-privilege profiles, roles and permission sets per job. It is supported by the specific finding that They should share authentication but have different Salesforce objects, licenses and profiles. The expected acceptance evidence is: Sales and support teams sign in through one IdP but cannot exceed their approved entitlements.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consulting firm changes job assignments frequently for employees who use Salesforce through SSO. Its relevant condition is: Their old Salesforce permission sets remain even after directory group membership changes. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: Keep common SSO trust while assigning least-privilege profiles, roles and permission sets per job.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner user is moved from one reseller account to another following a contract reassignment. Its relevant condition is: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: Keep common SSO trust while assigning least-privilege profiles, roles and permission sets per job.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An Experience Cloud customer logs in through external SAML federation for the first time. Its relevant condition is: A user must be created with the correct Contact association and an appropriate external user license. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: Keep common SSO trust while assigning least-privilege profiles, roles and permission sets per job.
Question 224
Consider the following hypothetical Salesforce initiative: A large company has sales and support employees authenticating with the same IdP. Which evidence would most strongly explain the current integration weakness?
- The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition.
- Their old Salesforce permission sets remain even after directory group membership changes.
- Salesforce can validate the IdP signature but provisioning fails due to account configuration restrictions.
- They should share authentication but have different Salesforce objects, licenses and profiles.
Explanation
Correct Answer
D:Best. The decisive observation is: They should share authentication but have different Salesforce objects, licenses and profiles. This is why the design response should be: Keep common SSO trust while assigning least-privilege profiles, roles and permission sets per job.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An acquired company's Salesforce users already exist, but their new enterprise IdP issues different subject IDs. Its relevant condition is: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: They should share authentication but have different Salesforce objects, licenses and profiles.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consulting firm changes job assignments frequently for employees who use Salesforce through SSO. Its relevant condition is: Their old Salesforce permission sets remain even after directory group membership changes. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: They should share authentication but have different Salesforce objects, licenses and profiles.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A first-login SAML JIT routine tries to assign a profile that has no remaining suitable license capacity. Its relevant condition is: Salesforce can validate the IdP signature but provisioning fails due to account configuration restrictions. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: They should share authentication but have different Salesforce objects, licenses and profiles.
Question 225
Review this change: Keep common SSO trust while assigning least-privilege profiles, roles and permission sets per job. It addresses a project where A large company has sales and support employees authenticating with the same IdP. Which result should appear in integration acceptance evidence?
- The user is created or updated with an available permitted license and consistent access profile.
- Sales and support teams sign in through one IdP but cannot exceed their approved entitlements.
- Employee departments update safely while privileged access still requires explicit approval.
- Either authorized IdP maps the employee to one existing Salesforce user and one entitlement set.
Explanation
Correct Answer
B:Best. The verification target is: Sales and support teams sign in through one IdP but cannot exceed their approved entitlements. It tests whether the chosen approach—Keep common SSO trust while assigning least-privilege profiles, roles and permission sets per job.—actually resolves the specific finding: They should share authentication but have different Salesforce objects, licenses and profiles.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A first-login SAML JIT routine tries to assign a profile that has no remaining suitable license capacity. Its relevant condition is: Salesforce can validate the IdP signature but provisioning fails due to account configuration restrictions. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: Sales and support teams sign in through one IdP but cannot exceed their approved entitlements.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A trusted SAML identity provider starts sending additional department information for employees. Its relevant condition is: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: Sales and support teams sign in through one IdP but cannot exceed their approved entitlements.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A multinational wants to keep one Salesforce identity for employees who use two SAML IdP entry points. Its relevant condition is: The IdPs use different opaque subject formats even though they represent the same employees. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: Sales and support teams sign in through one IdP but cannot exceed their approved entitlements.
Question 226
Suppose the integration design proceeds without correcting this issue: They should share authentication but have different Salesforce objects, licenses and profiles. In the environment A large company has sales and support employees authenticating with the same IdP. What should the risk register emphasize?
- The organization equates shared login method with identical application authorization.
- The SAML assertion provisions an internal user that bypasses external-account restrictions.
- A compromised assertion attribute grants system-administrator permission during first login.
- JIT creates duplicate users because the assertion matches neither username nor Federation ID.
Explanation
Correct Answer
A:Best. The most direct failure is: The organization equates shared login method with identical application authorization. It is a consequence of the documented condition: They should share authentication but have different Salesforce objects, licenses and profiles. A mitigation is: Keep common SSO trust while assigning least-privilege profiles, roles and permission sets per job.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An Experience Cloud customer logs in through external SAML federation for the first time. Its relevant condition is: A user must be created with the correct Contact association and an appropriate external user license. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: The organization equates shared login method with identical application authorization.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A trusted SAML identity provider starts sending additional department information for employees. Its relevant condition is: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: The organization equates shared login method with identical application authorization.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An acquired company's Salesforce users already exist, but their new enterprise IdP issues different subject IDs. Its relevant condition is: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The present case instead turns on: They should share authentication but have different Salesforce objects, licenses and profiles. The direct answer here is: The organization equates shared login method with identical application authorization.
Question 227
In this fictional project, A partner user is moved from one reseller account to another following a contract reassignment. The project team has uncovered that Their SSO subject identifier stays stable but Salesforce contact-account access must change. Which action is best supported by those facts?
- Update approved contact/account associations and dependent sharing rules under a controlled process.
- Plan a controlled immutable identifier mapping and update Federation IDs before cutover.
- Restrict JIT field updates and apply approved profiles and permission sets through governed assignment rules.
- Configure standard or controlled custom JIT with required contact, account and user attributes.
Explanation
Correct Answer
A:Best. The most direct action is to update approved contact/account associations and dependent sharing rules under a controlled process. It is supported by the specific finding that Their SSO subject identifier stays stable but Salesforce contact-account access must change. The expected acceptance evidence is: The user retains the same identity while access moves only to the new authorized reseller records.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An acquired company's Salesforce users already exist, but their new enterprise IdP issues different subject IDs. Its relevant condition is: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: Update approved contact/account associations and dependent sharing rules under a controlled process.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A trusted SAML identity provider starts sending additional department information for employees. Its relevant condition is: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: Update approved contact/account associations and dependent sharing rules under a controlled process.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An Experience Cloud customer logs in through external SAML federation for the first time. Its relevant condition is: A user must be created with the correct Contact association and an appropriate external user license. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: Update approved contact/account associations and dependent sharing rules under a controlled process.
Question 228
An enterprise review begins with this business situation: A partner user is moved from one reseller account to another following a contract reassignment. Which technical or process signal best identifies the obstacle?
- Their SSO subject identifier stays stable but Salesforce contact-account access must change.
- They should share authentication but have different Salesforce objects, licenses and profiles.
- The business requires Salesforce to redirect to the enterprise IdP before resuming the requested page.
- The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition.
Explanation
Correct Answer
A:Best. The decisive observation is: Their SSO subject identifier stays stable but Salesforce contact-account access must change. This is why the design response should be: Update approved contact/account associations and dependent sharing rules under a controlled process.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A large company has sales and support employees authenticating with the same IdP. Its relevant condition is: They should share authentication but have different Salesforce objects, licenses and profiles. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: Their SSO subject identifier stays stable but Salesforce contact-account access must change.
C:Not best for this scenario. This option is associated with another type of requirement: A field engineer opens a Salesforce deep link without a prior application session. Its relevant condition is: The business requires Salesforce to redirect to the enterprise IdP before resuming the requested page. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: Their SSO subject identifier stays stable but Salesforce contact-account access must change.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An acquired company's Salesforce users already exist, but their new enterprise IdP issues different subject IDs. Its relevant condition is: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: Their SSO subject identifier stays stable but Salesforce contact-account access must change.
Question 229
The team adopts this approach: Update approved contact/account associations and dependent sharing rules under a controlled process. The original project scenario is: A partner user is moved from one reseller account to another following a contract reassignment. Which verification outcome best demonstrates that it worked?
- The user retains the same identity while access moves only to the new authorized reseller records.
- The customer receives a user tied to the right Contact and site permission set.
- User rights reflect their current approved job and outdated assignments are removed.
- Either authorized IdP maps the employee to one existing Salesforce user and one entitlement set.
Explanation
Correct Answer
A:Best. The verification target is: The user retains the same identity while access moves only to the new authorized reseller records. It tests whether the chosen approach—Update approved contact/account associations and dependent sharing rules under a controlled process.—actually resolves the specific finding: Their SSO subject identifier stays stable but Salesforce contact-account access must change.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An Experience Cloud customer logs in through external SAML federation for the first time. Its relevant condition is: A user must be created with the correct Contact association and an appropriate external user license. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: The user retains the same identity while access moves only to the new authorized reseller records.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consulting firm changes job assignments frequently for employees who use Salesforce through SSO. Its relevant condition is: Their old Salesforce permission sets remain even after directory group membership changes. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: The user retains the same identity while access moves only to the new authorized reseller records.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A multinational wants to keep one Salesforce identity for employees who use two SAML IdP entry points. Its relevant condition is: The IdPs use different opaque subject formats even though they represent the same employees. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: The user retains the same identity while access moves only to the new authorized reseller records.
Question 230
A project manager declines to address this finding: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The related project is: A partner user is moved from one reseller account to another following a contract reassignment. Which consequence most directly follows?
- The organization equates shared login method with identical application authorization.
- The old partner relationship continues granting visibility to its former customers.
- JIT creates duplicate users because the assertion matches neither username nor Federation ID.
- SSO proves employee identity but preserves access from a previous privileged role.
Explanation
Correct Answer
B:Best. The most direct failure is: The old partner relationship continues granting visibility to its former customers. It is a consequence of the documented condition: Their SSO subject identifier stays stable but Salesforce contact-account access must change. A mitigation is: Update approved contact/account associations and dependent sharing rules under a controlled process.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A large company has sales and support employees authenticating with the same IdP. Its relevant condition is: They should share authentication but have different Salesforce objects, licenses and profiles. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: The old partner relationship continues granting visibility to its former customers.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An acquired company's Salesforce users already exist, but their new enterprise IdP issues different subject IDs. Its relevant condition is: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: The old partner relationship continues granting visibility to its former customers.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A consulting firm changes job assignments frequently for employees who use Salesforce through SSO. Its relevant condition is: Their old Salesforce permission sets remain even after directory group membership changes. The present case instead turns on: Their SSO subject identifier stays stable but Salesforce contact-account access must change. The direct answer here is: The old partner relationship continues granting visibility to its former customers.