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 3

Question 20

A B2C shopping site needs customer identity claims at sign-in while its separate fulfillment API needs delegated access. Best complete IAM decision record?

  1. Action: Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements.
  2. Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: Cryptographic signature validity alone cannot make an assertion with the wrong audience acceptable.
  3. Action: Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants. Verification: Follow the login redirects, assertion issuer and target audience. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.
  4. Action: Evaluate delegated authentication versus federated SSO in the context of current support, trust and credential-handling requirements. Verification: Test first login, required attributes, inactive status, license assignment and onboarding delay. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements.

Explanation

Correct Answer

A:

“Action: Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements” addresses the access-design responsibilities in a B2C shopping site needs customer identity claims at sign-in while its separate fulfillment API needs delegated access Test against review relying-party requirements, scopes, claims, token audiences and redirect flow; OIDC authentication and OAuth resource authorization solve related but different requirements.

Incorrect Answers

B:

“Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: Cryptographic signature validity alone cannot make an assertion with the wrong audience acceptable” may apply to a related identity task, but it does not establish review relying-party requirements, scopes, claims, token audiences and redirect flow for a B2C shopping site needs customer identity claims at sign-in while its separate fulfillment API needs delegated access The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.

C:

“Action: Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants. Verification: Follow the login redirects, assertion issuer and target audience. 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 review relying-party requirements, scopes, claims, token audiences and redirect flow for a B2C shopping site needs customer identity claims at sign-in while its separate fulfillment API needs delegated access The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.

D:

“Action: Evaluate delegated authentication versus federated SSO in the context of current support, trust and credential-handling requirements. Verification: Test first login, required attributes, inactive status, license assignment and onboarding delay. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements” may apply to a related identity task, but it does not establish review relying-party requirements, scopes, claims, token audiences and redirect flow for a B2C shopping site needs customer identity claims at sign-in while its separate fulfillment API needs delegated access The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.

Question 21

An employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data. Best next IAM response?

  1. Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements
  2. Use a stable unique federation subject mapping and plan conflict-safe account matching
  3. Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants
  4. Evaluate delegated authentication versus federated SSO in the context of current support, trust and credential-handling requirements

Explanation

Correct Answer

C:

“Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants” addresses the access-design responsibilities in an employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data Test against review relying-party requirements, scopes, claims, token audiences and redirect flow; OIDC authentication and OAuth resource authorization solve related but different requirements.

Incorrect Answers

A:

“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 review relying-party requirements, scopes, claims, token audiences and redirect flow for an employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.

B:

“Use a stable unique federation subject mapping and plan conflict-safe account matching” may apply to a related identity task, but it does not establish review relying-party requirements, scopes, claims, token audiences and redirect flow for an employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.

D:

“Evaluate delegated authentication versus federated SSO in the context of current support, trust and credential-handling requirements” may apply to a related identity task, but it does not establish review relying-party requirements, scopes, claims, token audiences and redirect flow for an employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.

Question 22

An employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data. Most decisive verification?

  1. Follow the login redirects, assertion issuer and target audience
  2. Test first login, required attributes, inactive status, license assignment and onboarding delay
  3. Verify provisioning feed events, assignment mapping, timing and reconciliation of failures
  4. Review relying-party requirements, scopes, claims, token audiences and redirect flow

Explanation

Correct Answer

D:

“Review relying-party requirements, scopes, claims, token audiences and redirect flow” distinguishes sign-in from entitlement administration in an employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data It checks whether select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants.

Incorrect Answers

A:

“Follow the login redirects, assertion issuer and target audience” needs to be evaluated against An employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data. The relevant check is Review relying-party requirements, scopes, claims, token audiences and redirect flow; OIDC authentication and OAuth resource authorization solve related but different requirements.

B:

“Test first login, required attributes, inactive status, license assignment and onboarding delay” needs to be evaluated against An employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data. The relevant check is Review relying-party requirements, scopes, claims, token audiences and redirect flow; OIDC authentication and OAuth resource authorization solve related but different requirements.

C:

“Verify provisioning feed events, assignment mapping, timing and reconciliation of failures” needs to be evaluated against An employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data. The relevant check is Review relying-party requirements, scopes, claims, token audiences and redirect flow; OIDC authentication and OAuth resource authorization solve related but different requirements.

Question 23

An employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data. 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. Cryptographic signature validity alone cannot make an assertion with the wrong audience acceptable
  4. OIDC authentication and OAuth resource authorization solve related but different requirements

Explanation

Correct Answer

D:

“OIDC authentication and OAuth resource authorization solve related but different requirements” needs to be evaluated against An employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data. The relevant check is Review relying-party requirements, scopes, claims, token audiences and redirect flow; OIDC authentication and OAuth resource authorization solve related but different requirements.

Incorrect Answers

A:

“A successful identity-provider change does not guarantee relying applications automatically trust the replacement key” needs to be evaluated against An employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data. The relevant check is Review relying-party requirements, scopes, claims, token audiences and redirect flow; OIDC authentication and OAuth resource authorization solve related but different requirements.

B:

