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 43

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.

Question 0421 — Salesforce as an Identity Provider

At fictional North Lake Financial 43A, the team managing API integration authentication reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.
  2. Use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.
  3. Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.
  4. Separate application registration and authorization policies by trust boundary, accountable owner and required data scope.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment. Trace a test callout using the approved credential principal with no reusable password in application code or logs.

Incorrect Answers

B:

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 prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.

C:

Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model. The needed correction is to prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.

D:

Separate application registration and authorization policies by trust boundary, accountable owner and required data scope. The needed correction is to prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.

Question 0422 — Salesforce as an Identity Provider

At fictional North Lake Financial 43A, the team managing API integration authentication reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. 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. Trace a test callout using the approved credential principal with no reusable password in application code or logs.
  3. Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.
  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

B:

Trace a test callout using the approved credential principal with no reusable password in application code or logs. The corresponding correction is to prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.

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 trace a test callout using the approved credential principal with no reusable password in application code or logs.

C:

Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations. The useful check here is whether trace a test callout using the approved credential principal with no reusable password in application code or logs.

D:

Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds. The useful check here is whether trace a test callout using the approved credential principal with no reusable password in application code or logs.

Question 0423 — Salesforce as an Identity Provider

At fictional North Lake Financial 43A, the team managing API integration authentication reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. 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. API authentication should be abstracted behind managed credentials with explicit principal authorization.
  4. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

API authentication should be abstracted behind managed credentials with explicit principal authorization. Trace a test callout using the approved credential principal with no reusable password in application code or logs.

Incorrect Answers

A:

Automated workload credentials should be independent of human interactive accounts and enforce least privilege. API authentication should be abstracted behind managed credentials with explicit principal authorization.

B:

Device-limited clients can delegate interactive approval to a separate secure authorization channel. API authentication should be abstracted behind managed credentials with explicit principal authorization.

D:

Identity-provider continuity requires controlled metadata changes and relying-party trust verification. API authentication should be abstracted behind managed credentials with explicit principal authorization.

Question 0424 — Salesforce as an Identity Provider

At fictional North Lake Financial 43A, the team managing API integration authentication reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. 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. Treating any signed identity token as API authorization opens confused-deputy token acceptance paths.
  3. Capturing credentials on untrusted shared devices enables theft and residual sessions.
  4. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges. Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.

Incorrect Answers

A:

Exposed access tokens in browser code can be stolen and replayed by unauthorized parties. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

B:

Treating any signed identity token as API authorization opens confused-deputy token acceptance paths. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

C:

Capturing credentials on untrusted shared devices enables theft and residual sessions. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

Question 0425 — Salesforce as an Identity Provider

At fictional North Lake Financial 43A, the team managing API integration authentication reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Review outbound callout credential mappings and principal permissions on a schedule.
  2. Reapprove connected-app scope sets during each API integration feature expansion.
  3. Reconcile registered apps, scopes and named owners to the enterprise application inventory.
  4. Rehearse My Domain issuer and metadata rollovers with every external service provider.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Review outbound callout credential mappings and principal permissions on a schedule. This recurring control addresses the observed problem: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. The measurable check is: Trace a test callout using the approved credential principal with no reusable password in application code or logs.

Incorrect Answers

B:

Reapprove connected-app scope sets during each API integration feature expansion. Review outbound callout credential mappings and principal permissions on a schedule.

C:

Reconcile registered apps, scopes and named owners to the enterprise application inventory. Review outbound callout credential mappings and principal permissions on a schedule.

D:

Rehearse My Domain issuer and metadata rollovers with every external service provider. Review outbound callout credential mappings and principal permissions on a schedule.

Question 0426 — Salesforce as an Identity Provider

At fictional Asterline Education 43B, the team managing external service identity reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.
  2. Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.
  3. Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.
  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

B:

Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment. Trace a test callout using the approved credential principal with no reusable password in application code or logs.

Incorrect Answers

A:

Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization. The needed correction is to prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.

C:

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

D:

Reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints. The needed correction is to prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.

Question 0427 — Salesforce as an Identity Provider

At fictional Asterline Education 43B, the team managing external service identity reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.
  2. Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.
  3. Trace a test callout using the approved credential principal with no reusable password in application code or logs.
  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:

Trace a test callout using the approved credential principal with no reusable password in application code or logs. The corresponding correction is to prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.

Incorrect Answers

A:

Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments. The useful check here is whether trace a test callout using the approved credential principal with no reusable password in application code or logs.

B:

Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds. The useful check here is whether trace a test callout using the approved credential principal with no reusable password in application code or logs.

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 trace a test callout using the approved credential principal with no reusable password in application code or logs.

Question 0428 — Salesforce as an Identity Provider

At fictional Asterline Education 43B, the team managing external service identity reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. Which security architecture principle most directly explains the remediation needed for these facts?

  1. OAuth scope and local user permissions both constrain what a delegated token may do.
  2. Independent relying applications should have isolatable least-privilege grants and governance.
  3. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.
  4. API authentication should be abstracted behind managed credentials with explicit principal authorization.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

API authentication should be abstracted behind managed credentials with explicit principal authorization. Trace a test callout using the approved credential principal with no reusable password in application code or logs.

Incorrect Answers

A:

OAuth scope and local user permissions both constrain what a delegated token may do. API authentication should be abstracted behind managed credentials with explicit principal authorization.

B:

Independent relying applications should have isolatable least-privilege grants and governance. API authentication should be abstracted behind managed credentials with explicit principal authorization.

C:

Identity-provider continuity requires controlled metadata changes and relying-party trust verification. API authentication should be abstracted behind managed credentials with explicit principal authorization.

Question 0429 — Salesforce as an Identity Provider

At fictional Asterline Education 43B, the team managing external service identity reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.
  2. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.
  3. One compromised broad connected-app grant can expose multiple unrelated services and datasets.
  4. Capturing credentials on untrusted shared devices enables theft and residual sessions.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges. Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.

Incorrect Answers

B:

Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

C:

One compromised broad connected-app grant can expose multiple unrelated services and datasets. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

D:

Capturing credentials on untrusted shared devices enables theft and residual sessions. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

Question 0430 — Salesforce as an Identity Provider

At fictional Asterline Education 43B, the team managing external service identity reports: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. 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. Review outbound callout credential mappings and principal permissions on a schedule.
  3. Rotate integration credentials and review non-interactive principal scope during service ownership changes.
  4. Reapprove connected-app scope sets during each API integration feature expansion.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Review outbound callout credential mappings and principal permissions on a schedule. This recurring control addresses the observed problem: An integration team places a shared static Salesforce password inside custom Named Credential metadata instead of using supported external credential principals. The measurable check is: Trace a test callout using the approved credential principal with no reusable password in application code or logs.

Incorrect Answers

A:

Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Review outbound callout credential mappings and principal permissions on a schedule.

C:

Rotate integration credentials and review non-interactive principal scope during service ownership changes. Review outbound callout credential mappings and principal permissions on a schedule.

D:

Reapprove connected-app scope sets during each API integration feature expansion. Review outbound callout credential mappings and principal permissions on a schedule.

Certified Platform Identity and Access Management Architect Practice Tests