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 41

Question 0400 — Salesforce as an Identity Provider

At fictional Seabrook Systems 40B, the team managing connected-app authorization reports: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. 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. Scan build artifacts and redirect configurations for client credentials and token leakage.
  3. Validate selected flow type against client capabilities and security requirements before deploying integrations.
  4. Test token type/audience separation at resource servers and connected-app boundaries.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Test token type/audience separation at resource servers and connected-app boundaries. This recurring control addresses the observed problem: A partner API rejects OIDC ID tokens correctly but developers demand that API accept them as bearer authorization simply because they include a username. The measurable check is: Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.

Incorrect Answers

A:

Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Test token type/audience separation at resource servers and connected-app boundaries.

B:

Scan build artifacts and redirect configurations for client credentials and token leakage. Test token type/audience separation at resource servers and connected-app boundaries.

C:

Validate selected flow type against client capabilities and security requirements before deploying integrations. Test token type/audience separation at resource servers and connected-app boundaries.

Question 0401 — Salesforce as an Identity Provider

At fictional Cedar Vale Research 41A, the team managing connected-app authorization reports: Several external Salesforce connected apps share one broad OAuth configuration and a common administrator-owned grant across unrelated business processes. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Separate application registration and authorization policies by trust boundary, accountable owner and required data scope.
  2. Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.
  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

A:

Separate application registration and authorization policies by trust boundary, accountable owner and required data scope. Review individual connected-app grants to show each has unique ownership, scope and revocation controls.

Incorrect Answers

B:

Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior. The needed correction is to separate application registration and authorization policies by trust boundary, accountable owner and required data scope.

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 separate application registration and authorization policies by trust boundary, accountable owner and required data scope.

D:

Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements. The needed correction is to separate application registration and authorization policies by trust boundary, accountable owner and required data scope.

Question 0402 — Salesforce as an Identity Provider

At fictional Cedar Vale Research 41A, the team managing connected-app authorization reports: Several external Salesforce connected apps share one broad OAuth configuration and a common administrator-owned grant across unrelated business processes. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Verify a revoked refresh token fails to mint new access tokens and document the residual lifetime of any access tokens.
  2. Review individual connected-app grants to show each has unique ownership, scope and revocation controls.
  3. Attempt a token flow with an unauthorized redirect URL and confirm it is rejected before code delivery.
  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

B:

Review individual connected-app grants to show each has unique ownership, scope and revocation controls. The corresponding correction is to separate application registration and authorization policies by trust boundary, accountable owner and required data scope.

Incorrect Answers

A:

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 review individual connected-app grants to show each has unique ownership, scope and revocation controls.

C:

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

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 review individual connected-app grants to show each has unique ownership, scope and revocation controls.

Question 0403 — Salesforce as an Identity Provider

At fictional Cedar Vale Research 41A, the team managing connected-app authorization reports: Several external Salesforce connected apps share one broad OAuth configuration and a common administrator-owned grant across unrelated business processes. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.
  2. API authentication should be abstracted behind managed credentials with explicit principal authorization.
  3. Independent relying applications should have isolatable least-privilege grants and governance.
  4. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Independent relying applications should have isolatable least-privilege grants and governance. Review individual connected-app grants to show each has unique ownership, scope and revocation controls.

Incorrect Answers

A:

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

B:

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

D:

Identity-provider continuity requires controlled metadata changes and relying-party trust verification. Independent relying applications should have isolatable least-privilege grants and governance.

Question 0404 — Salesforce as an Identity Provider

At fictional Cedar Vale Research 41A, the team managing connected-app authorization reports: Several external Salesforce connected apps share one broad OAuth configuration and a common administrator-owned grant across unrelated business processes. 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. Exposed access tokens in browser code can be stolen and replayed by unauthorized parties.
  3. Excessive scopes increase the damage possible when an application token is compromised.
  4. One compromised broad connected-app grant can expose multiple unrelated services and datasets.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

