cert
cert-1
cert-2

Pass Salesforce Certified Platform Identity and Access Management Architect Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
Certified Platform Identity and Access Management Architect Exam - Verified By Experts
Certified Platform Identity and Access Management Architect Premium File

Certified Platform Identity and Access Management Architect Premium File

$69.99
$76.99
  • Premium File 58 Questions & Answers. Last Update: Nov 17, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 10 downloads in the last 7 days
block-screenshots
Salesforce Certified Platform Identity and Access Management Architect Practice Test 12

Question 110

An architect must create an acceptance test after choosing: Correct the client redirect-URI registration and verify exact authorization endpoint and app identity. For the situation An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Which result most directly proves success?

  1. Login succeeds across affected orgs with the intended trusted signing certificate.
  2. An assertion targeted at the production service provider is accepted after proper validation.
  3. The assertion maps to the correct existing Salesforce account without accidental user duplication.
  4. The registered client completes its authorization flow only at an approved callback URL.

Explanation

Correct Answer

D:

Best. The verification target is: The registered client completes its authorization flow only at an approved callback URL. It tests whether the chosen approach—Correct the client redirect-URI registration and verify exact authorization endpoint and app identity.—actually resolves the specific finding: The callback URL in the authorization request does not match the registered app redirect configuration.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: The registered client completes its authorization flow only at an approved callback URL.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: The registered client completes its authorization flow only at an approved callback URL.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: The registered client completes its authorization flow only at an approved callback URL.

Question 111

An incident scenario concerns this architecture: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. The team has discovered: The callback URL in the authorization request does not match the registered app redirect configuration. Which project risk requires explicit mitigation?

  1. Admins disable assertion validation instead of correcting the environment mismatch.
  2. Treating a SAML assertion as an OAuth API token leaves the SSO flow incorrectly designed.
  3. A valid employee is repeatedly rejected or provisioned as another identity.
  4. Allowing arbitrary redirect URIs exposes the authorization result to attacker-controlled endpoints.

Explanation

Correct Answer

D:

Best. The most direct failure is: Allowing arbitrary redirect URIs exposes the authorization result to attacker-controlled endpoints. It is a consequence of the documented condition: The callback URL in the authorization request does not match the registered app redirect configuration. A mitigation is: Correct the client redirect-URI registration and verify exact authorization endpoint and app identity.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: Allowing arbitrary redirect URIs exposes the authorization result to attacker-controlled endpoints.

B:

Not best for this scenario. This option is associated with another type of requirement: A global manufacturer wants its workforce to access Salesforce and several SaaS applications after one corporate sign-in. Its relevant condition is: The existing workforce IdP can issue signed SAML assertions, while Salesforce must consume the authentication. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: Allowing arbitrary redirect URIs exposes the authorization result to attacker-controlled endpoints.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The callback URL in the authorization request does not match the registered app redirect configuration. The direct answer here is: Allowing arbitrary redirect URIs exposes the authorization result to attacker-controlled endpoints.

Question 112

An integration architect receives this requirement: A server-to-server integration fails with invalid_grant after a JWT-based OAuth rollout. A technical discovery also finds: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. Which response most directly addresses the present constraint?

  1. Compare both initiation paths, relay destination and SAML login history before changing access policies.
  2. Inspect NameID or federation identifier and user matching, then align immutable account identifiers.
  3. Inspect JWT signature, audience, issuer, subject, expiry and prior authorization settings.
  4. Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.

Explanation

Correct Answer

C:

Best. The most direct action is to inspect JWT signature, audience, issuer, subject, expiry and prior authorization settings. It is supported by the specific finding that the signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The expected acceptance evidence is: A correctly signed and scoped assertion receives an access token without password storage.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: Inspect JWT signature, audience, issuer, subject, expiry and prior authorization settings.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: Inspect JWT signature, audience, issuer, subject, expiry and prior authorization settings.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: Inspect JWT signature, audience, issuer, subject, expiry and prior authorization settings.

Question 113

Consider the following hypothetical Salesforce initiative: A server-to-server integration fails with invalid_grant after a JWT-based OAuth rollout. Which evidence would most strongly explain the current integration weakness?

  1. The callback URL in the authorization request does not match the registered app redirect configuration.
  2. The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org.
  3. The IdP sends a new employee email address while Salesforce user matching uses Federation ID.
  4. The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState.

Explanation

Correct Answer

B:

Best. The decisive observation is: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. This is why the design response should be: Inspect JWT signature, audience, issuer, subject, expiry and prior authorization settings.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Its relevant condition is: The callback URL in the authorization request does not match the registered app redirect configuration. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org.

Question 114

