McAfee-Secured Website

Exam Code: Certified Platform Identity and Access Management Architect

Exam Name: Certified Platform Identity and Access Management Architect

Certification Provider: Salesforce

100% Salesforce Certified Platform Identity and Access Management Architect Guaranteed Success With Testking Training Materials

Get Real Certified Platform Identity and Access Management Architect Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

58 Questions & Answers with Testing Engine

"Certified Platform Identity and Access Management Architect Exam", also known as Certified Platform Identity and Access Management Architect exam, is a Salesforce certification exam.

Pass your tests with the always up-to-date Certified Platform Identity and Access Management Architect Exam Engine. Your Certified Platform Identity and Access Management Architect training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Salesforce Certified Platform Identity and Access Management Architect Practice Test 40

Question 0390 — Salesforce as an Identity Provider

At fictional Laurelfield Transit 39B, the team managing OAuth token lifecycle reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Reapprove connected-app scope sets during each API integration feature expansion.
  2. Periodically test redirect URI matching and review changes to connected-app callback lists.
  3. Validate selected flow type against client capabilities and security requirements before deploying integrations.
  4. Reconcile registered apps, scopes and named owners to the enterprise application inventory.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Periodically test redirect URI matching and review changes to connected-app callback lists. This recurring control addresses the observed problem: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. The measurable check is: Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

Incorrect Answers

A:

Reapprove connected-app scope sets during each API integration feature expansion. Periodically test redirect URI matching and review changes to connected-app callback lists.

C:

Validate selected flow type against client capabilities and security requirements before deploying integrations. Periodically test redirect URI matching and review changes to connected-app callback lists.

D:

Reconcile registered apps, scopes and named owners to the enterprise application inventory. Periodically test redirect URI matching and review changes to connected-app callback lists.

Question 0391 — Salesforce as an Identity Provider

At fictional Moss River Health 40A, the team managing OAuth token lifecycle reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.
  2. Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.
  3. Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.
  4. Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose. Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

Incorrect Answers

A:

Use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret. The needed correction is to issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.

B:

Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements. The needed correction is to issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.

D:

Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment. The needed correction is to issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.

Question 0392 — Salesforce as an Identity Provider

At fictional Moss River Health 40A, the team managing OAuth token lifecycle reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.
  2. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.
  3. Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.
  4. Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds. The corresponding correction is to issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.

Incorrect Answers

A:

Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope. The useful check here is whether show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

B:

Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access. The useful check here is whether show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

C:

Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery. The useful check here is whether show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

Question 0393 — Salesforce as an Identity Provider

At fictional Moss River Health 40A, the team managing OAuth token lifecycle reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Identity assertions and resource access grants are separate token classes with different audiences and claims.
  2. Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side.
  3. OAuth grants and application sessions require explicit revocation semantics separate from browser login state.
  4. Independent relying applications should have isolatable least-privilege grants and governance.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Identity assertions and resource access grants are separate token classes with different audiences and claims. Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

Incorrect Answers

B:

Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side. Identity assertions and resource access grants are separate token classes with different audiences and claims.

C:

OAuth grants and application sessions require explicit revocation semantics separate from browser login state. Identity assertions and resource access grants are separate token classes with different audiences and claims.

D:

Independent relying applications should have isolatable least-privilege grants and governance. Identity assertions and resource access grants are separate token classes with different audiences and claims.

Question 0394 — Salesforce as an Identity Provider

At fictional Moss River Health 40A, the team managing OAuth token lifecycle reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Excessive scopes increase the damage possible when an application token is compromised.
  2. Treating any signed identity token as API authorization opens confused-deputy token acceptance paths.
  3. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.
  4. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Treating any signed identity token as API authorization opens confused-deputy token acceptance paths. Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.

Incorrect Answers

A:

Excessive scopes increase the damage possible when an application token is compromised. Treating any signed identity token as API authorization opens confused-deputy token acceptance paths.

C:

Overlooking long-lived refresh grants extends access beyond intended offboarding controls. Treating any signed identity token as API authorization opens confused-deputy token acceptance paths.

D:

Stale issuer acceptance can create federation outages or preserve obsolete trust paths. Treating any signed identity token as API authorization opens confused-deputy token acceptance paths.

Question 0395 — Salesforce as an Identity Provider

