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 38

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.

Question 0371 — Salesforce as an Identity Provider

At fictional Fern Ridge Services 38A, the team managing API integration authentication reports: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.
  2. Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.
  3. Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.
  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:

Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

Incorrect Answers

A:

Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior. The needed correction is to select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.

B:

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 select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.

D:

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

Question 0372 — Salesforce as an Identity Provider

At fictional Fern Ridge Services 38A, the team managing API integration authentication reports: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.
  2. Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.
  3. Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.
  4. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access. The corresponding correction is to select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.

Incorrect Answers

A:

Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery. The useful check here is whether run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

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 run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

C:

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

Question 0373 — Salesforce as an Identity Provider

At fictional Fern Ridge Services 38A, the team managing API integration authentication reports: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Machine workloads should not emulate user-agent browser sessions to obtain unattended access.
  2. Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications.
  3. Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate.
  4. Identity assertions and resource access grants are separate token classes with different audiences and claims.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Machine workloads should not emulate user-agent browser sessions to obtain unattended access. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

Incorrect Answers

B:

Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications. Machine workloads should not emulate user-agent browser sessions to obtain unattended access.

C:

Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate. Machine workloads should not emulate user-agent browser sessions to obtain unattended access.

D:

Identity assertions and resource access grants are separate token classes with different audiences and claims. Machine workloads should not emulate user-agent browser sessions to obtain unattended access.

Question 0374 — Salesforce as an Identity Provider

At fictional Fern Ridge Services 38A, the team managing API integration authentication reports: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Password replication multiplies credential exposure and obscures authoritative identity governance.
  2. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.
  3. Excessive scopes increase the damage possible when an application token is compromised.
  4. Treating any signed identity token as API authorization opens confused-deputy token acceptance paths.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs. Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.

Incorrect Answers

A:

Password replication multiplies credential exposure and obscures authoritative identity governance. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.

C:

Excessive scopes increase the damage possible when an application token is compromised. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.

D:

Treating any signed identity token as API authorization opens confused-deputy token acceptance paths. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.

Question 0375 — Salesforce as an Identity Provider

At fictional Fern Ridge Services 38A, the team managing API integration authentication reports: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. 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. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.
  3. Validate selected flow type against client capabilities and security requirements before deploying integrations.
  4. Rehearse My Domain issuer and metadata rollovers with every external service provider.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Validate selected flow type against client capabilities and security requirements before deploying integrations. This recurring control addresses the observed problem: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. The measurable check is: Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

Incorrect Answers

A:

Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Validate selected flow type against client capabilities and security requirements before deploying integrations.

B:

Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change. Validate selected flow type against client capabilities and security requirements before deploying integrations.

D:

Rehearse My Domain issuer and metadata rollovers with every external service provider. Validate selected flow type against client capabilities and security requirements before deploying integrations.

Question 0376 — Salesforce as an Identity Provider

At fictional Ember Coast Media 38B, the team managing external service identity reports: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. 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. Use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.
  3. Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.
  4. Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

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 select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.

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 select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.

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 select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.

Question 0377 — Salesforce as an Identity Provider

At fictional Ember Coast Media 38B, the team managing external service identity reports: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.
  2. Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.
  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

A:

Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access. The corresponding correction is to select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.

Incorrect Answers

B:

Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient. The useful check here is whether run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

C:

Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations. The useful check here is whether run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

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 run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

Question 0378 — Salesforce as an Identity Provider

At fictional Ember Coast Media 38B, the team managing external service identity reports: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications.
  2. Machine workloads should not emulate user-agent browser sessions to obtain unattended access.
  3. Device-limited clients can delegate interactive approval to a separate secure authorization channel.
  4. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Machine workloads should not emulate user-agent browser sessions to obtain unattended access. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

Incorrect Answers

A:

Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications. Machine workloads should not emulate user-agent browser sessions to obtain unattended access.

C:

Device-limited clients can delegate interactive approval to a separate secure authorization channel. Machine workloads should not emulate user-agent browser sessions to obtain unattended access.

D:

Identity-provider continuity requires controlled metadata changes and relying-party trust verification. Machine workloads should not emulate user-agent browser sessions to obtain unattended access.

Question 0379 — Salesforce as an Identity Provider

At fictional Ember Coast Media 38B, the team managing external service identity reports: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. 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. Excessive scopes increase the damage possible when an application token is compromised.
  3. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.
  4. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs. Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.

Incorrect Answers

A:

Extracted secrets and unbound codes create credential and authorization-code interception risks. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.

B:

Excessive scopes increase the damage possible when an application token is compromised. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.

D:

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

Question 0380 — Salesforce as an Identity Provider

At fictional Ember Coast Media 38B, the team managing external service identity reports: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. 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. Scan build artifacts and redirect configurations for client credentials and token leakage.
  3. Audit high-risk refresh grants and ensure leaver runbooks cover each connected app.
  4. Validate selected flow type against client capabilities and security requirements before deploying integrations.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Validate selected flow type against client capabilities and security requirements before deploying integrations. This recurring control addresses the observed problem: A back-end finance batch integration chooses the OAuth user-agent flow despite never presenting an interactive user or browser. The measurable check is: Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.

Incorrect Answers

A:

Rotate integration credentials and review non-interactive principal scope during service ownership changes. Validate selected flow type against client capabilities and security requirements before deploying integrations.

B:

Scan build artifacts and redirect configurations for client credentials and token leakage. Validate selected flow type against client capabilities and security requirements before deploying integrations.

C:

Audit high-risk refresh grants and ensure leaver runbooks cover each connected app. Validate selected flow type against client capabilities and security requirements before deploying integrations.

Certified Platform Identity and Access Management Architect Practice Tests