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 38

Question 370

A third-party app requests authorization from a user who does not understand the data access being granted. Most decisive verification?

  1. Review approved client identity, app scopes, grant history and denied-consent behavior
  2. Test code verifier/challenge, redirect registration, user grant and token exchange
  3. Test allowed resources, user permission sets, sensitive fields and scope restrictions
  4. Verify issuer discovery, token validation, audience, nonce and redirect URI handling

Explanation

Correct Answer

A:

“Review approved client identity, app scopes, grant history and denied-consent behavior” distinguishes sign-in from entitlement administration in a third-party app requests authorization from a user who does not understand the data access being granted It checks whether apply app access policies, understandable consent and administrative approval for sensitive integrations.

Incorrect Answers

B:

“Test code verifier/challenge, redirect registration, user grant and token exchange” needs to be evaluated against A third-party app requests authorization from a user who does not understand the data access being granted. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

C:

“Test allowed resources, user permission sets, sensitive fields and scope restrictions” needs to be evaluated against A third-party app requests authorization from a user who does not understand the data access being granted. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

D:

“Verify issuer discovery, token validation, audience, nonce and redirect URI handling” needs to be evaluated against A third-party app requests authorization from a user who does not understand the data access being granted. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Question 371

A third-party app requests authorization from a user who does not understand the data access being granted. Key caution for this case?

  1. New connected app creation is restricted as of Spring 2026; an old exam-guide click path may no longer apply
  2. An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration
  3. An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party
  4. IdP-initiated and SP-initiated SAML have different request context and cannot be assumed equivalent

Explanation

Correct Answer

B:

“An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration” needs to be evaluated against A third-party app requests authorization from a user who does not understand the data access being granted. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Incorrect Answers

A:

“New connected app creation is restricted as of Spring 2026; an old exam-guide click path may no longer apply” needs to be evaluated against A third-party app requests authorization from a user who does not understand the data access being granted. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

C:

“An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party” needs to be evaluated against A third-party app requests authorization from a user who does not understand the data access being granted. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

D:

“IdP-initiated and SP-initiated SAML have different request context and cannot be assumed equivalent” needs to be evaluated against A third-party app requests authorization from a user who does not understand the data access being granted. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Question 372

A third-party app requests authorization from a user who does not understand the data access being granted. Best complete IAM decision record?

  1. Action: Evaluate Salesforce as an OIDC provider for a compatible relying party with approved claims and client registration. Verification: Review approved client identity, app scopes, grant history and denied-consent behavior. Boundary: An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party.
  2. Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Review approved client identity, app scopes, grant history and denied-consent behavior. Boundary: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.
  3. Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Test allowed resources, user permission sets, sensitive fields and scope restrictions. Boundary: IdP-initiated and SP-initiated SAML have different request context and cannot be assumed equivalent.
  4. Action: Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed. Verification: Verify issuer discovery, token validation, audience, nonce and redirect URI handling. Boundary: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Explanation

Correct Answer

B:

“Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Review approved client identity, app scopes, grant history and denied-consent behavior. Boundary: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration” addresses the access-design responsibilities in a third-party app requests authorization from a user who does not understand the data access being granted Test against review approved client identity, app scopes, grant history and denied-consent behavior; an OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Incorrect Answers

A:

“Action: Evaluate Salesforce as an OIDC provider for a compatible relying party with approved claims and client registration. Verification: Review approved client identity, app scopes, grant history and denied-consent behavior. Boundary: An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party” may apply to a related identity task, but it does not establish review approved client identity, app scopes, grant history and denied-consent behavior for a third-party app requests authorization from a user who does not understand the data access being granted The controlling boundary is: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

C:

“Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Test allowed resources, user permission sets, sensitive fields and scope restrictions. Boundary: IdP-initiated and SP-initiated SAML have different request context and cannot be assumed equivalent” may apply to a related identity task, but it does not establish review approved client identity, app scopes, grant history and denied-consent behavior for a third-party app requests authorization from a user who does not understand the data access being granted The controlling boundary is: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

D:

“Action: Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed. Verification: Verify issuer discovery, token validation, audience, nonce and redirect URI handling. Boundary: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration” may apply to a related identity task, but it does not establish review approved client identity, app scopes, grant history and denied-consent behavior for a third-party app requests authorization from a user who does not understand the data access being granted The controlling boundary is: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Question 373

A sales manager is asked to approve an unfamiliar application with administrative OAuth scopes. Best next IAM response?

  1. Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed
  2. Evaluate Salesforce as an OIDC provider for a compatible relying party with approved claims and client registration
  3. Consider a supported device authorization flow only for an appropriate constrained client with secure user verification
  4. Apply app access policies, understandable consent and administrative approval for sensitive integrations

Explanation