One compromised broad connected-app grant can expose multiple unrelated services and datasets. Separate application registration and authorization policies by trust boundary, accountable owner and required data scope.

Incorrect Answers

A:

Password replication multiplies credential exposure and obscures authoritative identity governance. One compromised broad connected-app grant can expose multiple unrelated services and datasets.

B:

Exposed access tokens in browser code can be stolen and replayed by unauthorized parties. One compromised broad connected-app grant can expose multiple unrelated services and datasets.

C:

Excessive scopes increase the damage possible when an application token is compromised. One compromised broad connected-app grant can expose multiple unrelated services and datasets.

Question 0405 — Salesforce as an Identity Provider

At fictional Cedar Vale Research 41A, the team managing connected-app authorization 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. Reconcile registered apps, scopes and named owners to the enterprise application inventory.
  2. Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis.
  3. Validate selected flow type against client capabilities and security requirements before deploying integrations.
  4. Review outbound callout credential mappings and principal permissions on a schedule.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

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

B:

Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Reconcile registered apps, scopes and named owners to the enterprise application inventory.

C:

Validate selected flow type against client capabilities and security requirements before deploying integrations. Reconcile registered apps, scopes and named owners to the enterprise application inventory.

D:

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

Question 0406 — 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 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. Separate application registration and authorization policies by trust boundary, accountable owner and required data scope.
  3. Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.
  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:

Separate application registration and authorization policies by trust boundary, accountable owner and required data scope. Review individual connected-app grants to show each has unique ownership, scope and revocation controls.

Incorrect Answers

A:

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

C:

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

D:

Reconcile Salesforce identity-provider issuer metadata and partner trust anchors before switching production federation endpoints. The needed correction is to separate application registration and authorization policies by trust boundary, accountable owner and required data scope.

Question 0407 — 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 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. Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.
  3. Review individual connected-app grants to show each has unique ownership, scope and revocation controls.
  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

C:

Review individual connected-app grants to show each has unique ownership, scope and revocation controls. The corresponding correction is to separate application registration and authorization policies by trust boundary, accountable owner and required data scope.

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 review individual connected-app grants to show each has unique ownership, scope and revocation controls.

B:

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 review individual connected-app grants to show each has unique ownership, scope and revocation controls.

D:

Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations. The useful check here is whether review individual connected-app grants to show each has unique ownership, scope and revocation controls.

Question 0408 — 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 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. API authentication should be abstracted behind managed credentials with explicit principal authorization.
  4. Independent relying applications should have isolatable least-privilege grants and governance.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Independent relying applications should have isolatable least-privilege grants and governance. Review individual connected-app grants to show each has unique ownership, scope and revocation controls.

Incorrect Answers

A:

Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications. Independent relying applications should have isolatable least-privilege grants and governance.

B:

Machine workloads should not emulate user-agent browser sessions to obtain unattended access. Independent relying applications should have isolatable least-privilege grants and governance.

C:

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

Question 0409 — 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. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. One compromised broad connected-app grant can expose multiple unrelated services and datasets.
  2. Extracted secrets and unbound codes create credential and authorization-code interception risks.
  3. Exposed access tokens in browser code can be stolen and replayed by unauthorized parties.
  4. Loose redirect validation can leak authorization codes to unintended recipients.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

One compromised broad connected-app grant can expose multiple unrelated services and datasets. Separate application registration and authorization policies by trust boundary, accountable owner and required data scope.

Incorrect Answers

B:

Extracted secrets and unbound codes create credential and authorization-code interception risks. One compromised broad connected-app grant can expose multiple unrelated services and datasets.

C:

Exposed access tokens in browser code can be stolen and replayed by unauthorized parties. One compromised broad connected-app grant can expose multiple unrelated services and datasets.

D:

Loose redirect validation can leak authorization codes to unintended recipients. One compromised broad connected-app grant can expose multiple unrelated services and datasets.

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.

Certified Platform Identity and Access Management Architect Practice Tests