Salesforce Certified Platform Identity and Access Management Architect Practice Test 21
Question 200
An implementation team investigates this scenario: A public Experience Cloud site wants business partners and casual customers to use different IdPs. Which finding would most directly justify a change to the integration architecture?
- The identity source issues signed browser SAML assertions and controls the employee MFA policy.
- Salesforce receives proof of authentication from the institution but may not handle account passwords.
- The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in.
- The two populations have different assurance, licensing and contact-account relationships.
Explanation
Correct Answer
D:Best. The decisive observation is: The two populations have different assurance, licensing and contact-account relationships. This is why the design response should be: Configure approved authentication choices per audience and validate routing to the intended provider.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company wants Salesforce to authenticate employees who already sign into a SAML-compatible corporate IdP. Its relevant condition is: The identity source issues signed browser SAML assertions and controls the employee MFA policy. The present case instead turns on: The two populations have different assurance, licensing and contact-account relationships. The direct answer here is: The two populations have different assurance, licensing and contact-account relationships.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial institution insists the customer's authentication occurs only at its enterprise IdP. Its relevant condition is: Salesforce receives proof of authentication from the institution but may not handle account passwords. The present case instead turns on: The two populations have different assurance, licensing and contact-account relationships. The direct answer here is: The two populations have different assurance, licensing and contact-account relationships.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A digital subscription service has customers authenticating with an external OpenID Connect provider. Its relevant condition is: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The present case instead turns on: The two populations have different assurance, licensing and contact-account relationships. The direct answer here is: The two populations have different assurance, licensing and contact-account relationships.
Question 201
A solution review asks whether this control is effective: Configure approved authentication choices per audience and validate routing to the intended provider. The business setting is: A public Experience Cloud site wants business partners and casual customers to use different IdPs. What should a demonstrable successful outcome be?
- Returning customers are identified through validated OIDC identity claims and mapped users.
- Employee browsers enter Salesforce from the approved corporate IdP without password replication.
- Partners and consumers follow their permitted sign-in path and receive appropriately scoped sessions.
- The supplier portal handles only its registered SAML or OIDC identity evidence correctly.
Explanation
Correct Answer
C:Best. The verification target is: Partners and consumers follow their permitted sign-in path and receive appropriately scoped sessions. It tests whether the chosen approach—Configure approved authentication choices per audience and validate routing to the intended provider.—actually resolves the specific finding: The two populations have different assurance, licensing and contact-account relationships.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A digital subscription service has customers authenticating with an external OpenID Connect provider. Its relevant condition is: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The present case instead turns on: The two populations have different assurance, licensing and contact-account relationships. The direct answer here is: Partners and consumers follow their permitted sign-in path and receive appropriately scoped sessions.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company wants Salesforce to authenticate employees who already sign into a SAML-compatible corporate IdP. Its relevant condition is: The identity source issues signed browser SAML assertions and controls the employee MFA policy. The present case instead turns on: The two populations have different assurance, licensing and contact-account relationships. The direct answer here is: Partners and consumers follow their permitted sign-in path and receive appropriately scoped sessions.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A Salesforce admin compares a signed SAML assertion with an OpenID Connect ID token for a new supplier portal. Its relevant condition is: The design document calls both protocols identical because each can support web SSO. The present case instead turns on: The two populations have different assurance, licensing and contact-account relationships. The direct answer here is: Partners and consumers follow their permitted sign-in path and receive appropriately scoped sessions.
Question 202
A Salesforce integration initiative faces this situation: A public Experience Cloud site wants business partners and casual customers to use different IdPs. The critical observation is: The two populations have different assurance, licensing and contact-account relationships. What failure is most likely if it is ignored?
- An OIDC token is posted to the SAML assertion-consumer endpoint and fails authentication.
- An OAuth client token is incorrectly treated as a replacement for human password verification.
- A customer social login is accepted for sensitive partner administrator access without extra checks.
- The team tries an OAuth client-credentials flow for employee interactive SSO.
Explanation
Correct Answer
C:Best. The most direct failure is: A customer social login is accepted for sensitive partner administrator access without extra checks. It is a consequence of the documented condition: The two populations have different assurance, licensing and contact-account relationships. A mitigation is: Configure approved authentication choices per audience and validate routing to the intended provider.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A Salesforce admin compares a signed SAML assertion with an OpenID Connect ID token for a new supplier portal. Its relevant condition is: The design document calls both protocols identical because each can support web SSO. The present case instead turns on: The two populations have different assurance, licensing and contact-account relationships. The direct answer here is: A customer social login is accepted for sensitive partner administrator access without extra checks.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A payroll application sends a custom delegated authentication request to an old Salesforce implementation. Its relevant condition is: The architecture confuses delegated password validation with OAuth authorization scopes. The present case instead turns on: The two populations have different assurance, licensing and contact-account relationships. The direct answer here is: A customer social login is accepted for sensitive partner administrator access without extra checks.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company wants Salesforce to authenticate employees who already sign into a SAML-compatible corporate IdP. Its relevant condition is: The identity source issues signed browser SAML assertions and controls the employee MFA policy. The present case instead turns on: The two populations have different assurance, licensing and contact-account relationships. The direct answer here is: A customer social login is accepted for sensitive partner administrator access without extra checks.
Question 203
Salesforce and its partners face the following situation: A Salesforce admin compares a signed SAML assertion with an OpenID Connect ID token for a new supplier portal. The integration review notes: The design document calls both protocols identical because each can support web SSO. Which architectural step should take priority?
- Choose the format supported by the selected IdP and configure protocol-specific signature and claim validation.
- Evaluate Salesforce authentication provider support and a safe new-user registration handler.
- Configure approved authentication choices per audience and validate routing to the intended provider.
- Use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping.
Explanation
Correct Answer
A:Best. The most direct action is to choose the format supported by the selected IdP and configure protocol-specific signature and claim validation. It is supported by the specific finding that the design document calls both protocols identical because each can support web SSO. The expected acceptance evidence is: The supplier portal handles only its registered SAML or OIDC identity evidence correctly.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional service business wants its members to sign in with a supported social identity account. Its relevant condition is: The site's identity requirements allow a reviewed external social authentication provider. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: Choose the format supported by the selected IdP and configure protocol-specific signature and claim validation.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public Experience Cloud site wants business partners and casual customers to use different IdPs. Its relevant condition is: The two populations have different assurance, licensing and contact-account relationships. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: Choose the format supported by the selected IdP and configure protocol-specific signature and claim validation.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial institution insists the customer's authentication occurs only at its enterprise IdP. Its relevant condition is: Salesforce receives proof of authentication from the institution but may not handle account passwords. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: Choose the format supported by the selected IdP and configure protocol-specific signature and claim validation.
Question 204
An implementation team investigates this scenario: A Salesforce admin compares a signed SAML assertion with an OpenID Connect ID token for a new supplier portal. Which finding would most directly justify a change to the integration architecture?
- The identity source issues signed browser SAML assertions and controls the employee MFA policy.
- The design document calls both protocols identical because each can support web SSO.
- The workforce populations use different trusted assertion issuers and need separate SSO entry points.
- The site's identity requirements allow a reviewed external social authentication provider.
Explanation
Correct Answer
B:Best. The decisive observation is: The design document calls both protocols identical because each can support web SSO. This is why the design response should be: Choose the format supported by the selected IdP and configure protocol-specific signature and claim validation.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company wants Salesforce to authenticate employees who already sign into a SAML-compatible corporate IdP. Its relevant condition is: The identity source issues signed browser SAML assertions and controls the employee MFA policy. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: The design document calls both protocols identical because each can support web SSO.
C:Not best for this scenario. This option is associated with another type of requirement: A merged enterprise has two corporate IdPs during a gradual identity consolidation. Its relevant condition is: The workforce populations use different trusted assertion issuers and need separate SSO entry points. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: The design document calls both protocols identical because each can support web SSO.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional service business wants its members to sign in with a supported social identity account. Its relevant condition is: The site's identity requirements allow a reviewed external social authentication provider. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: The design document calls both protocols identical because each can support web SSO.
Question 205
A solution review asks whether this control is effective: Choose the format supported by the selected IdP and configure protocol-specific signature and claim validation. The business setting is: A Salesforce admin compares a signed SAML assertion with an OpenID Connect ID token for a new supplier portal. What should a demonstrable successful outcome be?
- Returning customers are identified through validated OIDC identity claims and mapped users.
- Employee browsers enter Salesforce from the approved corporate IdP without password replication.
- The supplier portal handles only its registered SAML or OIDC identity evidence correctly.
- The solution selects a supported mechanism matching the required interactive authentication behavior.
Explanation
Correct Answer
C:Best. The verification target is: The supplier portal handles only its registered SAML or OIDC identity evidence correctly. It tests whether the chosen approach—Choose the format supported by the selected IdP and configure protocol-specific signature and claim validation.—actually resolves the specific finding: The design document calls both protocols identical because each can support web SSO.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A digital subscription service has customers authenticating with an external OpenID Connect provider. Its relevant condition is: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: The supplier portal handles only its registered SAML or OIDC identity evidence correctly.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company wants Salesforce to authenticate employees who already sign into a SAML-compatible corporate IdP. Its relevant condition is: The identity source issues signed browser SAML assertions and controls the employee MFA policy. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: The supplier portal handles only its registered SAML or OIDC identity evidence correctly.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A payroll application sends a custom delegated authentication request to an old Salesforce implementation. Its relevant condition is: The architecture confuses delegated password validation with OAuth authorization scopes. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: The supplier portal handles only its registered SAML or OIDC identity evidence correctly.
Question 206
A Salesforce integration initiative faces this situation: A Salesforce admin compares a signed SAML assertion with an OpenID Connect ID token for a new supplier portal. The critical observation is: The design document calls both protocols identical because each can support web SSO. What failure is most likely if it is ignored?
- A custom password form inside Salesforce duplicates credentials and violates central authentication policy.
- An OIDC token is posted to the SAML assertion-consumer endpoint and fails authentication.
- Automatically trusting social email alone merges two unrelated member accounts.
- An OAuth client token is incorrectly treated as a replacement for human password verification.
Explanation
Correct Answer
B:Best. The most direct failure is: An OIDC token is posted to the SAML assertion-consumer endpoint and fails authentication. It is a consequence of the documented condition: The design document calls both protocols identical because each can support web SSO. A mitigation is: Choose the format supported by the selected IdP and configure protocol-specific signature and claim validation.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial institution insists the customer's authentication occurs only at its enterprise IdP. Its relevant condition is: Salesforce receives proof of authentication from the institution but may not handle account passwords. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: An OIDC token is posted to the SAML assertion-consumer endpoint and fails authentication.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional service business wants its members to sign in with a supported social identity account. Its relevant condition is: The site's identity requirements allow a reviewed external social authentication provider. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: An OIDC token is posted to the SAML assertion-consumer endpoint and fails authentication.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A payroll application sends a custom delegated authentication request to an old Salesforce implementation. Its relevant condition is: The architecture confuses delegated password validation with OAuth authorization scopes. The present case instead turns on: The design document calls both protocols identical because each can support web SSO. The direct answer here is: An OIDC token is posted to the SAML assertion-consumer endpoint and fails authentication.
Question 207
An architecture board reviews a proposed Salesforce integration. Context: An acquired company's Salesforce users already exist, but their new enterprise IdP issues different subject IDs. Finding: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. Which decision best resolves the concern?
- Configure standard or controlled custom JIT with required contact, account and user attributes.
- Diagnose the provisioning handler and licensed profile requirements before modifying the assertion.
- Restrict JIT field updates and apply approved profiles and permission sets through governed assignment rules.
- Plan a controlled immutable identifier mapping and update Federation IDs before cutover.
Explanation
Correct Answer
D:Best. The most direct action is to plan a controlled immutable identifier mapping and update Federation IDs before cutover. It is supported by the specific finding that the SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The expected acceptance evidence is: Existing Salesforce users authenticate with their original permissions and record ownership intact.
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: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The direct answer here is: Plan a controlled immutable identifier mapping and update Federation IDs before cutover.
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 SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The direct answer here is: Plan a controlled immutable identifier mapping and update Federation IDs before cutover.
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: Plan a controlled immutable identifier mapping and update Federation IDs before cutover.
Question 208
A design workshop describes this environment: An acquired company's Salesforce users already exist, but their new enterprise IdP issues different subject IDs. Which concrete observation should be documented as the most decisive issue?
- They should share authentication but have different Salesforce objects, licenses and profiles.
- Their SSO subject identifier stays stable but Salesforce contact-account access must change.
- 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.
Explanation
Correct Answer
C:Best. The decisive observation is: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. This is why the design response should be: 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 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 SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The direct answer here is: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition.
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 SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The direct answer here is: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition.
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: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The direct answer here is: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition.
Question 209
An architect must create an acceptance test after choosing: Plan a controlled immutable identifier mapping and update Federation IDs before cutover. For the situation An acquired company's Salesforce users already exist, but their new enterprise IdP issues different subject IDs. Which result most directly proves success?
- Either authorized IdP maps the employee to one existing Salesforce user and one entitlement set.
- The customer receives a user tied to the right Contact and site permission set.
- Employee departments update safely while privileged access still requires explicit approval.
- Existing Salesforce users authenticate with their original permissions and record ownership intact.
Explanation
Correct Answer
D:Best. The verification target is: Existing Salesforce users authenticate with their original permissions and record ownership intact. It tests whether the chosen approach—Plan a controlled immutable identifier mapping and update Federation IDs before cutover.—actually resolves the specific finding: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition.
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: Existing Salesforce users authenticate with their original permissions and record ownership intact.
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: The SAML assertion claims do not match the stored Salesforce Federation IDs after the acquisition. The direct answer here is: Existing Salesforce users authenticate with their original permissions and record ownership intact.
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: Existing Salesforce users authenticate with their original permissions and record ownership intact.
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.