Salesforce Certified Platform Identity and Access Management Architect Practice Test 22
Question 210
An incident scenario concerns this architecture: An acquired company's Salesforce users already exist, but their new enterprise IdP issues different subject IDs. The team has discovered: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. Which project risk requires explicit mitigation?
- Multiple assertions create conflicting identities for the same employee.
- SSO proves employee identity but preserves access from a previous privileged role.
- 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
D:Best. The most direct failure is: JIT creates duplicate users because the assertion matches neither username nor Federation ID. It is a consequence of the documented condition: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. A mitigation is: Plan a controlled immutable identifier mapping and update Federation IDs before cutover.
Incorrect Answers
A: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: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The direct answer here is: JIT creates duplicate users because the assertion matches neither username nor Federation ID.
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: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The direct answer here is: JIT creates duplicate users because the assertion matches neither username nor Federation ID.
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: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The direct answer here is: JIT creates duplicate users because the assertion matches neither username nor Federation ID.
Question 211
An architecture board reviews a proposed Salesforce integration. Context: A trusted SAML identity provider starts sending additional department information for employees. Finding: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. Which decision best resolves the concern?
- Plan a controlled immutable identifier mapping and update Federation IDs before cutover.
- Synchronize role-to-permission mappings during lifecycle changes and schedule access recertification.
- Restrict JIT field updates and apply approved profiles and permission sets through governed assignment rules.
- Update approved contact/account associations and dependent sharing rules under a controlled process.
Explanation
Correct Answer
C:Best. The most direct action is to restrict JIT field updates and apply approved profiles and permission sets through governed assignment rules. It is supported by the specific finding that the organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The expected acceptance evidence is: Employee departments update safely while privileged access still requires explicit approval.
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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: Restrict JIT field updates and apply approved profiles and permission sets through governed assignment rules.
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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: Restrict JIT field updates and apply approved profiles and permission sets through governed assignment rules.
D: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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: Restrict JIT field updates and apply approved profiles and permission sets through governed assignment rules.
Question 212
A design workshop describes this environment: A trusted SAML identity provider starts sending additional department information for employees. Which concrete observation should be documented as the most decisive issue?
- The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition.
- The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights.
- 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.
Explanation
Correct Answer
B:Best. The decisive observation is: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. This is why the design response should be: Restrict JIT field updates and apply approved profiles and permission sets through governed assignment rules.
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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights.
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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights.
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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights.
Question 213
An architect must create an acceptance test after choosing: Restrict JIT field updates and apply approved profiles and permission sets through governed assignment rules. For the situation A trusted SAML identity provider starts sending additional department information for employees. Which result most directly proves success?
- Employee departments update safely while privileged access still requires explicit approval.
- The user retains the same identity while access moves only to the new authorized reseller records.
- User rights reflect their current approved job and outdated assignments are removed.
- Sales and support teams sign in through one IdP but cannot exceed their approved entitlements.
Explanation
Correct Answer
A:Best. The verification target is: Employee departments update safely while privileged access still requires explicit approval. It tests whether the chosen approach—Restrict JIT field updates and apply approved profiles and permission sets through governed assignment rules.—actually resolves the specific finding: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights.
Incorrect Answers
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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: Employee departments update safely while privileged access still requires explicit approval.
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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: Employee departments update safely while privileged access still requires explicit approval.
D: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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: Employee departments update safely while privileged access still requires explicit approval.
Question 214
An incident scenario concerns this architecture: A trusted SAML identity provider starts sending additional department information for employees. The team has discovered: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. Which project risk requires explicit mitigation?
- The organization equates shared login method with identical application authorization.
- The team disables signature verification rather than resolving a provisioning constraint.
- A compromised assertion attribute grants system-administrator permission during first login.
- SSO proves employee identity but preserves access from a previous privileged role.
Explanation
Correct Answer
C:Best. The most direct failure is: A compromised assertion attribute grants system-administrator permission during first login. It is a consequence of the documented condition: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. A mitigation is: Restrict JIT field updates and apply approved profiles and permission sets through governed assignment rules.
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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: A compromised assertion attribute grants system-administrator permission during first login.
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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: A compromised assertion attribute grants system-administrator permission during first login.
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: The organization wants specific user attributes updated on login but must not let the IdP grant arbitrary admin rights. The direct answer here is: A compromised assertion attribute grants system-administrator permission during first login.
Question 215
An integration architect receives this requirement: An Experience Cloud customer logs in through external SAML federation for the first time. A technical discovery also finds: A user must be created with the correct Contact association and an appropriate external user license. Which response most directly addresses the present constraint?
- Configure standard or controlled custom JIT with required contact, account and user attributes.
- Design canonical Federation ID mapping and deduplication with approved source-of-truth governance.
- 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.
Explanation
Correct Answer
A:Best. The most direct action is to configure standard or controlled custom JIT with required contact, account and user attributes. It is supported by the specific finding that A user must be created with the correct Contact association and an appropriate external user license. The expected acceptance evidence is: The customer receives a user tied to the right Contact and site permission set.
Incorrect Answers
B: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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: Configure standard or controlled custom JIT with required contact, account and user attributes.
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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: Configure standard or controlled custom JIT with required contact, account and user attributes.
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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: Configure standard or controlled custom JIT with required contact, account and user attributes.
Question 216
Consider the following hypothetical Salesforce initiative: An Experience Cloud customer logs in through external SAML federation for the first time. Which evidence would most strongly explain the current integration weakness?
- A user must be created with the correct Contact association and an appropriate external user license.
- Their old Salesforce permission sets remain even after directory group membership changes.
- 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.
Explanation
Correct Answer
A:Best. The decisive observation is: A user must be created with the correct Contact association and an appropriate external user license. This is why the design response should be: Configure standard or controlled custom JIT with required contact, account and user attributes.
Incorrect Answers
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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: A user must be created with the correct Contact association and an appropriate external user license.
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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: A user must be created with the correct Contact association and an appropriate external user license.
D: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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: A user must be created with the correct Contact association and an appropriate external user license.
Question 217
Review this change: Configure standard or controlled custom JIT with required contact, account and user attributes. It addresses a project where An Experience Cloud customer logs in through external SAML federation for the first time. Which result should appear in integration acceptance evidence?
- Sales and support teams sign in through one IdP but cannot exceed their approved entitlements.
- User rights reflect their current approved job and outdated assignments are removed.
- 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.
Explanation
Correct Answer
D:Best. The verification target is: The customer receives a user tied to the right Contact and site permission set. It tests whether the chosen approach—Configure standard or controlled custom JIT with required contact, account and user attributes.—actually resolves the specific finding: A user must be created with the correct Contact association and an appropriate external user license.
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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: The customer receives a user tied to the right Contact and site permission set.
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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: The customer receives a user tied to the right Contact and site permission set.
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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: The customer receives a user tied to the right Contact and site permission set.
Question 218
Suppose the integration design proceeds without correcting this issue: A user must be created with the correct Contact association and an appropriate external user license. In the environment An Experience Cloud customer logs in through external SAML federation for the first time. What should the risk register emphasize?
- The team disables signature verification rather than resolving a provisioning constraint.
- The SAML assertion provisions an internal user that bypasses external-account restrictions.
- The old partner relationship continues granting visibility to its former customers.
- A compromised assertion attribute grants system-administrator permission during first login.
Explanation
Correct Answer
B:Best. The most direct failure is: The SAML assertion provisions an internal user that bypasses external-account restrictions. It is a consequence of the documented condition: A user must be created with the correct Contact association and an appropriate external user license. A mitigation is: Configure standard or controlled custom JIT with required contact, account and user attributes.
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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: The SAML assertion provisions an internal user that bypasses external-account restrictions.
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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: The SAML assertion provisions an internal user that bypasses external-account restrictions.
D: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: A user must be created with the correct Contact association and an appropriate external user license. The direct answer here is: The SAML assertion provisions an internal user that bypasses external-account restrictions.
Question 219
Salesforce and its partners face the following situation: A consulting firm changes job assignments frequently for employees who use Salesforce through SSO. The integration review notes: Their old Salesforce permission sets remain even after directory group membership changes. Which architectural step should take priority?
- Keep common SSO trust while assigning least-privilege profiles, roles and permission sets per job.
- 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.
- Design canonical Federation ID mapping and deduplication with approved source-of-truth governance.
Explanation
Correct Answer
B:Best. The most direct action is to synchronize role-to-permission mappings during lifecycle changes and schedule access recertification. It is supported by the specific finding that Their old Salesforce permission sets remain even after directory group membership changes. The expected acceptance evidence is: User rights reflect their current approved job and outdated assignments are removed.
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: Synchronize role-to-permission mappings during lifecycle changes and schedule access recertification.
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: Synchronize role-to-permission mappings during lifecycle changes and schedule access recertification.
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 old Salesforce permission sets remain even after directory group membership changes. The direct answer here is: Synchronize role-to-permission mappings during lifecycle changes and schedule access recertification.
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.