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 25

Question 240

An identity team points SAML to a retired Salesforce login URL after a domain migration. Best complete IAM decision record?

  1. Action: Correct the registered service provider audience, recipient, ACS and active site endpoint rather than changing permissions. Verification: Test handler user matching, account creation, least-privilege assignment and safe exception rollback. Boundary: Display name, address or shared email alias is not a safe primary unique identity key.
  2. Action: Configure Salesforce as the SAML service provider for trusted third-party identity assertions and maintain local authorization. Verification: Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error. Boundary: Salesforce acting as a SAML service provider is not the organization that issued or verified the employee password.
  3. Action: Diagnose cryptographic trust using approved IdP metadata and correct certificate rotation. Verification: Validate OIDC issuer, client settings, callback, verified user claims and registration handler outcomes. Boundary: A permission-set change cannot fix an assertion that is addressed to the wrong service provider.
  4. Action: Correct the registered service provider audience, recipient, ACS and active site endpoint rather than changing permissions. Verification: Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error. Boundary: A permission-set change cannot fix an assertion that is addressed to the wrong service provider.

Explanation

Correct Answer

D:

“Action: Correct the registered service provider audience, recipient, ACS and active site endpoint rather than changing permissions. Verification: Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error. Boundary: A permission-set change cannot fix an assertion that is addressed to the wrong service provider” addresses the access-design responsibilities in an identity team points SAML to a retired Salesforce login URL after a domain migration Test against compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error; a permission-set change cannot fix an assertion that is addressed to the wrong service provider.

Incorrect Answers

A:

“Action: Correct the registered service provider audience, recipient, ACS and active site endpoint rather than changing permissions. Verification: Test handler user matching, account creation, least-privilege assignment and safe exception rollback. Boundary: Display name, address or shared email alias is not a safe primary unique identity key” may apply to a related identity task, but it does not establish compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error for an identity team points SAML to a retired Salesforce login URL after a domain migration The controlling boundary is: A permission-set change cannot fix an assertion that is addressed to the wrong service provider.

B:

“Action: Configure Salesforce as the SAML service provider for trusted third-party identity assertions and maintain local authorization. Verification: Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error. Boundary: Salesforce acting as a SAML service provider is not the organization that issued or verified the employee password” may apply to a related identity task, but it does not establish compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error for an identity team points SAML to a retired Salesforce login URL after a domain migration The controlling boundary is: A permission-set change cannot fix an assertion that is addressed to the wrong service provider.

C:

“Action: Diagnose cryptographic trust using approved IdP metadata and correct certificate rotation. Verification: Validate OIDC issuer, client settings, callback, verified user claims and registration handler outcomes. Boundary: A permission-set change cannot fix an assertion that is addressed to the wrong service provider” may apply to a related identity task, but it does not establish compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error for an identity team points SAML to a retired Salesforce login URL after a domain migration The controlling boundary is: A permission-set change cannot fix an assertion that is addressed to the wrong service provider.

Question 241

A SAML assertion is rejected because the identity provider's clock is several minutes ahead. Best next IAM response?

  1. Diagnose clock drift and temporal assertion conditions with authoritative time synchronization
  2. Agree on an unambiguous NameID or federation identifier claim before accepting the identity
  3. Implement a supported secured provisioning integration with stable user identifiers, least privilege and reconciliation
  4. Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT

Explanation

Correct Answer

A:

“Diagnose clock drift and temporal assertion conditions with authoritative time synchronization” addresses the access-design responsibilities in a SAML assertion is rejected because the identity provider's clock is several minutes ahead Test against inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; disabling temporal validation is not an acceptable workaround for clock-skew problems.

Incorrect Answers

B:

“Agree on an unambiguous NameID or federation identifier claim before accepting the identity” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a SAML assertion is rejected because the identity provider's clock is several minutes ahead The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

C:

“Implement a supported secured provisioning integration with stable user identifiers, least privilege and reconciliation” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a SAML assertion is rejected because the identity provider's clock is several minutes ahead The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

D:

“Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a SAML assertion is rejected because the identity provider's clock is several minutes ahead The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

Question 242

A SAML assertion is rejected because the identity provider's clock is several minutes ahead. Most decisive verification?

  1. Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets
  2. Inspect FederationIdentifier values, SAML NameID, duplicate users and first-login creation trace
  3. Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error
  4. Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs

Explanation

Correct Answer

A:

“Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets” distinguishes sign-in from entitlement administration in a SAML assertion is rejected because the identity provider's clock is several minutes ahead It checks whether diagnose clock drift and temporal assertion conditions with authoritative time synchronization.

Incorrect Answers

B:

“Inspect FederationIdentifier values, SAML NameID, duplicate users and first-login creation trace” needs to be evaluated against A SAML assertion is rejected because the identity provider's clock is several minutes ahead. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

C:

“Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error” needs to be evaluated against A SAML assertion is rejected because the identity provider's clock is several minutes ahead. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

D:

“Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs” needs to be evaluated against A SAML assertion is rejected because the identity provider's clock is several minutes ahead. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

Question 243

A SAML assertion is rejected because the identity provider's clock is several minutes ahead. Key caution for this case?

  1. Disabling temporal validation is not an acceptable workaround for clock-skew problems
  2. A successful external authentication alone does not prove Salesforce can provision a license-valid user record
  3. Renaming an identity must not silently provision a second account with more access
  4. A provider's presence on a login page does not prove it is authorized for every account population

Explanation

Correct Answer

A:

“Disabling temporal validation is not an acceptable workaround for clock-skew problems” needs to be evaluated against A SAML assertion is rejected because the identity provider's clock is several minutes ahead. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

Incorrect Answers

B:

“A successful external authentication alone does not prove Salesforce can provision a license-valid user record” needs to be evaluated against A SAML assertion is rejected because the identity provider's clock is several minutes ahead. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

C:

“Renaming an identity must not silently provision a second account with more access” needs to be evaluated against A SAML assertion is rejected because the identity provider's clock is several minutes ahead. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

D:

“A provider's presence on a login page does not prove it is authorized for every account population” needs to be evaluated against A SAML assertion is rejected because the identity provider's clock is several minutes ahead. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

Question 244

A SAML assertion is rejected because the identity provider's clock is several minutes ahead. Best complete IAM decision record?

  1. Action: Agree on an unambiguous NameID or federation identifier claim before accepting the identity. Verification: Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets. Boundary: A successful external authentication alone does not prove Salesforce can provision a license-valid user record.
  2. Action: Diagnose clock drift and temporal assertion conditions with authoritative time synchronization. Verification: Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems.
  3. Action: Implement a supported secured provisioning integration with stable user identifiers, least privilege and reconciliation. Verification: Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems.
  4. Action: Diagnose clock drift and temporal assertion conditions with authoritative time synchronization. Verification: Inspect FederationIdentifier values, SAML NameID, duplicate users and first-login creation trace. Boundary: A provider's presence on a login page does not prove it is authorized for every account population.

Explanation

Correct Answer

B:

“Action: Diagnose clock drift and temporal assertion conditions with authoritative time synchronization. Verification: Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems” addresses the access-design responsibilities in a SAML assertion is rejected because the identity provider's clock is several minutes ahead Test against inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; disabling temporal validation is not an acceptable workaround for clock-skew problems.

Incorrect Answers

A:

“Action: Agree on an unambiguous NameID or federation identifier claim before accepting the identity. Verification: Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets. Boundary: A successful external authentication alone does not prove Salesforce can provision a license-valid user record” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a SAML assertion is rejected because the identity provider's clock is several minutes ahead The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

C:

“Action: Implement a supported secured provisioning integration with stable user identifiers, least privilege and reconciliation. Verification: Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a SAML assertion is rejected because the identity provider's clock is several minutes ahead The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

D:

“Action: Diagnose clock drift and temporal assertion conditions with authoritative time synchronization. Verification: Inspect FederationIdentifier values, SAML NameID, duplicate users and first-login creation trace. Boundary: A provider's presence on a login page does not prove it is authorized for every account population” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a SAML assertion is rejected because the identity provider's clock is several minutes ahead The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

Question 245

A multi-region company sees intermittent SSO failures when server time and token validity windows disagree. Best next IAM response?

  1. Agree on an unambiguous NameID or federation identifier claim before accepting the identity
  2. Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT
  3. Implement a supported secured provisioning integration with stable user identifiers, least privilege and reconciliation
  4. Diagnose clock drift and temporal assertion conditions with authoritative time synchronization

Explanation

Correct Answer

D:

“Diagnose clock drift and temporal assertion conditions with authoritative time synchronization” addresses the access-design responsibilities in a multi-region company sees intermittent SSO failures when server time and token validity windows disagree Test against inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; disabling temporal validation is not an acceptable workaround for clock-skew problems.

