mcAfee Secure Website
exam =5
exam =6

Exam Code: Certified Platform Identity and Access Management Architect

Exam Name: Certified Platform Identity and Access Management Architect

Certification Provider: Salesforce

Salesforce Certified Platform Identity and Access Management Architect Questions & Answers

Reliable & Actual Study Materials for Certified Platform Identity and Access Management Architect Exam Success

58 Questions & Answers with Testing Engine

"Certified Platform Identity and Access Management Architect: Certified Platform Identity and Access Management Architect" Testing Engine covers all the knowledge points of the real Salesforce Certified Platform Identity and Access Management Architect exam.

The latest actual Certified Platform Identity and Access Management Architect Questions & Answers from Pass4sure. Everything you need to prepare and get best score at Certified Platform Identity and Access Management Architect exam easily and quickly.

exam =7
Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Salesforce Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Was: $137.49
Now: $124.99

Salesforce Certified Platform Identity and Access Management Architect Practice Test 5

Question 40

A public-sector agency will accept signed assertions from a separately administered identity domain. Best complete IAM decision record?

  1. Action: Define trusted issuer, certificate or signing-key verification, audience and endpoint registration before enabling federation. Verification: Follow the login redirects, assertion issuer and target audience. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed.
  2. Action: Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required. Verification: Inspect signed metadata, certificate rotation plan, assertion audience and ACS URL. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements.
  3. Action: Evaluate Just-in-Time user creation versus pre-provisioning based on lifecycle and entitlement needs. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user.
  4. Action: Define trusted issuer, certificate or signing-key verification, audience and endpoint registration before enabling federation. Verification: Inspect signed metadata, certificate rotation plan, assertion audience and ACS URL. Boundary: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user.

Explanation

Correct Answer

D:

“Action: Define trusted issuer, certificate or signing-key verification, audience and endpoint registration before enabling federation. Verification: Inspect signed metadata, certificate rotation plan, assertion audience and ACS URL. Boundary: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user” addresses the access-design responsibilities in a public-sector agency will accept signed assertions from a separately administered identity domain Test against inspect signed metadata, certificate rotation plan, assertion audience and ACS URL; a signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user.

Incorrect Answers

A:

“Action: Define trusted issuer, certificate or signing-key verification, audience and endpoint registration before enabling federation. Verification: Follow the login redirects, assertion issuer and target audience. Boundary: A branding or domain change can break authentication even when user credentials and permissions have not changed” may apply to a related identity task, but it does not establish inspect signed metadata, certificate rotation plan, assertion audience and ACS URL for a public-sector agency will accept signed assertions from a separately administered identity domain The controlling boundary is: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user.

B:

“Action: Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required. Verification: Inspect signed metadata, certificate rotation plan, assertion audience and ACS URL. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements” may apply to a related identity task, but it does not establish inspect signed metadata, certificate rotation plan, assertion audience and ACS URL for a public-sector agency will accept signed assertions from a separately administered identity domain The controlling boundary is: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user.

C:

“Action: Evaluate Just-in-Time user creation versus pre-provisioning based on lifecycle and entitlement needs. Verification: Inventory ACS URLs, OAuth redirect URIs, custom domain routing and login history after cutover. Boundary: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user” may apply to a related identity task, but it does not establish inspect signed metadata, certificate rotation plan, assertion audience and ACS URL for a public-sector agency will accept signed assertions from a separately administered identity domain The controlling boundary is: A signed message from an unknown issuer or the wrong audience must not automatically authenticate a Salesforce user.

Question 41

Two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone. Best next IAM response?

  1. Use a stable unique federation subject mapping and plan conflict-safe account matching
  2. Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements
  3. Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required
  4. Investigate assertion time conditions and authoritative clock synchronization before changing user rights

Explanation

Correct Answer

A:

“Use a stable unique federation subject mapping and plan conflict-safe account matching” addresses the access-design responsibilities in two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone Test against inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; display names and mutable email addresses may be unreliable identity keys.

Incorrect Answers

B:

“Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

C:

“Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

D:

