Salesforce Certified Platform Identity and Access Management Architect Practice Test 19
Question 180
An enterprise review begins with this business situation: A company wants Salesforce to authenticate employees who already sign into a SAML-compatible corporate IdP. Which technical or process signal best identifies the obstacle?
- 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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in.
- The site's identity requirements allow a reviewed external social authentication provider.
Explanation
Correct Answer
A:Best. The decisive observation is: The identity source issues signed browser SAML assertions and controls the employee MFA policy. This is why the design response should be: Choose supported SAML SSO with Salesforce as service provider and verify federation trust.
Incorrect Answers
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: The identity source issues signed browser SAML assertions and controls the employee MFA policy. The direct answer here is: The identity source issues signed browser SAML assertions and controls the employee MFA policy.
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 identity source issues signed browser SAML assertions and controls the employee MFA policy. The direct answer here is: The identity source issues signed browser SAML assertions and controls the employee MFA policy.
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 identity source issues signed browser SAML assertions and controls the employee MFA policy. The direct answer here is: The identity source issues signed browser SAML assertions and controls the employee MFA policy.
Question 181
The team adopts this approach: Choose supported SAML SSO with Salesforce as service provider and verify federation trust. The original project scenario is: A company wants Salesforce to authenticate employees who already sign into a SAML-compatible corporate IdP. Which verification outcome best demonstrates that it worked?
- Salesforce establishes a session after validating identity evidence from the financial institution.
- 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.
Explanation
Correct Answer
C:Best. The verification target is: Employee browsers enter Salesforce from the approved corporate IdP without password replication. It tests whether the chosen approach—Choose supported SAML SSO with Salesforce as service provider and verify federation trust.—actually resolves the specific finding: The identity source issues signed browser SAML assertions and controls the employee MFA policy.
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 identity source issues signed browser SAML assertions and controls the employee MFA policy. The direct answer here is: Employee browsers enter Salesforce from the approved corporate IdP without password replication.
B: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 identity source issues signed browser SAML assertions and controls the employee MFA policy. The direct answer here is: Employee browsers enter Salesforce from the approved corporate IdP without password replication.
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 identity source issues signed browser SAML assertions and controls the employee MFA policy. The direct answer here is: Employee browsers enter Salesforce from the approved corporate IdP without password replication.
Question 182
A project manager declines to address this finding: The identity source issues signed browser SAML assertions and controls the employee MFA policy. The related project is: A company wants Salesforce to authenticate employees who already sign into a SAML-compatible corporate IdP. Which consequence most directly follows?
- 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.
- Using an access token without issuer/audience validation permits account impersonation.
Explanation
Correct Answer
C:Best. The most direct failure is: The team tries an OAuth client-credentials flow for employee interactive SSO. It is a consequence of the documented condition: The identity source issues signed browser SAML assertions and controls the employee MFA policy. A mitigation is: Choose supported SAML SSO with Salesforce as service provider and verify federation trust.
Incorrect Answers
A: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 identity source issues signed browser SAML assertions and controls the employee MFA policy. The direct answer here is: The team tries an OAuth client-credentials flow for employee interactive SSO.
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 identity source issues signed browser SAML assertions and controls the employee MFA policy. The direct answer here is: The team tries an OAuth client-credentials flow for employee interactive SSO.
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: The identity source issues signed browser SAML assertions and controls the employee MFA policy. The direct answer here is: The team tries an OAuth client-credentials flow for employee interactive SSO.
Question 183
An integration architect receives this requirement: A digital subscription service has customers authenticating with an external OpenID Connect provider. A technical discovery also finds: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. Which response most directly addresses the present constraint?
- Distinguish delegated authentication's credential-verification callout from token-scoped OAuth or federated sign-in.
- Configure an OpenID Connect authentication provider and controlled registration handler for Salesforce or its site.
- Choose the format supported by the selected IdP and configure protocol-specific signature and claim validation.
- Use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping.
Explanation
Correct Answer
B:Best. The most direct action is to configure an OpenID Connect authentication provider and controlled registration handler for Salesforce or its site. It is supported by the specific finding that the provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The expected acceptance evidence is: Returning customers are identified through validated OIDC identity claims and mapped users.
Incorrect Answers
A: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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: Configure an OpenID Connect authentication provider and controlled registration handler for Salesforce or its site.
C: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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: Configure an OpenID Connect authentication provider and controlled registration handler for Salesforce or its site.
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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: Configure an OpenID Connect authentication provider and controlled registration handler for Salesforce or its site.
Question 184
Consider the following hypothetical Salesforce initiative: A digital subscription service has customers authenticating with an external OpenID Connect provider. Which evidence would most strongly explain the current integration weakness?
- The design document calls both protocols identical because each can support web SSO.
- 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 site's identity requirements allow a reviewed external social authentication provider.
Explanation
Correct Answer
C:Best. The decisive observation is: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. This is why the design response should be: Configure an OpenID Connect authentication provider and controlled registration handler for Salesforce or its site.
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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in.
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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in.
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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in.
Question 185
Review this change: Configure an OpenID Connect authentication provider and controlled registration handler for Salesforce or its site. It addresses a project where A digital subscription service has customers authenticating with an external OpenID Connect provider. Which result should appear in integration acceptance evidence?
- Returning customers are identified through validated OIDC identity claims and mapped users.
- The supplier portal handles only its registered SAML or OIDC identity evidence correctly.
- 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
A:Best. The verification target is: Returning customers are identified through validated OIDC identity claims and mapped users. It tests whether the chosen approach—Configure an OpenID Connect authentication provider and controlled registration handler for Salesforce or its site.—actually resolves the specific finding: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in.
Incorrect Answers
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: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: Returning customers are identified through validated OIDC identity claims and mapped users.
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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: Returning customers are identified through validated OIDC identity claims and mapped users.
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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: Returning customers are identified through validated OIDC identity claims and mapped users.
Question 186
Suppose the integration design proceeds without correcting this issue: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. In the environment A digital subscription service has customers authenticating with an external OpenID Connect provider. What should the risk register emphasize?
- Using an access token without issuer/audience validation permits account impersonation.
- Automatically trusting social email alone merges two unrelated member accounts.
- 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.
Explanation
Correct Answer
A:Best. The most direct failure is: Using an access token without issuer/audience validation permits account impersonation. It is a consequence of the documented condition: The provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. A mitigation is: Configure an OpenID Connect authentication provider and controlled registration handler for Salesforce or its site.
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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: Using an access token without issuer/audience validation permits account impersonation.
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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: Using an access token without issuer/audience validation permits account impersonation.
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 provider supplies signed ID tokens through a documented OIDC authorization-code-based sign-in. The direct answer here is: Using an access token without issuer/audience validation permits account impersonation.
Question 187
Salesforce and its partners face the following situation: A regional service business wants its members to sign in with a supported social identity account. The integration review notes: The site's identity requirements allow a reviewed external social authentication provider. Which architectural step should take priority?
- Choose the format supported by the selected IdP and configure protocol-specific signature and claim validation.
- Use a trusted federation approach, such as SAML or supported OIDC, with necessary user mapping.
- Configure an OpenID Connect authentication provider and controlled registration handler for Salesforce or its site.
- Evaluate Salesforce authentication provider support and a safe new-user registration handler.
Explanation
Correct Answer
D:Best. The most direct action is to evaluate Salesforce authentication provider support and a safe new-user registration handler. It is supported by the specific finding that the site's identity requirements allow a reviewed external social authentication provider. The expected acceptance evidence is: Members complete an authorized social login and are matched to the correct external-user record.
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 site's identity requirements allow a reviewed external social authentication provider. The direct answer here is: Evaluate Salesforce authentication provider support and a safe new-user registration handler.
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 site's identity requirements allow a reviewed external social authentication provider. The direct answer here is: Evaluate Salesforce authentication provider support and a safe new-user registration handler.
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 site's identity requirements allow a reviewed external social authentication provider. The direct answer here is: Evaluate Salesforce authentication provider support and a safe new-user registration handler.
Question 188
An implementation team investigates this scenario: A regional service business wants its members to sign in with a supported social identity account. Which finding would most directly justify a change to the integration architecture?
- The design document calls both protocols identical because each can support web SSO.
- The site's identity requirements allow a reviewed external social authentication provider.
- Salesforce receives proof of authentication from the institution but may not handle account passwords.
- The identity source issues signed browser SAML assertions and controls the employee MFA policy.
Explanation
Correct Answer
B:Best. The decisive observation is: The site's identity requirements allow a reviewed external social authentication provider. This is why the design response should be: 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 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 site's identity requirements allow a reviewed external social authentication provider. The direct answer here is: The site's identity requirements allow a reviewed external social authentication 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 site's identity requirements allow a reviewed external social authentication provider. The direct answer here is: The site's identity requirements allow a reviewed external social authentication provider.
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 site's identity requirements allow a reviewed external social authentication provider. The direct answer here is: The site's identity requirements allow a reviewed external social authentication provider.
Question 189
A solution review asks whether this control is effective: Evaluate Salesforce authentication provider support and a safe new-user registration handler. The business setting is: A regional service business wants its members to sign in with a supported social identity account. What should a demonstrable successful outcome be?
- 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.
- 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.
Explanation
Correct Answer
B:Best. The verification target is: Members complete an authorized social login and are matched to the correct external-user record. It tests whether the chosen approach—Evaluate Salesforce authentication provider support and a safe new-user registration handler.—actually resolves the specific finding: The site's identity requirements allow a reviewed external social authentication provider.
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: Members complete an authorized social login and are matched to the correct external-user record.
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 site's identity requirements allow a reviewed external social authentication provider. The direct answer here is: Members complete an authorized social login and are matched to the correct external-user record.
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 site's identity requirements allow a reviewed external social authentication provider. The direct answer here is: Members complete an authorized social login and are matched to the correct external-user record.
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.