Correct Answer

D:

“Apply app access policies, understandable consent and administrative approval for sensitive integrations” addresses the access-design responsibilities in a sales manager is asked to approve an unfamiliar application with administrative OAuth scopes Test against review approved client identity, app scopes, grant history and denied-consent behavior; an OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Incorrect Answers

A:

“Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed” may apply to a related identity task, but it does not establish review approved client identity, app scopes, grant history and denied-consent behavior for a sales manager is asked to approve an unfamiliar application with administrative OAuth scopes The controlling boundary is: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

B:

“Evaluate Salesforce as an OIDC provider for a compatible relying party with approved claims and client registration” may apply to a related identity task, but it does not establish review approved client identity, app scopes, grant history and denied-consent behavior for a sales manager is asked to approve an unfamiliar application with administrative OAuth scopes The controlling boundary is: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

C:

“Consider a supported device authorization flow only for an appropriate constrained client with secure user verification” may apply to a related identity task, but it does not establish review approved client identity, app scopes, grant history and denied-consent behavior for a sales manager is asked to approve an unfamiliar application with administrative OAuth scopes The controlling boundary is: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Question 374

A sales manager is asked to approve an unfamiliar application with administrative OAuth scopes. Most decisive verification?

  1. Review approved client identity, app scopes, grant history and denied-consent behavior
  2. Verify issuer discovery, token validation, audience, nonce and redirect URI handling
  3. Test code verifier/challenge, redirect registration, user grant and token exchange
  4. Test allowed resources, user permission sets, sensitive fields and scope restrictions

Explanation

Correct Answer

A:

“Review approved client identity, app scopes, grant history and denied-consent behavior” distinguishes sign-in from entitlement administration in a sales manager is asked to approve an unfamiliar application with administrative OAuth scopes It checks whether apply app access policies, understandable consent and administrative approval for sensitive integrations.

Incorrect Answers

B:

“Verify issuer discovery, token validation, audience, nonce and redirect URI handling” needs to be evaluated against A sales manager is asked to approve an unfamiliar application with administrative OAuth scopes. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

C:

“Test code verifier/challenge, redirect registration, user grant and token exchange” needs to be evaluated against A sales manager is asked to approve an unfamiliar application with administrative OAuth scopes. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

D:

“Test allowed resources, user permission sets, sensitive fields and scope restrictions” needs to be evaluated against A sales manager is asked to approve an unfamiliar application with administrative OAuth scopes. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Question 375

A sales manager is asked to approve an unfamiliar application with administrative OAuth scopes. Key caution for this case?

  1. IdP-initiated and SP-initiated SAML have different request context and cannot be assumed equivalent
  2. New connected app creation is restricted as of Spring 2026; an old exam-guide click path may no longer apply
  3. An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration
  4. An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party

Explanation

Correct Answer

C:

“An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration” needs to be evaluated against A sales manager is asked to approve an unfamiliar application with administrative OAuth scopes. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Incorrect Answers

A:

“IdP-initiated and SP-initiated SAML have different request context and cannot be assumed equivalent” needs to be evaluated against A sales manager is asked to approve an unfamiliar application with administrative OAuth scopes. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

B:

“New connected app creation is restricted as of Spring 2026; an old exam-guide click path may no longer apply” needs to be evaluated against A sales manager is asked to approve an unfamiliar application with administrative OAuth scopes. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

D:

“An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party” needs to be evaluated against A sales manager is asked to approve an unfamiliar application with administrative OAuth scopes. The relevant check is Review approved client identity, app scopes, grant history and denied-consent behavior; An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Question 376

A sales manager is asked to approve an unfamiliar application with administrative OAuth scopes. Best complete IAM decision record?

  1. Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Review approved client identity, app scopes, grant history and denied-consent behavior. Boundary: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.
  2. Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Test allowed resources, user permission sets, sensitive fields and scope restrictions. Boundary: IdP-initiated and SP-initiated SAML have different request context and cannot be assumed equivalent.
  3. Action: Evaluate Salesforce as an OIDC provider for a compatible relying party with approved claims and client registration. Verification: Review approved client identity, app scopes, grant history and denied-consent behavior. Boundary: An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party.
  4. Action: Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed. Verification: Verify issuer discovery, token validation, audience, nonce and redirect URI handling. Boundary: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Explanation

Correct Answer

A:

“Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Review approved client identity, app scopes, grant history and denied-consent behavior. Boundary: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration” addresses the access-design responsibilities in a sales manager is asked to approve an unfamiliar application with administrative OAuth scopes Test against review approved client identity, app scopes, grant history and denied-consent behavior; an OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Incorrect Answers

B:

