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 39

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.

Question 0381 — Salesforce as an Identity Provider

At fictional Clearbrook Labs 39A, the team managing external service identity reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.
  2. Configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.
  3. Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.
  4. Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations. Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

Incorrect Answers

B:

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 restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.

C:

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

D:

Explicitly review connected-app token revocation and user deactivation behavior, then revoke the affected OAuth grants under incident procedure. The needed correction is to restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.

Question 0382 — Salesforce as an Identity Provider

At fictional Clearbrook Labs 39A, the team managing external service identity reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. 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. Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.
  3. Review individual connected-app grants to show each has unique ownership, scope and revocation controls.
  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

B:

Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery. The corresponding correction is to restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.

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 attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

C:

Review individual connected-app grants to show each has unique ownership, scope and revocation controls. The useful check here is whether attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

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 attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

Question 0383 — Salesforce as an Identity Provider

At fictional Clearbrook Labs 39A, the team managing external service identity reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate.
  2. OAuth scope and local user permissions both constrain what a delegated token may do.
  3. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.
  4. Independent relying applications should have isolatable least-privilege grants and governance.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration. Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

Incorrect Answers

A:

Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.

B:

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

D:

Independent relying applications should have isolatable least-privilege grants and governance. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.

Question 0384 — Salesforce as an Identity Provider

At fictional Clearbrook Labs 39A, the team managing external service identity reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. 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. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.
  3. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.
  4. Loose redirect validation can leak authorization codes to unintended recipients.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Loose redirect validation can leak authorization codes to unintended recipients. Restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.

Incorrect Answers

A:

Extracted secrets and unbound codes create credential and authorization-code interception risks. Loose redirect validation can leak authorization codes to unintended recipients.

B:

Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges. Loose redirect validation can leak authorization codes to unintended recipients.

C:

Stale issuer acceptance can create federation outages or preserve obsolete trust paths. Loose redirect validation can leak authorization codes to unintended recipients.

Question 0385 — Salesforce as an Identity Provider

At fictional Clearbrook Labs 39A, the team managing external service identity reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Periodically test redirect URI matching and review changes to connected-app callback lists.
  2. Rotate integration credentials and review non-interactive principal scope during service ownership changes.
  3. Validate selected flow type against client capabilities and security requirements before deploying integrations.
  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

A:

Periodically test redirect URI matching and review changes to connected-app callback lists. This recurring control addresses the observed problem: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. The measurable check is: Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

Incorrect Answers

B:

Rotate integration credentials and review non-interactive principal scope during service ownership changes. Periodically test redirect URI matching and review changes to connected-app callback lists.

C:

Validate selected flow type against client capabilities and security requirements before deploying integrations. Periodically test redirect URI matching and review changes to connected-app callback lists.

D:

Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change. Periodically test redirect URI matching and review changes to connected-app callback lists.

Question 0386 — Salesforce as an Identity Provider

At fictional Laurelfield Transit 39B, the team managing OAuth token lifecycle reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. 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. Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.
  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

B:

Restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations. Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

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 restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.

C:

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

D:

Separate application registration and authorization policies by trust boundary, accountable owner and required data scope. The needed correction is to restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.

Question 0387 — Salesforce as an Identity Provider

At fictional Laurelfield Transit 39B, the team managing OAuth token lifecycle reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. 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. Trace a test callout using the approved credential principal with no reusable password in application code or logs.
  3. Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.
  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

C:

Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery. The corresponding correction is to restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.

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 attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

B:

Trace a test callout using the approved credential principal with no reusable password in application code or logs. The useful check here is whether attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

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 attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

Question 0388 — Salesforce as an Identity Provider

At fictional Laurelfield Transit 39B, the team managing OAuth token lifecycle reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. 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. 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. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration. Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

Incorrect Answers

A:

Automated workload credentials should be independent of human interactive accounts and enforce least privilege. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.

B:

Machine workloads should not emulate user-agent browser sessions to obtain unattended access. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.

C:

Device-limited clients can delegate interactive approval to a separate secure authorization channel. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.

Question 0389 — Salesforce as an Identity Provider

At fictional Laurelfield Transit 39B, the team managing OAuth token lifecycle reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Loose redirect validation can leak authorization codes to unintended recipients.
  2. Exposed access tokens in browser code can be stolen and replayed by unauthorized parties.
  3. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.
  4. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Loose redirect validation can leak authorization codes to unintended recipients. Restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.

Incorrect Answers

B:

Exposed access tokens in browser code can be stolen and replayed by unauthorized parties. Loose redirect validation can leak authorization codes to unintended recipients.

C:

Overlooking long-lived refresh grants extends access beyond intended offboarding controls. Loose redirect validation can leak authorization codes to unintended recipients.

D:

Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges. Loose redirect validation can leak authorization codes to unintended recipients.

Question 0390 — Salesforce as an Identity Provider

At fictional Laurelfield Transit 39B, the team managing OAuth token lifecycle reports: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Reapprove connected-app scope sets during each API integration feature expansion.
  2. Periodically test redirect URI matching and review changes to connected-app callback lists.
  3. Validate selected flow type against client capabilities and security requirements before deploying integrations.
  4. Reconcile registered apps, scopes and named owners to the enterprise application inventory.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Periodically test redirect URI matching and review changes to connected-app callback lists. This recurring control addresses the observed problem: An OAuth-connected web application accepts any callback URL beginning with an approved hostname, including attacker-controlled paths and redirect parameters. The measurable check is: Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.

Incorrect Answers

A:

Reapprove connected-app scope sets during each API integration feature expansion. Periodically test redirect URI matching and review changes to connected-app callback lists.

C:

Validate selected flow type against client capabilities and security requirements before deploying integrations. Periodically test redirect URI matching and review changes to connected-app callback lists.

D:

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

Certified Platform Identity and Access Management Architect Practice Tests