“Even a correctly authenticated external subject must not gain access to another tenant's records by default” needs to be evaluated against An employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data. The relevant check is Review relying-party requirements, scopes, claims, token audiences and redirect flow; OIDC authentication and OAuth resource authorization solve related but different requirements.

C:

“Cryptographic signature validity alone cannot make an assertion with the wrong audience acceptable” needs to be evaluated against An employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data. The relevant check is Review relying-party requirements, scopes, claims, token audiences and redirect flow; OIDC authentication and OAuth resource authorization solve related but different requirements.

Question 24

An employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data. Best complete IAM decision record?

  1. Action: Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements.
  2. Action: Evaluate delegated authentication versus federated SSO in the context of current support, trust and credential-handling requirements. Verification: Test first login, required attributes, inactive status, license assignment and onboarding delay. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements.
  3. Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: Cryptographic signature validity alone cannot make an assertion with the wrong audience acceptable.
  4. Action: Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants. Verification: Follow the login redirects, assertion issuer and target audience. Boundary: A successful identity-provider change does not guarantee relying applications automatically trust the replacement key.

Explanation

Correct Answer

A:

“Action: Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements” addresses the access-design responsibilities in an employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data Test against review relying-party requirements, scopes, claims, token audiences and redirect flow; OIDC authentication and OAuth resource authorization solve related but different requirements.

Incorrect Answers

B:

“Action: Evaluate delegated authentication versus federated SSO in the context of current support, trust and credential-handling requirements. Verification: Test first login, required attributes, inactive status, license assignment and onboarding delay. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements” may apply to a related identity task, but it does not establish review relying-party requirements, scopes, claims, token audiences and redirect flow for an employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.

C:

“Action: Distinguish identity-provider-initiated and service-provider-initiated SAML login entry points and their state-handling requirements. Verification: Review relying-party requirements, scopes, claims, token audiences and redirect flow. Boundary: Cryptographic signature validity alone cannot make an assertion with the wrong audience acceptable” may apply to a related identity task, but it does not establish review relying-party requirements, scopes, claims, token audiences and redirect flow for an employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.

D:

“Action: Select OIDC for identity assertions and OAuth authorization flows for scoped API access when supported by the participants. Verification: Follow the login redirects, assertion issuer and target audience. 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 review relying-party requirements, scopes, claims, token audiences and redirect flow for an employee dashboard needs login federation and a back-office service needs limited permission to query Salesforce data The controlling boundary is: OIDC authentication and OAuth resource authorization solve related but different requirements.

Question 25

A legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect. Best next IAM response?

  1. Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints
  2. Match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application
  3. Establish an authoritative joiner-mover-leaver flow and independent deprovisioning controls beyond sign-in
  4. Prefer scheduled or event-driven lifecycle provisioning when entitlements must exist or be revoked before login

Explanation

Correct Answer

B:

“Match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application” addresses the access-design responsibilities in a legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect Test against validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; a protocol supported by the identity provider is insufficient if the relying application cannot validate it.

Incorrect Answers

A:

“Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints” may apply to a related identity task, but it does not establish validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app for a legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect The controlling boundary is: A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

C:

“Establish an authoritative joiner-mover-leaver flow and independent deprovisioning controls beyond sign-in” may apply to a related identity task, but it does not establish validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app for a legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect The controlling boundary is: A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

D:

“Prefer scheduled or event-driven lifecycle provisioning when entitlements must exist or be revoked before login” may apply to a related identity task, but it does not establish validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app for a legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect The controlling boundary is: A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

Question 26

A legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect. Most decisive verification?

  1. Document where passwords are validated, failure modes and supported new federation choices
  2. Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app
  3. Verify provisioning feed events, assignment mapping, timing and reconciliation of failures
  4. Map credential issuer, application permission owner and traceable audit events for each relying system

Explanation

Correct Answer

B:

“Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app” distinguishes sign-in from entitlement administration in a legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect It checks whether match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application.

Incorrect Answers

A:

“Document where passwords are validated, failure modes and supported new federation choices” needs to be evaluated against A legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect. The relevant check is Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

C:

“Verify provisioning feed events, assignment mapping, timing and reconciliation of failures” needs to be evaluated against A legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect. The relevant check is Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

D:

“Map credential issuer, application permission owner and traceable audit events for each relying system” needs to be evaluated against A legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect. The relevant check is Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

Question 27

A legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect. Key caution for this case?

  1. A protocol supported by the identity provider is insufficient if the relying application cannot validate it
  2. Possession of an API access token alone does not establish the claimed identity for every application
  3. OIDC authentication and OAuth resource authorization solve related but different requirements
  4. Cryptographic signature validity alone cannot make an assertion with the wrong audience acceptable

Explanation

Correct Answer

A:

“A protocol supported by the identity provider is insufficient if the relying application cannot validate it” needs to be evaluated against A legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect. The relevant check is Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

Incorrect Answers

B:

“Possession of an API access token alone does not establish the claimed identity for every application” needs to be evaluated against A legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect. The relevant check is Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