Incorrect Answers

A:

“Agree on an unambiguous NameID or federation identifier claim before accepting the identity” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a multi-region company sees intermittent SSO failures when server time and token validity windows disagree The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

B:

“Add an authoritative deprovisioning and session-revocation workflow independent of login-time JIT” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a multi-region company sees intermittent SSO failures when server time and token validity windows disagree The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

C:

“Implement a supported secured provisioning integration with stable user identifiers, least privilege and reconciliation” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a multi-region company sees intermittent SSO failures when server time and token validity windows disagree The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

Question 246

A multi-region company sees intermittent SSO failures when server time and token validity windows disagree. Most decisive verification?

  1. Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets
  2. Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs
  3. Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error
  4. Inspect FederationIdentifier values, SAML NameID, duplicate users and first-login creation trace

Explanation

Correct Answer

A:

“Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets” distinguishes sign-in from entitlement administration in a multi-region company sees intermittent SSO failures when server time and token validity windows disagree It checks whether diagnose clock drift and temporal assertion conditions with authoritative time synchronization.

Incorrect Answers

B:

“Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs” needs to be evaluated against A multi-region company sees intermittent SSO failures when server time and token validity windows disagree. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

C:

“Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error” needs to be evaluated against A multi-region company sees intermittent SSO failures when server time and token validity windows disagree. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

D:

“Inspect FederationIdentifier values, SAML NameID, duplicate users and first-login creation trace” needs to be evaluated against A multi-region company sees intermittent SSO failures when server time and token validity windows disagree. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

Question 247

A multi-region company sees intermittent SSO failures when server time and token validity windows disagree. Key caution for this case?

  1. A successful external authentication alone does not prove Salesforce can provision a license-valid user record
  2. Disabling temporal validation is not an acceptable workaround for clock-skew problems
  3. A provider's presence on a login page does not prove it is authorized for every account population
  4. Renaming an identity must not silently provision a second account with more access

Explanation

Correct Answer

B:

“Disabling temporal validation is not an acceptable workaround for clock-skew problems” needs to be evaluated against A multi-region company sees intermittent SSO failures when server time and token validity windows disagree. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

Incorrect Answers

A:

“A successful external authentication alone does not prove Salesforce can provision a license-valid user record” needs to be evaluated against A multi-region company sees intermittent SSO failures when server time and token validity windows disagree. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

C:

“A provider's presence on a login page does not prove it is authorized for every account population” needs to be evaluated against A multi-region company sees intermittent SSO failures when server time and token validity windows disagree. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

D:

“Renaming an identity must not silently provision a second account with more access” needs to be evaluated against A multi-region company sees intermittent SSO failures when server time and token validity windows disagree. The relevant check is Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; Disabling temporal validation is not an acceptable workaround for clock-skew problems.

Question 248

A multi-region company sees intermittent SSO failures when server time and token validity windows disagree. Best complete IAM decision record?

  1. Action: Agree on an unambiguous NameID or federation identifier claim before accepting the identity. Verification: Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets. Boundary: A successful external authentication alone does not prove Salesforce can provision a license-valid user record.
  2. Action: Diagnose clock drift and temporal assertion conditions with authoritative time synchronization. Verification: Inspect FederationIdentifier values, SAML NameID, duplicate users and first-login creation trace. Boundary: A provider's presence on a login page does not prove it is authorized for every account population.
  3. Action: Implement a supported secured provisioning integration with stable user identifiers, least privilege and reconciliation. Verification: Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems.
  4. Action: Diagnose clock drift and temporal assertion conditions with authoritative time synchronization. Verification: Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

Explanation

Correct Answer

D:

“Action: Diagnose clock drift and temporal assertion conditions with authoritative time synchronization. Verification: Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems” addresses the access-design responsibilities in a multi-region company sees intermittent SSO failures when server time and token validity windows disagree Test against inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets; disabling temporal validation is not an acceptable workaround for clock-skew problems.

Incorrect Answers

A:

“Action: Agree on an unambiguous NameID or federation identifier claim before accepting the identity. Verification: Inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets. Boundary: A successful external authentication alone does not prove Salesforce can provision a license-valid user record” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a multi-region company sees intermittent SSO failures when server time and token validity windows disagree The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

B:

“Action: Diagnose clock drift and temporal assertion conditions with authoritative time synchronization. Verification: Inspect FederationIdentifier values, SAML NameID, duplicate users and first-login creation trace. Boundary: A provider's presence on a login page does not prove it is authorized for every account population” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a multi-region company sees intermittent SSO failures when server time and token validity windows disagree The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

