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 36

Question 0350 — Salesforce as an Identity Provider

At fictional Sagebridge Manufacturing 35B, the team managing connected-app authorization reports: A confidential server-rendered web app needs Salesforce user authorization and developers propose placing access tokens in front-end source code. 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. Reconcile registered apps, scopes and named owners to the enterprise application inventory.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Scan build artifacts and redirect configurations for client credentials and token leakage. This recurring control addresses the observed problem: A confidential server-rendered web app needs Salesforce user authorization and developers propose placing access tokens in front-end source code. The measurable check is: Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.

Incorrect Answers

A:

Rotate integration credentials and review non-interactive principal scope during service ownership changes. Scan build artifacts and redirect configurations for client credentials and token leakage.

C:

Audit high-risk refresh grants and ensure leaver runbooks cover each connected app. Scan build artifacts and redirect configurations for client credentials and token leakage.

D:

Reconcile registered apps, scopes and named owners to the enterprise application inventory. Scan build artifacts and redirect configurations for client credentials and token leakage.

Question 0351 — Salesforce as an Identity Provider

At fictional Granite Plain Utilities 36A, the team managing connected-app authorization reports: A connected application asks for broad Salesforce API scopes even though it only needs read-only identity attributes for an external dashboard. 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. Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.
  3. Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.
  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

C:

Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior. Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.

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 choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.

B:

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

D:

Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements. The needed correction is to choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.

Question 0352 — Salesforce as an Identity Provider

At fictional Granite Plain Utilities 36A, the team managing connected-app authorization reports: A connected application asks for broad Salesforce API scopes even though it only needs read-only identity attributes for an external dashboard. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.
  2. Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.
  3. Complete a test showing verification on a separate trusted device and secure expiry of the kiosk authorization request.
  4. Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations. The corresponding correction is to choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.

Incorrect Answers

A:

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 verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.

B:

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 token can read the approved identity fields but cannot invoke unrelated administrative operations.

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 verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.

Question 0353 — Salesforce as an Identity Provider

At fictional Granite Plain Utilities 36A, the team managing connected-app authorization reports: A connected application asks for broad Salesforce API scopes even though it only needs read-only identity attributes for an external dashboard. 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. Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate.
  3. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.
  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:

OAuth scope and local user permissions both constrain what a delegated token may do. Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.

Incorrect Answers

B:

Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate. OAuth scope and local user permissions both constrain what a delegated token may do.

C:

Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration. OAuth scope and local user permissions both constrain what a delegated token may do.

D:

Identity assertions and resource access grants are separate token classes with different audiences and claims. OAuth scope and local user permissions both constrain what a delegated token may do.

Question 0354 — Salesforce as an Identity Provider

At fictional Granite Plain Utilities 36A, the team managing connected-app authorization reports: A connected application asks for broad Salesforce API scopes even though it only needs read-only identity attributes for an external dashboard. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Reusing an employee password creates outages and untraceable automation when employment status changes.
  2. Excessive scopes increase the damage possible when an application token is compromised.
  3. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.
  4. Loose redirect validation can leak authorization codes to unintended recipients.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Excessive scopes increase the damage possible when an application token is compromised. Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.

Incorrect Answers

A:

Reusing an employee password creates outages and untraceable automation when employment status changes. Excessive scopes increase the damage possible when an application token is compromised.

C:

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

D:

Loose redirect validation can leak authorization codes to unintended recipients. Excessive scopes increase the damage possible when an application token is compromised.

Question 0355 — Salesforce as an Identity Provider

At fictional Granite Plain Utilities 36A, the team managing connected-app authorization 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. Rotate integration credentials and review non-interactive principal scope during service ownership changes.
  2. Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change.
  3. Reapprove connected-app scope sets during each API integration feature expansion.
  4. Review outbound callout credential mappings and principal permissions on a schedule.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

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:

Rotate integration credentials and review non-interactive principal scope during service ownership changes. Reapprove connected-app scope sets during each API integration feature expansion.

B:

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

D:

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

Question 0356 — 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 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. Restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.
  3. Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.
  4. Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior. Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.

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 choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.

B:

Restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations. The needed correction is to choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.

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 choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.

Question 0357 — 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 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. Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.
  3. Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.
  4. Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations. The corresponding correction is to choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.

Incorrect Answers

B:

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 token can read the approved identity fields but cannot invoke unrelated administrative operations.

C:

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

D:

Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery. The useful check here is whether verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.

Question 0358 — 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 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. OAuth scope and local user permissions both constrain what a delegated token may do.
  3. Device-limited clients can delegate interactive approval to a separate secure authorization channel.
  4. API authentication should be abstracted behind managed credentials with explicit principal authorization.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

OAuth scope and local user permissions both constrain what a delegated token may do. Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.

Incorrect Answers

A:

Automated workload credentials should be independent of human interactive accounts and enforce least privilege. OAuth scope and local user permissions both constrain what a delegated token may do.

C:

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

D:

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

Question 0359 — 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. 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. Excessive scopes increase the damage possible when an application token is compromised.
  4. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Excessive scopes increase the damage possible when an application token is compromised. Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.

Incorrect Answers

A:

Exposed access tokens in browser code can be stolen and replayed by unauthorized parties. Excessive scopes increase the damage possible when an application token is compromised.

B:

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

D:

Stale issuer acceptance can create federation outages or preserve obsolete trust paths. Excessive scopes increase the damage possible when an application token is compromised.

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.

Certified Platform Identity and Access Management Architect Practice Tests