C:

“OIDC authentication and OAuth resource authorization solve related but different requirements” needs to be evaluated against A legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect. The relevant check is Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

D:

“Cryptographic signature validity alone cannot make an assertion with the wrong audience acceptable” needs to be evaluated against A legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect. The relevant check is Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

Question 28

A legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect. Best complete IAM decision record?

  1. Action: Match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application. Verification: Map credential issuer, application permission owner and traceable audit events for each relying system. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements.
  2. Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app. Boundary: Possession of an API access token alone does not establish the claimed identity for every application.
  3. Action: Prefer scheduled or event-driven lifecycle provisioning when entitlements must exist or be revoked before login. Verification: Verify provisioning feed events, assignment mapping, timing and reconciliation of failures. Boundary: A protocol supported by the identity provider is insufficient if the relying application cannot validate it.
  4. Action: Match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application. Verification: Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app. Boundary: A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

Explanation

Correct Answer

D:

“Action: Match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application. Verification: Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app. Boundary: A protocol supported by the identity provider is insufficient if the relying application cannot validate it” addresses the access-design responsibilities in a legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect Test against validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; a protocol supported by the identity provider is insufficient if the relying application cannot validate it.

Incorrect Answers

A:

“Action: Match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application. Verification: Map credential issuer, application permission owner and traceable audit events for each relying system. Boundary: OIDC authentication and OAuth resource authorization solve related but different requirements” may apply to a related identity task, but it does not establish validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app for a legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect The controlling boundary is: A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

B:

“Action: Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints. Verification: Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app. Boundary: Possession of an API access token alone does not establish the claimed identity for every application” may apply to a related identity task, but it does not establish validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app for a legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect The controlling boundary is: A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

C:

“Action: Prefer scheduled or event-driven lifecycle provisioning when entitlements must exist or be revoked before login. Verification: Verify provisioning feed events, assignment mapping, timing and reconciliation of failures. Boundary: A protocol supported by the identity provider is insufficient if the relying application cannot validate it” may apply to a related identity task, but it does not establish validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app for a legacy app only accepts SAML assertions while a new mobile app supports OpenID Connect The controlling boundary is: A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

Question 29

A merger brings an XML-based enterprise identity platform alongside an OIDC-based supplier portal. Best next IAM response?

  1. Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints
  2. Match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application
  3. Prefer scheduled or event-driven lifecycle provisioning when entitlements must exist or be revoked before login
  4. Establish an authoritative joiner-mover-leaver flow and independent deprovisioning controls beyond sign-in

Explanation

Correct Answer

B:

“Match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application” addresses the access-design responsibilities in a merger brings an XML-based enterprise identity platform alongside an OIDC-based supplier portal Test against validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; a protocol supported by the identity provider is insufficient if the relying application cannot validate it.

Incorrect Answers

A:

“Plan domain and redirect URI migration across identity providers and supported Salesforce endpoints” may apply to a related identity task, but it does not establish validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app for a merger brings an XML-based enterprise identity platform alongside an OIDC-based supplier portal The controlling boundary is: A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

C:

“Prefer scheduled or event-driven lifecycle provisioning when entitlements must exist or be revoked before login” may apply to a related identity task, but it does not establish validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app for a merger brings an XML-based enterprise identity platform alongside an OIDC-based supplier portal The controlling boundary is: A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

D:

“Establish an authoritative joiner-mover-leaver flow and independent deprovisioning controls beyond sign-in” may apply to a related identity task, but it does not establish validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app for a merger brings an XML-based enterprise identity platform alongside an OIDC-based supplier portal The controlling boundary is: A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

Question 30

A merger brings an XML-based enterprise identity platform alongside an OIDC-based supplier portal. Most decisive verification?

  1. Map credential issuer, application permission owner and traceable audit events for each relying system
  2. Verify provisioning feed events, assignment mapping, timing and reconciliation of failures
  3. Document where passwords are validated, failure modes and supported new federation choices
  4. Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app

Explanation

Correct Answer

D:

“Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app” distinguishes sign-in from entitlement administration in a merger brings an XML-based enterprise identity platform alongside an OIDC-based supplier portal It checks whether match the federation protocol to service-provider compatibility and security requirements instead of choosing one for every application.

Incorrect Answers

A:

“Map credential issuer, application permission owner and traceable audit events for each relying system” needs to be evaluated against A merger brings an XML-based enterprise identity platform alongside an OIDC-based supplier portal. The relevant check is Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

B:

“Verify provisioning feed events, assignment mapping, timing and reconciliation of failures” needs to be evaluated against A merger brings an XML-based enterprise identity platform alongside an OIDC-based supplier portal. The relevant check is Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

C:

“Document where passwords are validated, failure modes and supported new federation choices” needs to be evaluated against A merger brings an XML-based enterprise identity platform alongside an OIDC-based supplier portal. The relevant check is Validate supported SAML bindings, OIDC endpoints, signing trust and session lifecycle for each app; A protocol supported by the identity provider is insufficient if the relying application cannot validate it.

Certified Platform Identity and Access Management Architect Practice Tests