Review this change: Inspect JWT signature, audience, issuer, subject, expiry and prior authorization settings. It addresses a project where A server-to-server integration fails with invalid_grant after a JWT-based OAuth rollout. Which result should appear in integration acceptance evidence?

  1. An assertion targeted at the production service provider is accepted after proper validation.
  2. Approved entry points direct the user to the expected Salesforce page with valid authentication.
  3. A correctly signed and scoped assertion receives an access token without password storage.
  4. Login succeeds across affected orgs with the intended trusted signing certificate.

Explanation

Correct Answer

C:

Best. The verification target is: A correctly signed and scoped assertion receives an access token without password storage. It tests whether the chosen approach—Inspect JWT signature, audience, issuer, subject, expiry and prior authorization settings.—actually resolves the specific finding: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: A correctly signed and scoped assertion receives an access token without password storage.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: A correctly signed and scoped assertion receives an access token without password storage.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: A correctly signed and scoped assertion receives an access token without password storage.

Question 115

Suppose the integration design proceeds without correcting this issue: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. In the environment A server-to-server integration fails with invalid_grant after a JWT-based OAuth rollout. What should the risk register emphasize?

  1. Admins disable assertion validation instead of correcting the environment mismatch.
  2. A misrouted RelayState is wrongly diagnosed as a user-permission problem.
  3. The team disables token checks or embeds human passwords to hide a configuration issue.
  4. A valid employee is repeatedly rejected or provisioned as another identity.

Explanation

Correct Answer

C:

Best. The most direct failure is: The team disables token checks or embeds human passwords to hide a configuration issue. It is a consequence of the documented condition: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. A mitigation is: Inspect JWT signature, audience, issuer, subject, expiry and prior authorization settings.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: The team disables token checks or embeds human passwords to hide a configuration issue.

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Its relevant condition is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: The team disables token checks or embeds human passwords to hide a configuration issue.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The direct answer here is: The team disables token checks or embeds human passwords to hide a configuration issue.

Question 116

An integration architect receives this requirement: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. A technical discovery also finds: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. Which response most directly addresses the present constraint?

  1. Compare the active signature certificate with trusted metadata, then rotate without weakening signature checks.
  2. Compare both initiation paths, relay destination and SAML login history before changing access policies.
  3. Correct the client redirect-URI registration and verify exact authorization endpoint and app identity.
  4. Inspect the SAML assertion and Salesforce SSO configuration; correct entity IDs and audience mapping.

Explanation

Correct Answer

B:

Best. The most direct action is to compare both initiation paths, relay destination and SAML login history before changing access policies. It is supported by the specific finding that the flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The expected acceptance evidence is: Approved entry points direct the user to the expected Salesforce page with valid authentication.

Incorrect Answers

A:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: Compare both initiation paths, relay destination and SAML login history before changing access policies.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Its relevant condition is: The callback URL in the authorization request does not match the registered app redirect configuration. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: Compare both initiation paths, relay destination and SAML login history before changing access policies.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: Compare both initiation paths, relay destination and SAML login history before changing access policies.

Question 117

Consider the following hypothetical Salesforce initiative: A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Which evidence would most strongly explain the current integration weakness?

  1. The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState.
  2. The IdP uses a destination string copied from a sandbox while the user is signing into production.
  3. The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs.
  4. The IdP sends a new employee email address while Salesforce user matching uses Federation ID.

Explanation

Correct Answer

A:

Best. The decisive observation is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. This is why the design response should be: Compare both initiation paths, relay destination and SAML login history before changing access policies.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: Salesforce rejects a newly deployed SAML integration with an invalid assertion audience error. Its relevant condition is: The IdP uses a destination string copied from a sandbox while the user is signing into production. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A group of employees receives intermittent SAML signature failures after an identity-provider certificate rollover. Its relevant condition is: The IdP rotated keys, but metadata and signing trust were not updated consistently across Salesforce orgs. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState.

Question 118

Review this change: Compare both initiation paths, relay destination and SAML login history before changing access policies. It addresses a project where A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. Which result should appear in integration acceptance evidence?

  1. Approved entry points direct the user to the expected Salesforce page with valid authentication.
  2. Suspended identities lose interactive and programmatic access within the documented control window.
  3. The registered client completes its authorization flow only at an approved callback URL.
  4. A correctly signed and scoped assertion receives an access token without password storage.

Explanation

Correct Answer

A:

Best. The verification target is: Approved entry points direct the user to the expected Salesforce page with valid authentication. It tests whether the chosen approach—Compare both initiation paths, relay destination and SAML login history before changing access policies.—actually resolves the specific finding: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState.