“Investigate assertion time conditions and authoritative clock synchronization before changing user rights” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

Question 42

Two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone. Most decisive verification?

  1. Check metadata update, active certificate fingerprint, error codes and rollback path
  2. Record initial URL, authentication request, relay target and completed session destination
  3. Compare HR events, directory account changes, Salesforce active status and delayed sync recovery
  4. Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes

Explanation

Correct Answer

D:

“Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes” distinguishes sign-in from entitlement administration in two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone It checks whether use a stable unique federation subject mapping and plan conflict-safe account matching.

Incorrect Answers

A:

“Check metadata update, active certificate fingerprint, error codes and rollback path” needs to be evaluated against Two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

B:

“Record initial URL, authentication request, relay target and completed session destination” needs to be evaluated against Two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

C:

“Compare HR events, directory account changes, Salesforce active status and delayed sync recovery” needs to be evaluated against Two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

Question 43

Two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone. Key caution for this case?

  1. A successful identity-provider change does not guarantee relying applications automatically trust the replacement key
  2. Even a correctly authenticated external subject must not gain access to another tenant's records by default
  3. The system hosting the application is not necessarily the system authenticating credentials
  4. Display names and mutable email addresses may be unreliable identity keys

Explanation

Correct Answer

D:

“Display names and mutable email addresses may be unreliable identity keys” needs to be evaluated against Two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

Incorrect Answers

A:

“A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” needs to be evaluated against Two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

B:

“Even a correctly authenticated external subject must not gain access to another tenant's records by default” needs to be evaluated against Two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

C:

“The system hosting the application is not necessarily the system authenticating credentials” needs to be evaluated against Two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

Question 44

Two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone. Best complete IAM decision record?

  1. Action: Use a stable unique federation subject mapping and plan conflict-safe account matching. Verification: Record initial URL, authentication request, relay target and completed session destination. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.
  2. Action: Use a stable unique federation subject mapping and plan conflict-safe account matching. Verification: Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes. Boundary: Display names and mutable email addresses may be unreliable identity keys.
  3. Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Check metadata update, active certificate fingerprint, error codes and rollback path. Boundary: Display names and mutable email addresses may be unreliable identity keys.
  4. Action: Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required. Verification: Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes. Boundary: Even a correctly authenticated external subject must not gain access to another tenant's records by default.

Explanation

Correct Answer

B:

“Action: Use a stable unique federation subject mapping and plan conflict-safe account matching. Verification: Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes. Boundary: Display names and mutable email addresses may be unreliable identity keys” addresses the access-design responsibilities in two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone Test against inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; display names and mutable email addresses may be unreliable identity keys.

Incorrect Answers

A:

“Action: Use a stable unique federation subject mapping and plan conflict-safe account matching. Verification: Record initial URL, authentication request, relay target and completed session destination. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

C:

“Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Check metadata update, active certificate fingerprint, error codes and rollback path. Boundary: Display names and mutable email addresses may be unreliable identity keys” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

D:

“Action: Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required. Verification: Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes. Boundary: Even a correctly authenticated external subject must not gain access to another tenant's records by default” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for two employees share an email display alias after a corporate rename, and the SSO mapping uses email alone The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

Question 45

A directory consolidation changes employee email addresses while stable workforce IDs remain unchanged. Best next IAM response?

  1. Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required
  2. Use a stable unique federation subject mapping and plan conflict-safe account matching
  3. Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements
  4. Investigate assertion time conditions and authoritative clock synchronization before changing user rights

Explanation

Correct Answer

B:

“Use a stable unique federation subject mapping and plan conflict-safe account matching” addresses the access-design responsibilities in a directory consolidation changes employee email addresses while stable workforce IDs remain unchanged Test against inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; display names and mutable email addresses may be unreliable identity keys.

Incorrect Answers

A:

“Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for a directory consolidation changes employee email addresses while stable workforce IDs remain unchanged The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

C:

“Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for a directory consolidation changes employee email addresses while stable workforce IDs remain unchanged The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

D:

“Investigate assertion time conditions and authoritative clock synchronization before changing user rights” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for a directory consolidation changes employee email addresses while stable workforce IDs remain unchanged The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