At fictional Moss River Health 40A, the team managing OAuth token lifecycle reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Audit high-risk refresh grants and ensure leaver runbooks cover each connected app.
  2. Reconcile registered apps, scopes and named owners to the enterprise application inventory.
  3. Test token type/audience separation at resource servers and connected-app boundaries.
  4. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Test token type/audience separation at resource servers and connected-app boundaries. This recurring control addresses the observed problem: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. The measurable check is: Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

Incorrect Answers

A:

Audit high-risk refresh grants and ensure leaver runbooks cover each connected app. Test token type/audience separation at resource servers and connected-app boundaries.

B:

Reconcile registered apps, scopes and named owners to the enterprise application inventory. Test token type/audience separation at resource servers and connected-app boundaries.

D:

Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change. Test token type/audience separation at resource servers and connected-app boundaries.

Question 0396 — Salesforce as an Identity Provider

At fictional Seabrook Systems 40B, the team managing connected-app authorization reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.
  2. Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.
  3. Separate application registration and authorization policies by trust boundary, accountable owner and required data scope.
  4. Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose. Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

Incorrect Answers

A:

Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage. The needed correction is to issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.

B:

Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure. The needed correction is to issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.

C:

Separate application registration and authorization policies by trust boundary, accountable owner and required data scope. The needed correction is to issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.

Question 0397 — Salesforce as an Identity Provider

At fictional Seabrook Systems 40B, the team managing connected-app authorization reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.
  2. Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.
  3. Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.
  4. Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds. The corresponding correction is to issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.

Incorrect Answers

B:

Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations. The useful check here is whether show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

C:

Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens. The useful check here is whether show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

D:

Validate an updated signed assertion from the active Salesforce issuer and show the partner rejects deprecated issuer metadata. The useful check here is whether show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

Question 0398 — Salesforce as an Identity Provider

At fictional Seabrook Systems 40B, the team managing connected-app authorization reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. Which security architecture principle most directly explains the remediation needed for these facts?

  1. OAuth grants and application sessions require explicit revocation semantics separate from browser login state.
  2. Identity assertions and resource access grants are separate token classes with different audiences and claims.
  3. Independent relying applications should have isolatable least-privilege grants and governance.
  4. Device-limited clients can delegate interactive approval to a separate secure authorization channel.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Identity assertions and resource access grants are separate token classes with different audiences and claims. Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

Incorrect Answers

A:

OAuth grants and application sessions require explicit revocation semantics separate from browser login state. Identity assertions and resource access grants are separate token classes with different audiences and claims.

C:

Independent relying applications should have isolatable least-privilege grants and governance. Identity assertions and resource access grants are separate token classes with different audiences and claims.

D:

Device-limited clients can delegate interactive approval to a separate secure authorization channel. Identity assertions and resource access grants are separate token classes with different audiences and claims.

Question 0399 — Salesforce as an Identity Provider

At fictional Seabrook Systems 40B, the team managing connected-app authorization reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. One compromised broad connected-app grant can expose multiple unrelated services and datasets.
  2. Capturing credentials on untrusted shared devices enables theft and residual sessions.
  3. Treating any signed identity token as API authorization opens confused-deputy token acceptance paths.
  4. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Treating any signed identity token as API authorization opens confused-deputy token acceptance paths. Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.

Incorrect Answers

A:

One compromised broad connected-app grant can expose multiple unrelated services and datasets. Treating any signed identity token as API authorization opens confused-deputy token acceptance paths.

B:

Capturing credentials on untrusted shared devices enables theft and residual sessions. Treating any signed identity token as API authorization opens confused-deputy token acceptance paths.

D:

Stale issuer acceptance can create federation outages or preserve obsolete trust paths. Treating any signed identity token as API authorization opens confused-deputy token acceptance paths.

Question 0400 — Salesforce as an Identity Provider

At fictional Seabrook Systems 40B, the team managing connected-app authorization reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis.
  2. Scan build artifacts and redirect configurations for client credentials and token leakage.
  3. Validate selected flow type against client capabilities and security requirements before deploying integrations.
  4. Test token type/audience separation at resource servers and connected-app boundaries.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Test token type/audience separation at resource servers and connected-app boundaries. This recurring control addresses the observed problem: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. The measurable check is: Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

Incorrect Answers

A:

Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Test token type/audience separation at resource servers and connected-app boundaries.

B:

Scan build artifacts and redirect configurations for client credentials and token leakage. Test token type/audience separation at resource servers and connected-app boundaries.

C:

Validate selected flow type against client capabilities and security requirements before deploying integrations. Test token type/audience separation at resource servers and connected-app boundaries.

Certified Platform Identity and Access Management Architect Practice Tests