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 37

Question 0360 — Salesforce as an Identity Provider

At fictional Meadow Point Software 36B, the team managing relying application federation reports: A connected application asks for broad Salesforce API scopes even though it only needs read-only identity attributes for an external dashboard. 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. Rehearse My Domain issuer and metadata rollovers with every external service provider.
  4. Reapprove connected-app scope sets during each API integration feature expansion.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Reapprove connected-app scope sets during each API integration feature expansion. This recurring control addresses the observed problem: A connected application asks for broad Salesforce API scopes even though it only needs read-only identity attributes for an external dashboard. The measurable check is: Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.

Incorrect Answers

A:

Audit high-risk refresh grants and ensure leaver runbooks cover each connected app. Reapprove connected-app scope sets during each API integration feature expansion.

B:

Reconcile registered apps, scopes and named owners to the enterprise application inventory. Reapprove connected-app scope sets during each API integration feature expansion.

C:

Rehearse My Domain issuer and metadata rollovers with every external service provider. Reapprove connected-app scope sets during each API integration feature expansion.

Question 0361 — Salesforce as an Identity Provider

At fictional Aspen Trail Retail 37A, the team managing relying application federation reports: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.
  2. Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.
  3. Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.
  4. Reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure. Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

Incorrect Answers

B:

Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization. The needed correction is to explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.

C:

Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage. The needed correction is to explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.

D:

Reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints. The needed correction is to explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.

Question 0362 — Salesforce as an Identity Provider

At fictional Aspen Trail Retail 37A, the team managing relying application federation reports: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. 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. Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.
  3. Review individual connected-app grants to show each has unique ownership, scope and revocation controls.
  4. Trace a test callout using the approved credential principal with no reusable password in application code or logs.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens. The corresponding correction is to explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.

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 verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

C:

Review individual connected-app grants to show each has unique ownership, scope and revocation controls. The useful check here is whether verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

D:

Trace a test callout using the approved credential principal with no reusable password in application code or logs. The useful check here is whether verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

Question 0363 — Salesforce as an Identity Provider

At fictional Aspen Trail Retail 37A, the team managing relying application federation reports: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side.
  2. Identity assertions and resource access grants are separate token classes with different audiences and claims.
  3. OAuth grants and application sessions require explicit revocation semantics separate from browser login state.
  4. Device-limited clients can delegate interactive approval to a separate secure authorization channel.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

OAuth grants and application sessions require explicit revocation semantics separate from browser login state. Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

Incorrect Answers

A:

Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side. OAuth grants and application sessions require explicit revocation semantics separate from browser login state.

B:

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

D:

Device-limited clients can delegate interactive approval to a separate secure authorization channel. OAuth grants and application sessions require explicit revocation semantics separate from browser login state.

Question 0364 — Salesforce as an Identity Provider

At fictional Aspen Trail Retail 37A, the team managing relying application federation reports: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. 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. One compromised broad connected-app grant can expose multiple unrelated services and datasets.
  3. Capturing credentials on untrusted shared devices enables theft and residual sessions.
  4. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Overlooking long-lived refresh grants extends access beyond intended offboarding controls. Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.

Incorrect Answers

A:

Excessive scopes increase the damage possible when an application token is compromised. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.

B:

One compromised broad connected-app grant can expose multiple unrelated services and datasets. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.

C:

Capturing credentials on untrusted shared devices enables theft and residual sessions. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.

Question 0365 — Salesforce as an Identity Provider

At fictional Aspen Trail Retail 37A, the team managing relying application federation reports: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. 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. Periodically test redirect URI matching and review changes to connected-app callback lists.
  3. Test token type/audience separation at resource servers and connected-app boundaries.
  4. Rehearse My Domain issuer and metadata rollovers with every external service provider.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Audit high-risk refresh grants and ensure leaver runbooks cover each connected app. This recurring control addresses the observed problem: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. The measurable check is: Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

Incorrect Answers

B:

Periodically test redirect URI matching and review changes to connected-app callback lists. Audit high-risk refresh grants and ensure leaver runbooks cover each connected app.

C:

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

D:

Rehearse My Domain issuer and metadata rollovers with every external service provider. Audit high-risk refresh grants and ensure leaver runbooks cover each connected app.

Question 0366 — Salesforce as an Identity Provider

At fictional Westhaven Insurance 37B, the team managing API integration authentication reports: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. 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. Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.
  4. Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure. Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

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 explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.

C:

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

D:

Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements. The needed correction is to explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.

Question 0367 — Salesforce as an Identity Provider

At fictional Westhaven Insurance 37B, the team managing API integration authentication reports: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.
  2. Review individual connected-app grants to show each has unique ownership, scope and revocation controls.
  3. Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.
  4. Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens. The corresponding correction is to explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.

Incorrect Answers

A:

Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations. The useful check here is whether verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

B:

Review individual connected-app grants to show each has unique ownership, scope and revocation controls. The useful check here is whether verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

D:

Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request. The useful check here is whether verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

Question 0368 — Salesforce as an Identity Provider

At fictional Westhaven Insurance 37B, the team managing API integration authentication reports: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.
  2. Identity assertions and resource access grants are separate token classes with different audiences and claims.
  3. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.
  4. OAuth grants and application sessions require explicit revocation semantics separate from browser login state.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

OAuth grants and application sessions require explicit revocation semantics separate from browser login state. Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

Incorrect Answers

A:

Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration. OAuth grants and application sessions require explicit revocation semantics separate from browser login state.

B:

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

C:

Identity-provider continuity requires controlled metadata changes and relying-party trust verification. OAuth grants and application sessions require explicit revocation semantics separate from browser login state.

Question 0369 — Salesforce as an Identity Provider

At fictional Westhaven Insurance 37B, the team managing API integration authentication reports: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.
  2. Password replication multiplies credential exposure and obscures authoritative identity governance.
  3. Extracted secrets and unbound codes create credential and authorization-code interception risks.
  4. Capturing credentials on untrusted shared devices enables theft and residual sessions.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Overlooking long-lived refresh grants extends access beyond intended offboarding controls. Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.

Incorrect Answers

B:

Password replication multiplies credential exposure and obscures authoritative identity governance. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.

C:

Extracted secrets and unbound codes create credential and authorization-code interception risks. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.

D:

Capturing credentials on untrusted shared devices enables theft and residual sessions. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.

Question 0370 — Salesforce as an Identity Provider

At fictional Westhaven Insurance 37B, the team managing API integration authentication reports: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. 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. Audit high-risk refresh grants and ensure leaver runbooks cover each connected app.
  3. Reapprove connected-app scope sets during each API integration feature expansion.
  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

B:

Audit high-risk refresh grants and ensure leaver runbooks cover each connected app. This recurring control addresses the observed problem: A departed contractor still has a refresh token for a connected application, and operations believes disabling browser login necessarily invalidates every existing grant. The measurable check is: Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.

Incorrect Answers

A:

Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Audit high-risk refresh grants and ensure leaver runbooks cover each connected app.

C:

Reapprove connected-app scope sets during each API integration feature expansion. Audit high-risk refresh grants and ensure leaver runbooks cover each connected app.

D:

Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change. Audit high-risk refresh grants and ensure leaver runbooks cover each connected app.

Certified Platform Identity and Access Management Architect Practice Tests