Salesforce Certified Platform Identity and Access Management Architect Practice Test 64
Question 630
Consider the following hypothetical Salesforce initiative: A supplier partner SAML login validates the signature but Salesforce rejects user creation. Which evidence would most strongly explain the current integration weakness?
- Their identity provider can still authenticate but they must lose Salesforce record access immediately.
- The new provider returns a different subject value but the person must retain the original account.
- The SAML JIT attributes omit required Contact or Account information for an external user.
- The existing site lacks a safe registration handler to match first-time identity claims to Contacts.
Explanation
Correct Answer
C:Best. The decisive observation is: The SAML JIT attributes omit required Contact or Account information for an external user. This is why the design response should be: Compare the publisher's JIT external-user requirements and update the approved provisioning handler.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner is removed from a retailer's supplier network after a contract termination. Its relevant condition is: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The present case instead turns on: The SAML JIT attributes omit required Contact or Account information for an external user. The direct answer here is: The SAML JIT attributes omit required Contact or Account information for an external user.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A customer already has an Experience Cloud user and signs in through a newly added OIDC provider. Its relevant condition is: The new provider returns a different subject value but the person must retain the original account. The present case instead turns on: The SAML JIT attributes omit required Contact or Account information for an external user. The direct answer here is: The SAML JIT attributes omit required Contact or Account information for an external user.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An online retailer lets customers sign in using a supported OpenID Connect social provider. Its relevant condition is: The existing site lacks a safe registration handler to match first-time identity claims to Contacts. The present case instead turns on: The SAML JIT attributes omit required Contact or Account information for an external user. The direct answer here is: The SAML JIT attributes omit required Contact or Account information for an external user.
Question 631
Review this change: Compare the publisher's JIT external-user requirements and update the approved provisioning handler. It addresses a project where A supplier partner SAML login validates the signature but Salesforce rejects user creation. Which result should appear in integration acceptance evidence?
- Each customer signs in at the correct trusted IdP and maps to a single scoped external identity.
- Newly federated partners are created with the necessary valid Contact/account association.
- The customer retains order history without automatically trusting matching email claims.
- No later SSO attempt or previous session can reveal former partner records.
Explanation
Correct Answer
B:Best. The verification target is: Newly federated partners are created with the necessary valid Contact/account association. It tests whether the chosen approach—Compare the publisher's JIT external-user requirements and update the approved provisioning handler.—actually resolves the specific finding: The SAML JIT attributes omit required Contact or Account information for an external user.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2C portal supports customers from several countries through different approved IdPs. Its relevant condition is: The configuration sends all users to one provider and assumes each national identity source has the same format. The present case instead turns on: The SAML JIT attributes omit required Contact or Account information for an external user. The direct answer here is: Newly federated partners are created with the necessary valid Contact/account association.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A customer already has an Experience Cloud user and signs in through a newly added OIDC provider. Its relevant condition is: The new provider returns a different subject value but the person must retain the original account. The present case instead turns on: The SAML JIT attributes omit required Contact or Account information for an external user. The direct answer here is: Newly federated partners are created with the necessary valid Contact/account association.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner is removed from a retailer's supplier network after a contract termination. Its relevant condition is: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The present case instead turns on: The SAML JIT attributes omit required Contact or Account information for an external user. The direct answer here is: Newly federated partners are created with the necessary valid Contact/account association.
Question 632
Suppose the integration design proceeds without correcting this issue: The SAML JIT attributes omit required Contact or Account information for an external user. In the environment A supplier partner SAML login validates the signature but Salesforce rejects user creation. What should the risk register emphasize?
- The team disables identity checks rather than providing mandatory external-user fields.
- An updated surname causes reassignment to a different citizen's Salesforce record.
- A mislinked Contact permits the partner to inspect another distributor's customer data.
- Matching solely on email lets an attacker claim a customer's preexisting CRM account.
Explanation
Correct Answer
A:Best. The most direct failure is: The team disables identity checks rather than providing mandatory external-user fields. It is a consequence of the documented condition: The SAML JIT attributes omit required Contact or Account information for an external user. A mitigation is: Compare the publisher's JIT external-user requirements and update the approved provisioning handler.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A government agency allows its constituent services to federate from a trusted national IdP. Its relevant condition is: The IdP issues a stable subject claim, but the site currently keys users by mutable display names. The present case instead turns on: The SAML JIT attributes omit required Contact or Account information for an external user. The direct answer here is: The team disables identity checks rather than providing mandatory external-user fields.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional distributor wants partners to authenticate through their employer's corporate SAML IdP. Its relevant condition is: Each partner user must be associated with a Contact and a permitted Salesforce partner account. The present case instead turns on: The SAML JIT attributes omit required Contact or Account information for an external user. The direct answer here is: The team disables identity checks rather than providing mandatory external-user fields.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An online retailer lets customers sign in using a supported OpenID Connect social provider. Its relevant condition is: The existing site lacks a safe registration handler to match first-time identity claims to Contacts. The present case instead turns on: The SAML JIT attributes omit required Contact or Account information for an external user. The direct answer here is: The team disables identity checks rather than providing mandatory external-user fields.
Question 633
In this fictional project, A customer already has an Experience Cloud user and signs in through a newly added OIDC provider. The project team has uncovered that The new provider returns a different subject value but the person must retain the original account. Which action is best supported by those facts?
- Configure external SAML SSO and verify contact-account, federation ID, license and sharing mappings.
- Use an approved account-linking process with proof of identity and stable mapping between providers.
- Use a stable verified federation identifier and controlled identity-to-Contact association.
- Deactivate or remove the associated external site user and revoke active sessions while closing sharing grants.
Explanation
Correct Answer
B:Best. The most direct action is to use an approved account-linking process with proof of identity and stable mapping between providers. It is supported by the specific finding that the new provider returns a different subject value but the person must retain the original account. The expected acceptance evidence is: The customer retains order history without automatically trusting matching email claims.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional distributor wants partners to authenticate through their employer's corporate SAML IdP. Its relevant condition is: Each partner user must be associated with a Contact and a permitted Salesforce partner account. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: Use an approved account-linking process with proof of identity and stable mapping between providers.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A government agency allows its constituent services to federate from a trusted national IdP. Its relevant condition is: The IdP issues a stable subject claim, but the site currently keys users by mutable display names. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: Use an approved account-linking process with proof of identity and stable mapping between providers.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner is removed from a retailer's supplier network after a contract termination. Its relevant condition is: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: Use an approved account-linking process with proof of identity and stable mapping between providers.
Question 634
An enterprise review begins with this business situation: A customer already has an Experience Cloud user and signs in through a newly added OIDC provider. Which technical or process signal best identifies the obstacle?
- The user directory contains multiple stores with similar email domains, but their data boundaries differ.
- Each partner user must be associated with a Contact and a permitted Salesforce partner account.
- The new provider returns a different subject value but the person must retain the original account.
- The IdP issues a stable subject claim, but the site currently keys users by mutable display names.
Explanation
Correct Answer
C:Best. The decisive observation is: The new provider returns a different subject value but the person must retain the original account. This is why the design response should be: Use an approved account-linking process with proof of identity and stable mapping between providers.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A franchise creates Experience Cloud accounts for independent stores using one Salesforce org. Its relevant condition is: The user directory contains multiple stores with similar email domains, but their data boundaries differ. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: The new provider returns a different subject value but the person must retain the original account.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional distributor wants partners to authenticate through their employer's corporate SAML IdP. Its relevant condition is: Each partner user must be associated with a Contact and a permitted Salesforce partner account. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: The new provider returns a different subject value but the person must retain the original account.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A government agency allows its constituent services to federate from a trusted national IdP. Its relevant condition is: The IdP issues a stable subject claim, but the site currently keys users by mutable display names. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: The new provider returns a different subject value but the person must retain the original account.
Question 635
The team adopts this approach: Use an approved account-linking process with proof of identity and stable mapping between providers. The original project scenario is: A customer already has an Experience Cloud user and signs in through a newly added OIDC provider. Which verification outcome best demonstrates that it worked?
- Name changes do not create duplicate users or alter account permissions.
- A store manager signs in and manages only their franchise's allowed business records.
- The customer retains order history without automatically trusting matching email claims.
- No later SSO attempt or previous session can reveal former partner records.
Explanation
Correct Answer
C:Best. The verification target is: The customer retains order history without automatically trusting matching email claims. It tests whether the chosen approach—Use an approved account-linking process with proof of identity and stable mapping between providers.—actually resolves the specific finding: The new provider returns a different subject value but the person must retain the original account.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A government agency allows its constituent services to federate from a trusted national IdP. Its relevant condition is: The IdP issues a stable subject claim, but the site currently keys users by mutable display names. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: The customer retains order history without automatically trusting matching email claims.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A franchise creates Experience Cloud accounts for independent stores using one Salesforce org. Its relevant condition is: The user directory contains multiple stores with similar email domains, but their data boundaries differ. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: The customer retains order history without automatically trusting matching email claims.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner is removed from a retailer's supplier network after a contract termination. Its relevant condition is: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: The customer retains order history without automatically trusting matching email claims.
Question 636
A project manager declines to address this finding: The new provider returns a different subject value but the person must retain the original account. The related project is: A customer already has an Experience Cloud user and signs in through a newly added OIDC provider. Which consequence most directly follows?
- Matching solely on email lets an attacker claim a customer's preexisting CRM account.
- An unverified linking decision merges two different customers into one user.
- An updated surname causes reassignment to a different citizen's Salesforce record.
- A mislinked Contact permits the partner to inspect another distributor's customer data.
Explanation
Correct Answer
B:Best. The most direct failure is: An unverified linking decision merges two different customers into one user. It is a consequence of the documented condition: The new provider returns a different subject value but the person must retain the original account. A mitigation is: Use an approved account-linking process with proof of identity and stable mapping between providers.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An online retailer lets customers sign in using a supported OpenID Connect social provider. Its relevant condition is: The existing site lacks a safe registration handler to match first-time identity claims to Contacts. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: An unverified linking decision merges two different customers into one user.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A government agency allows its constituent services to federate from a trusted national IdP. Its relevant condition is: The IdP issues a stable subject claim, but the site currently keys users by mutable display names. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: An unverified linking decision merges two different customers into one user.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional distributor wants partners to authenticate through their employer's corporate SAML IdP. Its relevant condition is: Each partner user must be associated with a Contact and a permitted Salesforce partner account. The present case instead turns on: The new provider returns a different subject value but the person must retain the original account. The direct answer here is: An unverified linking decision merges two different customers into one user.
Question 637
In this fictional project, A partner is removed from a retailer's supplier network after a contract termination. The project team has uncovered that Their identity provider can still authenticate but they must lose Salesforce record access immediately. Which action is best supported by those facts?
- Implement supported provider discovery and country-specific federation settings with consistent validation.
- Use a stable verified federation identifier and controlled identity-to-Contact association.
- Deactivate or remove the associated external site user and revoke active sessions while closing sharing grants.
- Compare the publisher's JIT external-user requirements and update the approved provisioning handler.
Explanation
Correct Answer
C:Best. The most direct action is to deactivate or remove the associated external site user and revoke active sessions while closing sharing grants. It is supported by the specific finding that Their identity provider can still authenticate but they must lose Salesforce record access immediately. The expected acceptance evidence is: No later SSO attempt or previous session can reveal former partner records.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2C portal supports customers from several countries through different approved IdPs. Its relevant condition is: The configuration sends all users to one provider and assumes each national identity source has the same format. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: Deactivate or remove the associated external site user and revoke active sessions while closing sharing grants.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A government agency allows its constituent services to federate from a trusted national IdP. Its relevant condition is: The IdP issues a stable subject claim, but the site currently keys users by mutable display names. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: Deactivate or remove the associated external site user and revoke active sessions while closing sharing grants.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A supplier partner SAML login validates the signature but Salesforce rejects user creation. Its relevant condition is: The SAML JIT attributes omit required Contact or Account information for an external user. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: Deactivate or remove the associated external site user and revoke active sessions while closing sharing grants.
Question 638
An enterprise review begins with this business situation: A partner is removed from a retailer's supplier network after a contract termination. Which technical or process signal best identifies the obstacle?
- The configuration sends all users to one provider and assumes each national identity source has the same format.
- Their identity provider can still authenticate but they must lose Salesforce record access immediately.
- The IdP issues a stable subject claim, but the site currently keys users by mutable display names.
- The existing site lacks a safe registration handler to match first-time identity claims to Contacts.
Explanation
Correct Answer
B:Best. The decisive observation is: Their identity provider can still authenticate but they must lose Salesforce record access immediately. This is why the design response should be: Deactivate or remove the associated external site user and revoke active sessions while closing sharing grants.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2C portal supports customers from several countries through different approved IdPs. Its relevant condition is: The configuration sends all users to one provider and assumes each national identity source has the same format. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: Their identity provider can still authenticate but they must lose Salesforce record access immediately.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A government agency allows its constituent services to federate from a trusted national IdP. Its relevant condition is: The IdP issues a stable subject claim, but the site currently keys users by mutable display names. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: Their identity provider can still authenticate but they must lose Salesforce record access immediately.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An online retailer lets customers sign in using a supported OpenID Connect social provider. Its relevant condition is: The existing site lacks a safe registration handler to match first-time identity claims to Contacts. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: Their identity provider can still authenticate but they must lose Salesforce record access immediately.
Question 639
The team adopts this approach: Deactivate or remove the associated external site user and revoke active sessions while closing sharing grants. The original project scenario is: A partner is removed from a retailer's supplier network after a contract termination. Which verification outcome best demonstrates that it worked?
- No later SSO attempt or previous session can reveal former partner records.
- Name changes do not create duplicate users or alter account permissions.
- Each customer signs in at the correct trusted IdP and maps to a single scoped external identity.
- A store manager signs in and manages only their franchise's allowed business records.
Explanation
Correct Answer
A:Best. The verification target is: No later SSO attempt or previous session can reveal former partner records. It tests whether the chosen approach—Deactivate or remove the associated external site user and revoke active sessions while closing sharing grants.—actually resolves the specific finding: Their identity provider can still authenticate but they must lose Salesforce record access immediately.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A government agency allows its constituent services to federate from a trusted national IdP. Its relevant condition is: The IdP issues a stable subject claim, but the site currently keys users by mutable display names. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: No later SSO attempt or previous session can reveal former partner records.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A B2C portal supports customers from several countries through different approved IdPs. Its relevant condition is: The configuration sends all users to one provider and assumes each national identity source has the same format. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: No later SSO attempt or previous session can reveal former partner records.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A franchise creates Experience Cloud accounts for independent stores using one Salesforce org. Its relevant condition is: The user directory contains multiple stores with similar email domains, but their data boundaries differ. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: No later SSO attempt or previous session can reveal former partner records.
Question 640
A project manager declines to address this finding: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The related project is: A partner is removed from a retailer's supplier network after a contract termination. Which consequence most directly follows?
- An authentic assertion from a valid but terminated partner continues to grant sensitive access.
- Matching solely on email lets an attacker claim a customer's preexisting CRM account.
- A mislinked Contact permits the partner to inspect another distributor's customer data.
- A broad external sharing rule exposes orders and contracts across competing franchisees.
Explanation
Correct Answer
A:Best. The most direct failure is: An authentic assertion from a valid but terminated partner continues to grant sensitive access. It is a consequence of the documented condition: Their identity provider can still authenticate but they must lose Salesforce record access immediately. A mitigation is: Deactivate or remove the associated external site user and revoke active sessions while closing sharing grants.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An online retailer lets customers sign in using a supported OpenID Connect social provider. Its relevant condition is: The existing site lacks a safe registration handler to match first-time identity claims to Contacts. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: An authentic assertion from a valid but terminated partner continues to grant sensitive access.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A regional distributor wants partners to authenticate through their employer's corporate SAML IdP. Its relevant condition is: Each partner user must be associated with a Contact and a permitted Salesforce partner account. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: An authentic assertion from a valid but terminated partner continues to grant sensitive access.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A franchise creates Experience Cloud accounts for independent stores using one Salesforce org. Its relevant condition is: The user directory contains multiple stores with similar email domains, but their data boundaries differ. The present case instead turns on: Their identity provider can still authenticate but they must lose Salesforce record access immediately. The direct answer here is: An authentic assertion from a valid but terminated partner continues to grant sensitive access.