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 42

Question 0410 — Salesforce as an Identity Provider

At fictional Hollowbrook Logistics 41B, the team managing relying application federation reports: Several external Salesforce connected apps share one broad OAuth configuration and a common administrator-owned grant across unrelated business processes. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.
  2. Reconcile registered apps, scopes and named owners to the enterprise application inventory.
  3. Periodically test redirect URI matching and review changes to connected-app callback lists.
  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:

Reconcile registered apps, scopes and named owners to the enterprise application inventory. This recurring control addresses the observed problem: Several external Salesforce connected apps share one broad OAuth configuration and a common administrator-owned grant across unrelated business processes. The measurable check is: Review individual connected-app grants to show each has unique ownership, scope and revocation controls.

Incorrect Answers

A:

Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews. Reconcile registered apps, scopes and named owners to the enterprise application inventory.

C:

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

D:

Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change. Reconcile registered apps, scopes and named owners to the enterprise application inventory.

Question 0411 — Salesforce as an Identity Provider

At fictional Silver Orchard Care 42A, the team managing relying application federation reports: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.
  2. Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.
  3. Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.
  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:

Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements. Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

Incorrect Answers

A:

Configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials. The needed correction is to assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.

B:

Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization. The needed correction is to assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.

D:

Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment. The needed correction is to assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.

Question 0412 — Salesforce as an Identity Provider

At fictional Silver Orchard Care 42A, the team managing relying application federation reports: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.
  2. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.
  3. Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.
  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

D:

Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request. The corresponding correction is to assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.

Incorrect Answers

A:

Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient. The useful check here is whether complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

B:

Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access. The useful check here is whether complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

C:

Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds. The useful check here is whether complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

Question 0413 — Salesforce as an Identity Provider

At fictional Silver Orchard Care 42A, the team managing relying application federation reports: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Device-limited clients can delegate interactive approval to a separate secure authorization channel.
  2. Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate.
  3. Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side.
  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

A:

Device-limited clients can delegate interactive approval to a separate secure authorization channel. Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

Incorrect Answers

B:

Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate. Device-limited clients can delegate interactive approval to a separate secure authorization channel.

C:

Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side. Device-limited clients can delegate interactive approval to a separate secure authorization channel.

D:

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

Question 0414 — Salesforce as an Identity Provider

At fictional Silver Orchard Care 42A, the team managing relying application federation reports: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Extracted secrets and unbound codes create credential and authorization-code interception risks.
  2. Capturing credentials on untrusted shared devices enables theft and residual sessions.
  3. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.
  4. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Capturing credentials on untrusted shared devices enables theft and residual sessions. Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.

Incorrect Answers

A:

Extracted secrets and unbound codes create credential and authorization-code interception risks. Capturing credentials on untrusted shared devices enables theft and residual sessions.

C:

Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs. Capturing credentials on untrusted shared devices enables theft and residual sessions.

D:

Stale issuer acceptance can create federation outages or preserve obsolete trust paths. Capturing credentials on untrusted shared devices enables theft and residual sessions.

Question 0415 — Salesforce as an Identity Provider

At fictional Silver Orchard Care 42A, the team managing relying application federation reports: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Rotate integration credentials and review non-interactive principal scope during service ownership changes.
  2. Reapprove connected-app scope sets during each API integration feature expansion.
  3. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.
  4. Rehearse My Domain issuer and metadata rollovers with every external service provider.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change. This recurring control addresses the observed problem: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. The measurable check is: Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

Incorrect Answers

A:

Rotate integration credentials and review non-interactive principal scope during service ownership changes. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.

B:

Reapprove connected-app scope sets during each API integration feature expansion. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.

D:

Rehearse My Domain issuer and metadata rollovers with every external service provider. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.

Question 0416 — Salesforce as an Identity Provider

At fictional Pinehaven Commerce 42B, the team managing API integration authentication reports: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. 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. Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.
  3. Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.
  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

D:

Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements. Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

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 assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.

B:

Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage. The needed correction is to assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.

C:

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

Question 0417 — Salesforce as an Identity Provider

At fictional Pinehaven Commerce 42B, the team managing API integration authentication reports: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.
  2. Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.
  3. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.
  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:

Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request. The corresponding correction is to assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.

Incorrect Answers

B:

Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier. The useful check here is whether complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

C:

Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access. The useful check here is whether complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

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 complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

Question 0418 — Salesforce as an Identity Provider

At fictional Pinehaven Commerce 42B, the team managing API integration authentication reports: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Automated workload credentials should be independent of human interactive accounts and enforce least privilege.
  2. Device-limited clients can delegate interactive approval to a separate secure authorization channel.
  3. OAuth scope and local user permissions both constrain what a delegated token may do.
  4. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Device-limited clients can delegate interactive approval to a separate secure authorization channel. Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

Incorrect Answers

A:

Automated workload credentials should be independent of human interactive accounts and enforce least privilege. Device-limited clients can delegate interactive approval to a separate secure authorization channel.

C:

OAuth scope and local user permissions both constrain what a delegated token may do. Device-limited clients can delegate interactive approval to a separate secure authorization channel.

D:

Identity-provider continuity requires controlled metadata changes and relying-party trust verification. Device-limited clients can delegate interactive approval to a separate secure authorization channel.

Question 0419 — Salesforce as an Identity Provider

At fictional Pinehaven Commerce 42B, the team managing API integration authentication reports: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Exposed access tokens in browser code can be stolen and replayed by unauthorized parties.
  2. Excessive scopes increase the damage possible when an application token is compromised.
  3. Capturing credentials on untrusted shared devices enables theft and residual sessions.
  4. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Capturing credentials on untrusted shared devices enables theft and residual sessions. Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.

Incorrect Answers

A:

Exposed access tokens in browser code can be stolen and replayed by unauthorized parties. Capturing credentials on untrusted shared devices enables theft and residual sessions.

B:

Excessive scopes increase the damage possible when an application token is compromised. Capturing credentials on untrusted shared devices enables theft and residual sessions.

D:

Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs. Capturing credentials on untrusted shared devices enables theft and residual sessions.

Question 0420 — Salesforce as an Identity Provider

At fictional Pinehaven Commerce 42B, the team managing API integration authentication reports: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Scan build artifacts and redirect configurations for client credentials and token leakage.
  2. Reconcile registered apps, scopes and named owners to the enterprise application inventory.
  3. Review outbound callout credential mappings and principal permissions on a schedule.
  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

D:

Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change. This recurring control addresses the observed problem: A shared kiosk with no keyboard must complete a Salesforce-connected authorization flow but developers propose asking users to type their passwords into the kiosk. The measurable check is: Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.

Incorrect Answers

A:

Scan build artifacts and redirect configurations for client credentials and token leakage. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.

B:

Reconcile registered apps, scopes and named owners to the enterprise application inventory. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.

C:

Review outbound callout credential mappings and principal permissions on a schedule. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.

Certified Platform Identity and Access Management Architect Practice Tests