“Action: Apply app access policies, understandable consent and administrative approval for sensitive integrations. Verification: Test allowed resources, user permission sets, sensitive fields and scope restrictions. Boundary: IdP-initiated and SP-initiated SAML have different request context and cannot be assumed equivalent” may apply to a related identity task, but it does not establish review approved client identity, app scopes, grant history and denied-consent behavior for a sales manager is asked to approve an unfamiliar application with administrative OAuth scopes The controlling boundary is: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

C:

“Action: Evaluate Salesforce as an OIDC provider for a compatible relying party with approved claims and client registration. Verification: Review approved client identity, app scopes, grant history and denied-consent behavior. Boundary: An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party” may apply to a related identity task, but it does not establish review approved client identity, app scopes, grant history and denied-consent behavior for a sales manager is asked to approve an unfamiliar application with administrative OAuth scopes The controlling boundary is: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

D:

“Action: Plan new OAuth integrations with the external client app framework and confirm exception procedures only when genuinely needed. Verification: Verify issuer discovery, token validation, audience, nonce and redirect URI handling. Boundary: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration” may apply to a related identity task, but it does not establish review approved client identity, app scopes, grant history and denied-consent behavior for a sales manager is asked to approve an unfamiliar application with administrative OAuth scopes The controlling boundary is: An OAuth consent screen is not a substitute for enterprise security review or least-privilege configuration.

Question 377

A relying party uses an OAuth access token as evidence of a user's birthdate and email identity. Best next IAM response?

  1. Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate
  2. Consider a supported device authorization flow only for an appropriate constrained client with secure user verification
  3. Separate identity claims validation from API token handling and enforce correct issuer, audience and nonce checks
  4. Fix authorization-code redirect registration, state integrity and callback matching before widening trusted origins

Explanation

Correct Answer

C:

“Separate identity claims validation from API token handling and enforce correct issuer, audience and nonce checks” addresses the access-design responsibilities in a relying party uses an OAuth access token as evidence of a user's birthdate and email identity Test against validate token type, signature trust, issuer, subject, audience and replay context; a correctly signed token intended for another client must not authenticate the local relying party.

Incorrect Answers

A:

“Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate” may apply to a related identity task, but it does not establish validate token type, signature trust, issuer, subject, audience and replay context for a relying party uses an OAuth access token as evidence of a user's birthdate and email identity The controlling boundary is: A correctly signed token intended for another client must not authenticate the local relying party.

B:

“Consider a supported device authorization flow only for an appropriate constrained client with secure user verification” may apply to a related identity task, but it does not establish validate token type, signature trust, issuer, subject, audience and replay context for a relying party uses an OAuth access token as evidence of a user's birthdate and email identity The controlling boundary is: A correctly signed token intended for another client must not authenticate the local relying party.

D:

“Fix authorization-code redirect registration, state integrity and callback matching before widening trusted origins” may apply to a related identity task, but it does not establish validate token type, signature trust, issuer, subject, audience and replay context for a relying party uses an OAuth access token as evidence of a user's birthdate and email identity The controlling boundary is: A correctly signed token intended for another client must not authenticate the local relying party.

Question 378

A relying party uses an OAuth access token as evidence of a user's birthdate and email identity. Most decisive verification?

  1. Test code verifier/challenge, redirect registration, user grant and token exchange
  2. Validate token type, signature trust, issuer, subject, audience and replay context
  3. Check signing key fingerprint, metadata published to partners, trust-update status and login smoke tests
  4. Verify issuer discovery, token validation, audience, nonce and redirect URI handling

Explanation

Correct Answer

B:

“Validate token type, signature trust, issuer, subject, audience and replay context” distinguishes sign-in from entitlement administration in a relying party uses an OAuth access token as evidence of a user's birthdate and email identity It checks whether separate identity claims validation from API token handling and enforce correct issuer, audience and nonce checks.

Incorrect Answers

A:

“Test code verifier/challenge, redirect registration, user grant and token exchange” needs to be evaluated against A relying party uses an OAuth access token as evidence of a user's birthdate and email identity. The relevant check is Validate token type, signature trust, issuer, subject, audience and replay context; A correctly signed token intended for another client must not authenticate the local relying party.

C:

“Check signing key fingerprint, metadata published to partners, trust-update status and login smoke tests” needs to be evaluated against A relying party uses an OAuth access token as evidence of a user's birthdate and email identity. The relevant check is Validate token type, signature trust, issuer, subject, audience and replay context; A correctly signed token intended for another client must not authenticate the local relying party.

D:

“Verify issuer discovery, token validation, audience, nonce and redirect URI handling” needs to be evaluated against A relying party uses an OAuth access token as evidence of a user's birthdate and email identity. The relevant check is Validate token type, signature trust, issuer, subject, audience and replay context; A correctly signed token intended for another client must not authenticate the local relying party.