Question 46

A directory consolidation changes employee email addresses while stable workforce IDs remain unchanged. Most decisive verification?

  1. Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes
  2. Compare HR events, directory account changes, Salesforce active status and delayed sync recovery
  3. Check metadata update, active certificate fingerprint, error codes and rollback path
  4. Record initial URL, authentication request, relay target and completed session destination

Explanation

Correct Answer

A:

“Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes” distinguishes sign-in from entitlement administration in a directory consolidation changes employee email addresses while stable workforce IDs remain unchanged It checks whether use a stable unique federation subject mapping and plan conflict-safe account matching.

Incorrect Answers

B:

“Compare HR events, directory account changes, Salesforce active status and delayed sync recovery” needs to be evaluated against A directory consolidation changes employee email addresses while stable workforce IDs remain unchanged. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

C:

“Check metadata update, active certificate fingerprint, error codes and rollback path” needs to be evaluated against A directory consolidation changes employee email addresses while stable workforce IDs remain unchanged. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

D:

“Record initial URL, authentication request, relay target and completed session destination” needs to be evaluated against A directory consolidation changes employee email addresses while stable workforce IDs remain unchanged. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

Question 47

A directory consolidation changes employee email addresses while stable workforce IDs remain unchanged. Key caution for this case?

  1. Display names and mutable email addresses may be unreliable identity keys
  2. A successful identity-provider change does not guarantee relying applications automatically trust the replacement key
  3. The system hosting the application is not necessarily the system authenticating credentials
  4. Even a correctly authenticated external subject must not gain access to another tenant's records by default

Explanation

Correct Answer

A:

“Display names and mutable email addresses may be unreliable identity keys” needs to be evaluated against A directory consolidation changes employee email addresses while stable workforce IDs remain unchanged. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

Incorrect Answers

B:

“A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” needs to be evaluated against A directory consolidation changes employee email addresses while stable workforce IDs remain unchanged. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

C:

“The system hosting the application is not necessarily the system authenticating credentials” needs to be evaluated against A directory consolidation changes employee email addresses while stable workforce IDs remain unchanged. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

D:

“Even a correctly authenticated external subject must not gain access to another tenant's records by default” needs to be evaluated against A directory consolidation changes employee email addresses while stable workforce IDs remain unchanged. The relevant check is Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; Display names and mutable email addresses may be unreliable identity keys.

Question 48

A directory consolidation changes employee email addresses while stable workforce IDs remain unchanged. Best complete IAM decision record?

  1. Action: Use a stable unique federation subject mapping and plan conflict-safe account matching. Verification: Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes. Boundary: Display names and mutable email addresses may be unreliable identity keys.
  2. Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Check metadata update, active certificate fingerprint, error codes and rollback path. Boundary: Display names and mutable email addresses may be unreliable identity keys.
  3. Action: Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required. Verification: Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes. Boundary: Even a correctly authenticated external subject must not gain access to another tenant's records by default.
  4. Action: Use a stable unique federation subject mapping and plan conflict-safe account matching. Verification: Record initial URL, authentication request, relay target and completed session destination. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

Explanation

Correct Answer

A:

“Action: Use a stable unique federation subject mapping and plan conflict-safe account matching. Verification: Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes. Boundary: Display names and mutable email addresses may be unreliable identity keys” addresses the access-design responsibilities in a directory consolidation changes employee email addresses while stable workforce IDs remain unchanged Test against inspect federation identifier uniqueness, migration map and duplicate-user test outcomes; display names and mutable email addresses may be unreliable identity keys.

Incorrect Answers

B:

“Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Check metadata update, active certificate fingerprint, error codes and rollback path. Boundary: Display names and mutable email addresses may be unreliable identity keys” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for a directory consolidation changes employee email addresses while stable workforce IDs remain unchanged The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

C:

“Action: Distinguish identity assertions from API authorization grants and use a suitable authenticated identity protocol when user login is required. Verification: Inspect federation identifier uniqueness, migration map and duplicate-user test outcomes. Boundary: Even a correctly authenticated external subject must not gain access to another tenant's records by default” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for a directory consolidation changes employee email addresses while stable workforce IDs remain unchanged The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