Incorrect Answers

B:

Not best for this scenario. This option is associated with another type of requirement: A partner identity is suspended at the corporate IdP, but a long-lived Salesforce API token remains usable. Its relevant condition is: The current design treats authentication termination as though it automatically revokes every issued token. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: Approved entry points direct the user to the expected Salesforce page with valid authentication.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Its relevant condition is: The callback URL in the authorization request does not match the registered app redirect configuration. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: Approved entry points direct the user to the expected Salesforce page with valid authentication.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-to-server integration fails with invalid_grant after a JWT-based OAuth rollout. Its relevant condition is: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: Approved entry points direct the user to the expected Salesforce page with valid authentication.

Question 119

Suppose the integration design proceeds without correcting this issue: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. In the environment A partner reports sporadic SSO failures only when opening Salesforce from a bookmarked application link. What should the risk register emphasize?

  1. A misrouted RelayState is wrongly diagnosed as a user-permission problem.
  2. A valid employee is repeatedly rejected or provisioned as another identity.
  3. Allowing arbitrary redirect URIs exposes the authorization result to attacker-controlled endpoints.
  4. The team disables token checks or embeds human passwords to hide a configuration issue.

Explanation

Correct Answer

A:

Best. The most direct failure is: A misrouted RelayState is wrongly diagnosed as a user-permission problem. It is a consequence of the documented condition: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. A mitigation is: Compare both initiation paths, relay destination and SAML login history before changing access policies.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A browser SSO login returns a valid assertion but Salesforce cannot find the intended existing user. Its relevant condition is: The IdP sends a new employee email address while Salesforce user matching uses Federation ID. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: A misrouted RelayState is wrongly diagnosed as a user-permission problem.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An OAuth client receives invalid_redirect_uri after its administrator migrates from test to production. Its relevant condition is: The callback URL in the authorization request does not match the registered app redirect configuration. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: A misrouted RelayState is wrongly diagnosed as a user-permission problem.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A server-to-server integration fails with invalid_grant after a JWT-based OAuth rollout. Its relevant condition is: The signed JWT uses an expired timestamp and the wrong Salesforce audience for the target org. The present case instead turns on: The flow differs between IdP-initiated and service-provider-initiated login, and one entry point lacks correct RelayState. The direct answer here is: A misrouted RelayState is wrongly diagnosed as a user-permission problem.

Question 120

An integration architect receives this requirement: A parent company uses a central workforce IdP to authenticate employees to Salesforce Service Cloud. A technical discovery also finds: Salesforce receives SAML assertions from the corporate IdP rather than verifying user passwords itself. Which response most directly addresses the present constraint?

  1. Configure Salesforce as the SAML service provider with matching issuer, ACS, entity and certificate settings.
  2. Use a service-provider-initiated SAML SSO flow with an approved return destination.
  3. Review the Salesforce login policy, My Domain authentication service configuration and controlled fallback access.
  4. Design multiple SAML SSO configurations with deterministic identity routing and separate certificate trust.

Explanation

Correct Answer

A:

Best. The most direct action is to configure Salesforce as the SAML service provider with matching issuer, ACS, entity and certificate settings. It is supported by the specific finding that Salesforce receives SAML assertions from the corporate IdP rather than verifying user passwords itself. The expected acceptance evidence is: Employees authenticate at the IdP and enter Salesforce through validated assertions.

Incorrect Answers

B:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A field engineer opens a Salesforce deep link without a prior application session. Its relevant condition is: The business requires Salesforce to redirect to the enterprise IdP before resuming the requested page. The present case instead turns on: Salesforce receives SAML assertions from the corporate IdP rather than verifying user passwords itself. The direct answer here is: Configure Salesforce as the SAML service provider with matching issuer, ACS, entity and certificate settings.

C:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A security officer worries that employees will still type Salesforce credentials despite enterprise SSO. Its relevant condition is: The corporate IdP authentication page is working, but direct login pathways remain outside the intended policy. The present case instead turns on: Salesforce receives SAML assertions from the corporate IdP rather than verifying user passwords itself. The direct answer here is: Configure Salesforce as the SAML service provider with matching issuer, ACS, entity and certificate settings.

D:

Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A merged enterprise has two corporate IdPs during a gradual identity consolidation. Its relevant condition is: The workforce populations use different trusted assertion issuers and need separate SSO entry points. The present case instead turns on: Salesforce receives SAML assertions from the corporate IdP rather than verifying user passwords itself. The direct answer here is: Configure Salesforce as the SAML service provider with matching issuer, ACS, entity and certificate settings.

Certified Platform Identity and Access Management Architect Practice Tests