C:

“Action: Implement a supported secured provisioning integration with stable user identifiers, least privilege and reconciliation. Verification: Inspect signed subject, unique mapping field, duplicate-name tests and account resolution logs. Boundary: Disabling temporal validation is not an acceptable workaround for clock-skew problems” may apply to a related identity task, but it does not establish inspect time stamps, NotBefore, NotOnOrAfter and observed server offsets for a multi-region company sees intermittent SSO failures when server time and token validity windows disagree The controlling boundary is: Disabling temporal validation is not an acceptable workaround for clock-skew problems.

Question 249

A user enters through an IdP app tile and the returned RelayState is constructed from untrusted request parameters. Best next IAM response?

  1. Use the supported Salesforce authentication-provider integration with claim validation and account registration mapping
  2. Implement a controlled authentication provider and registration handler mapping for the external customer population
  3. Supply and validate all required user, profile and relationship attributes for the chosen JIT provisioning mode
  4. Preserve approved destination state without accepting arbitrary external redirect targets

Explanation

Correct Answer

D:

“Preserve approved destination state without accepting arbitrary external redirect targets” addresses the access-design responsibilities in a user enters through an IdP app tile and the returned RelayState is constructed from untrusted request parameters Test against review RelayState handling, target allowlists, request correlation and open-redirect tests; a successful SAML login does not make an unvalidated post-login destination safe.

Incorrect Answers

A:

“Use the supported Salesforce authentication-provider integration with claim validation and account registration mapping” may apply to a related identity task, but it does not establish review RelayState handling, target allowlists, request correlation and open-redirect tests for a user enters through an IdP app tile and the returned RelayState is constructed from untrusted request parameters The controlling boundary is: A successful SAML login does not make an unvalidated post-login destination safe.

B:

“Implement a controlled authentication provider and registration handler mapping for the external customer population” may apply to a related identity task, but it does not establish review RelayState handling, target allowlists, request correlation and open-redirect tests for a user enters through an IdP app tile and the returned RelayState is constructed from untrusted request parameters The controlling boundary is: A successful SAML login does not make an unvalidated post-login destination safe.

C:

“Supply and validate all required user, profile and relationship attributes for the chosen JIT provisioning mode” may apply to a related identity task, but it does not establish review RelayState handling, target allowlists, request correlation and open-redirect tests for a user enters through an IdP app tile and the returned RelayState is constructed from untrusted request parameters The controlling boundary is: A successful SAML login does not make an unvalidated post-login destination safe.

Question 250

A user enters through an IdP app tile and the returned RelayState is constructed from untrusted request parameters. Most decisive verification?

  1. Test name or email changes against unchanged federation identifiers and audit links
  2. Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error
  3. Validate accepted issuer IDs, signing keys, user identifiers and regional login test cases
  4. Review RelayState handling, target allowlists, request correlation and open-redirect tests

Explanation

Correct Answer

D:

“Review RelayState handling, target allowlists, request correlation and open-redirect tests” distinguishes sign-in from entitlement administration in a user enters through an IdP app tile and the returned RelayState is constructed from untrusted request parameters It checks whether preserve approved destination state without accepting arbitrary external redirect targets.

Incorrect Answers

A:

“Test name or email changes against unchanged federation identifiers and audit links” needs to be evaluated against A user enters through an IdP app tile and the returned RelayState is constructed from untrusted request parameters. The relevant check is Review RelayState handling, target allowlists, request correlation and open-redirect tests; A successful SAML login does not make an unvalidated post-login destination safe.

B:

“Compare Destination, AudienceRestriction, ACS, My Domain and the exact SAML error” needs to be evaluated against A user enters through an IdP app tile and the returned RelayState is constructed from untrusted request parameters. The relevant check is Review RelayState handling, target allowlists, request correlation and open-redirect tests; A successful SAML login does not make an unvalidated post-login destination safe.

C:

“Validate accepted issuer IDs, signing keys, user identifiers and regional login test cases” needs to be evaluated against A user enters through an IdP app tile and the returned RelayState is constructed from untrusted request parameters. The relevant check is Review RelayState handling, target allowlists, request correlation and open-redirect tests; A successful SAML login does not make an unvalidated post-login destination safe.

Certified Platform Identity and Access Management Architect Practice Tests