D:

“Action: Use a stable unique federation subject mapping and plan conflict-safe account matching. Verification: Record initial URL, authentication request, relay target and completed session destination. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” may apply to a related identity task, but it does not establish inspect federation identifier uniqueness, migration map and duplicate-user test outcomes for a directory consolidation changes employee email addresses while stable workforce IDs remain unchanged The controlling boundary is: Display names and mutable email addresses may be unreliable identity keys.

Question 49

A helpdesk says Salesforce can authenticate external users but cannot explain which system serves as the service provider. Best next IAM response?

  1. Match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application
  2. Trace which party verifies credentials and which party consumes the identity assertion for the actual sign-in
  3. Decouple trusted authentication from tenant-specific authorization and enforce scoped privileges after account matching
  4. Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements

Explanation

Correct Answer

B:

“Trace which party verifies credentials and which party consumes the identity assertion for the actual sign-in” addresses the access-design responsibilities in a helpdesk says Salesforce can authenticate external users but cannot explain which system serves as the service provider Test against follow the login redirects, assertion issuer and target audience; the system hosting the application is not necessarily the system authenticating credentials.

Incorrect Answers

A:

“Match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application” may apply to a related identity task, but it does not establish follow the login redirects, assertion issuer and target audience for a helpdesk says Salesforce can authenticate external users but cannot explain which system serves as the service provider The controlling boundary is: The system hosting the application is not necessarily the system authenticating credentials.

C:

“Decouple trusted authentication from tenant-specific authorization and enforce scoped privileges after account matching” may apply to a related identity task, but it does not establish follow the login redirects, assertion issuer and target audience for a helpdesk says Salesforce can authenticate external users but cannot explain which system serves as the service provider The controlling boundary is: The system hosting the application is not necessarily the system authenticating credentials.

D:

“Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements” may apply to a related identity task, but it does not establish follow the login redirects, assertion issuer and target audience for a helpdesk says Salesforce can authenticate external users but cannot explain which system serves as the service provider The controlling boundary is: The system hosting the application is not necessarily the system authenticating credentials.

Question 50

A helpdesk says Salesforce can authenticate external users but cannot explain which system serves as the service provider. Most decisive verification?

  1. Check metadata update, active certificate fingerprint, error codes and rollback path
  2. Examine NotBefore, NotOnOrAfter, system time offsets and error logs
  3. Validate tenant claims, user mapping, assigned permissions and unauthorized cross-tenant access tests
  4. Follow the login redirects, assertion issuer and target audience

Explanation

Correct Answer

D:

“Follow the login redirects, assertion issuer and target audience” distinguishes sign-in from entitlement administration in a helpdesk says Salesforce can authenticate external users but cannot explain which system serves as the service provider It checks whether trace which party verifies credentials and which party consumes the identity assertion for the actual sign-in.

Incorrect Answers

A:

“Check metadata update, active certificate fingerprint, error codes and rollback path” needs to be evaluated against A helpdesk says Salesforce can authenticate external users but cannot explain which system serves as the service provider. The relevant check is Follow the login redirects, assertion issuer and target audience; The system hosting the application is not necessarily the system authenticating credentials.

B:

“Examine NotBefore, NotOnOrAfter, system time offsets and error logs” needs to be evaluated against A helpdesk says Salesforce can authenticate external users but cannot explain which system serves as the service provider. The relevant check is Follow the login redirects, assertion issuer and target audience; The system hosting the application is not necessarily the system authenticating credentials.

C:

“Validate tenant claims, user mapping, assigned permissions and unauthorized cross-tenant access tests” needs to be evaluated against A helpdesk says Salesforce can authenticate external users but cannot explain which system serves as the service provider. The relevant check is Follow the login redirects, assertion issuer and target audience; The system hosting the application is not necessarily the system authenticating credentials.

Certified Platform Identity and Access Management Architect Practice Tests