Question 379

A relying party uses an OAuth access token as evidence of a user's birthdate and email identity. Key caution for this case?

  1. Restricting new connected app creation does not mean every existing connected app immediately stops working
  2. An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party
  3. A correctly signed token intended for another client must not authenticate the local relying party
  4. Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in

Explanation

Correct Answer

C:

“A correctly signed token intended for another client must not authenticate the local relying party” needs to be evaluated against A relying party uses an OAuth access token as evidence of a user's birthdate and email identity. The relevant check is Validate token type, signature trust, issuer, subject, audience and replay context; A correctly signed token intended for another client must not authenticate the local relying party.

Incorrect Answers

A:

“Restricting new connected app creation does not mean every existing connected app immediately stops working” needs to be evaluated against A relying party uses an OAuth access token as evidence of a user's birthdate and email identity. The relevant check is Validate token type, signature trust, issuer, subject, audience and replay context; A correctly signed token intended for another client must not authenticate the local relying party.

B:

“An OAuth API access token is not a substitute for validating an OIDC identity token at the relying party” needs to be evaluated against A relying party uses an OAuth access token as evidence of a user's birthdate and email identity. The relevant check is Validate token type, signature trust, issuer, subject, audience and replay context; A correctly signed token intended for another client must not authenticate the local relying party.

D:

“Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in” needs to be evaluated against A relying party uses an OAuth access token as evidence of a user's birthdate and email identity. The relevant check is Validate token type, signature trust, issuer, subject, audience and replay context; A correctly signed token intended for another client must not authenticate the local relying party.

Question 380

A relying party uses an OAuth access token as evidence of a user's birthdate and email identity. Best complete IAM decision record?

  1. Action: Separate identity claims validation from API token handling and enforce correct issuer, audience and nonce checks. Verification: Validate token type, signature trust, issuer, subject, audience and replay context. Boundary: A correctly signed token intended for another client must not authenticate the local relying party.
  2. Action: Fix authorization-code redirect registration, state integrity and callback matching before widening trusted origins. Verification: Test code verifier/challenge, redirect registration, user grant and token exchange. Boundary: A correctly signed token intended for another client must not authenticate the local relying party.
  3. Action: Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate. Verification: Validate token type, signature trust, issuer, subject, audience and replay context. Boundary: Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in.
  4. Action: Separate identity claims validation from API token handling and enforce correct issuer, audience and nonce checks. Verification: Verify issuer discovery, token validation, audience, nonce and redirect URI handling. Boundary: Restricting new connected app creation does not mean every existing connected app immediately stops working.

Explanation

Correct Answer

A:

“Action: Separate identity claims validation from API token handling and enforce correct issuer, audience and nonce checks. Verification: Validate token type, signature trust, issuer, subject, audience and replay context. Boundary: A correctly signed token intended for another client must not authenticate the local relying party” addresses the access-design responsibilities in a relying party uses an OAuth access token as evidence of a user's birthdate and email identity Test against validate token type, signature trust, issuer, subject, audience and replay context; a correctly signed token intended for another client must not authenticate the local relying party.

Incorrect Answers

B:

“Action: Fix authorization-code redirect registration, state integrity and callback matching before widening trusted origins. Verification: Test code verifier/challenge, redirect registration, user grant and token exchange. Boundary: A correctly signed token intended for another client must not authenticate the local relying party” may apply to a related identity task, but it does not establish validate token type, signature trust, issuer, subject, audience and replay context for a relying party uses an OAuth access token as evidence of a user's birthdate and email identity The controlling boundary is: A correctly signed token intended for another client must not authenticate the local relying party.

C:

“Action: Consider supported OAuth client credentials under a dedicated run-as user and explicit access policy where appropriate. Verification: Validate token type, signature trust, issuer, subject, audience and replay context. Boundary: Rotating a signing certificate without coordinating trust at the SP can interrupt every affected sign-in” may apply to a related identity task, but it does not establish validate token type, signature trust, issuer, subject, audience and replay context for a relying party uses an OAuth access token as evidence of a user's birthdate and email identity The controlling boundary is: A correctly signed token intended for another client must not authenticate the local relying party.

D:

“Action: Separate identity claims validation from API token handling and enforce correct issuer, audience and nonce checks. Verification: Verify issuer discovery, token validation, audience, nonce and redirect URI handling. Boundary: Restricting new connected app creation does not mean every existing connected app immediately stops working” may apply to a related identity task, but it does not establish validate token type, signature trust, issuer, subject, audience and replay context for a relying party uses an OAuth access token as evidence of a user's birthdate and email identity The controlling boundary is: A correctly signed token intended for another client must not authenticate the local relying party.

Certified Platform Identity and Access Management Architect Practice Tests