Salesforce Certified Platform Identity and Access Management Architect Practice Test 20
Question 190
A Salesforce integration initiative faces this situation: A regional service business wants its members to sign in with a supported social identity account. The critical observation is: The site's identity requirements allow a reviewed external social authentication provider. What failure is most likely if it is ignored?
- A custom password form inside Salesforce duplicates credentials and violates central authentication policy.
- The team tries an OAuth client-credentials flow for employee interactive SSO.
- 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
C:Best. The most direct failure is: Automatically trusting social email alone merges two unrelated member accounts. It is a consequence of the documented condition: The site's identity requirements allow a reviewed external social authentication provider. A mitigation is: Evaluate Salesforce authentication provider support and a safe new-user registration handler.
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 site's identity requirements allow a reviewed external social authentication provider. The direct answer here is: Automatically trusting social email alone merges two unrelated member accounts.
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 site's identity requirements allow a reviewed external social authentication provider. The direct answer here is: Automatically trusting social email alone merges two unrelated member accounts.
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 site's identity requirements allow a reviewed external social authentication provider. The direct answer here is: Automatically trusting social email alone merges two unrelated member accounts.
Question 191
An architecture board reviews a proposed Salesforce integration. Context: A financial institution insists the customer's authentication occurs only at its enterprise IdP. Finding: Salesforce receives proof of authentication from the institution but may not handle account passwords. Which decision best resolves the concern?
- Use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping.
- Choose supported SAML SSO with Salesforce as service provider and verify federation trust.
- Distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in.
- Choose the format supported by the selected IdP and configure protocol-specific signature and claim validation.
Explanation
Correct Answer
A:Best. The most direct action is to use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping. It is supported by the specific finding that Salesforce receives proof of authentication from the institution but may not handle account passwords. The expected acceptance evidence is: Salesforce establishes a session after validating identity evidence from the financial institution.
Incorrect Answers
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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: Use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping.
C: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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: Use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping.
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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: Use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping.
Question 192
A design workshop describes this environment: A financial institution insists the customer's authentication occurs only at its enterprise IdP. Which concrete observation should be documented as the most decisive issue?
- 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 architecture confuses delegated password validation with OAuth authorization scopes.
- The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in.
Explanation
Correct Answer
B:Best. The decisive observation is: Salesforce receives proof of authentication from the institution but may not handle account passwords. This is why the design response should be: Use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping.
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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: Salesforce receives proof of authentication from the institution but may not handle account passwords.
C: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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: Salesforce receives proof of authentication from the institution but may not handle account passwords.
D: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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: Salesforce receives proof of authentication from the institution but may not handle account passwords.
Question 193
An architect must create an acceptance test after choosing: Use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping. For the situation A financial institution insists the customer's authentication occurs only at its enterprise IdP. Which result most directly proves success?
- Employee browsers enter Salesforce from the approved corporate IdP without password replication.
- Salesforce establishes a session after validating identity evidence from the financial institution.
- Members complete an authorized social login and are matched to the correct external-user record.
- Partners and consumers follow their permitted sign-in path and receive appropriately scoped sessions.
Explanation
Correct Answer
B:Best. The verification target is: Salesforce establishes a session after validating identity evidence from the financial institution. It tests whether the chosen approach—Use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping.—actually resolves the specific finding: Salesforce receives proof of authentication from the institution but may not handle account passwords.
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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: Salesforce establishes a session after validating identity evidence from the financial institution.
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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: Salesforce establishes a session after validating identity evidence from the financial institution.
D: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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: Salesforce establishes a session after validating identity evidence from the financial institution.
Question 194
An incident scenario concerns this architecture: A financial institution insists the customer's authentication occurs only at its enterprise IdP. The team has discovered: Salesforce receives proof of authentication from the institution but may not handle account passwords. Which project risk requires explicit mitigation?
- Automatically trusting social email alone merges two unrelated member accounts.
- An OIDC token is posted to the SAML assertion-consumer endpoint and fails authentication.
- A customer social login is accepted for sensitive partner administrator access without extra checks.
- A custom password form inside Salesforce duplicates credentials and violates central authentication policy.
Explanation
Correct Answer
D:Best. The most direct failure is: A custom password form inside Salesforce duplicates credentials and violates central authentication policy. It is a consequence of the documented condition: Salesforce receives proof of authentication from the institution but may not handle account passwords. A mitigation is: Use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping.
Incorrect Answers
A: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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: A custom password form inside Salesforce duplicates credentials and violates central authentication policy.
B: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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: A custom password form inside Salesforce duplicates credentials and violates central authentication policy.
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: Salesforce receives proof of authentication from the institution but may not handle account passwords. The direct answer here is: A custom password form inside Salesforce duplicates credentials and violates central authentication policy.
Question 195
Salesforce and its partners face the following situation: A payroll application sends a custom delegated authentication request to an old Salesforce implementation. The integration review notes: The architecture confuses delegated password validation with OAuth authorization scopes. Which architectural step should take priority?
- Distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in.
- Evaluate Salesforce authentication provider support and a safe new-user registration handler.
- Configure an OpenID Connect authentication provider and controlled registration handler for Salesforce or its site.
- Configure approved authentication choices per audience and validate routing to the intended provider.
Explanation
Correct Answer
A:Best. The most direct action is to distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in. It is supported by the specific finding that the architecture confuses delegated password validation with OAuth authorization scopes. The expected acceptance evidence is: The solution selects a supported mechanism matching the required interactive authentication behavior.
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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: Distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in.
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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: Distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in.
D: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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: Distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in.
Question 196
An implementation team investigates this scenario: A payroll application sends a custom delegated authentication request to an old Salesforce implementation. 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 architecture confuses delegated password validation with OAuth authorization scopes.
- The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in.
- The design document calls both protocols identical because each can support web SSO.
Explanation
Correct Answer
B:Best. The decisive observation is: The architecture confuses delegated password validation with OAuth authorization scopes. This is why the design response should be: Distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in.
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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: The architecture confuses delegated password validation with OAuth authorization scopes.
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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: The architecture confuses delegated password validation with OAuth authorization scopes.
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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: The architecture confuses delegated password validation with OAuth authorization scopes.
Question 197
A solution review asks whether this control is effective: Distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in. The business setting is: A payroll application sends a custom delegated authentication request to an old Salesforce implementation. What should a demonstrable successful outcome be?
- Partners and consumers follow their permitted sign-in path and receive appropriately scoped sessions.
- The solution selects a supported mechanism matching the required interactive authentication behavior.
- Employee browsers enter Salesforce from the approved corporate IdP without password replication.
- Members complete an authorized social login and are matched to the correct external-user record.
Explanation
Correct Answer
B:Best. The verification target is: The solution selects a supported mechanism matching the required interactive authentication behavior. It tests whether the chosen approach—Distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in.—actually resolves the specific finding: The architecture confuses delegated password validation with OAuth authorization scopes.
Incorrect Answers
A: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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: The solution selects a supported mechanism matching the required interactive authentication behavior.
C: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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: The solution selects a supported mechanism matching the required interactive authentication behavior.
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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: The solution selects a supported mechanism matching the required interactive authentication behavior.
Question 198
A Salesforce integration initiative faces this situation: A payroll application sends a custom delegated authentication request to an old Salesforce implementation. The critical observation is: The architecture confuses delegated password validation with OAuth authorization scopes. What failure is most likely if it is ignored?
- The team tries an OAuth client-credentials flow for employee interactive SSO.
- A customer social login is accepted for sensitive partner administrator access without extra checks.
- The team disables signature verification rather than resolving a provisioning constraint.
- An OAuth client token is incorrectly treated as a replacement for human password verification.
Explanation
Correct Answer
D:Best. The most direct failure is: An OAuth client token is incorrectly treated as a replacement for human password verification. It is a consequence of the documented condition: The architecture confuses delegated password validation with OAuth authorization scopes. A mitigation is: Distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in.
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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: An OAuth client token is incorrectly treated as a replacement for human password verification.
B: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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: An OAuth client token is incorrectly treated as a replacement for human password verification.
C:Not best for this scenario. This option is associated with another type of requirement: 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 architecture confuses delegated password validation with OAuth authorization scopes. The direct answer here is: An OAuth client token is incorrectly treated as a replacement for human password verification.
Question 199
Salesforce and its partners face the following situation: A public Experience Cloud site wants business partners and casual customers to use different IdPs. The integration review notes: The two populations have different assurance, licensing and contact-account relationships. Which architectural step should take priority?
- Choose supported SAML SSO with Salesforce as service provider and verify federation trust.
- 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.
- Distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in.
Explanation
Correct Answer
B:Best. The most direct action is to configure approved authentication choices per audience and validate routing to the intended provider. It is supported by the specific finding that the two populations have different assurance, licensing and contact-account relationships. The expected acceptance evidence is: Partners and consumers follow their permitted sign-in path and receive appropriately scoped sessions.
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: Configure approved authentication choices per audience and validate routing to the intended provider.
C: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: Configure approved authentication choices per audience and validate routing to the intended provider.
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 two populations have different assurance, licensing and contact-account relationships. The direct answer here is: Configure approved authentication choices per audience and validate routing to the intended provider.
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.