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 35

Question 0340 — Salesforce as an Identity Provider

At fictional Lighthouse Nonprofit 34B, the team managing OAuth token lifecycle reports: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. 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. Periodically test redirect URI matching and review changes to connected-app callback lists.
  3. Reconcile registered apps, scopes and named owners to the enterprise application inventory.
  4. Rotate integration credentials and review non-interactive principal scope during service ownership changes.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Rotate integration credentials and review non-interactive principal scope during service ownership changes. This recurring control addresses the observed problem: A headless middleware service needs Salesforce API access without an interactive user, but its job stores a human employee's reusable password. The measurable check is: Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.

Incorrect Answers

A:

Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. Rotate integration credentials and review non-interactive principal scope during service ownership changes.

B:

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

C:

Reconcile registered apps, scopes and named owners to the enterprise application inventory. Rotate integration credentials and review non-interactive principal scope during service ownership changes.

Question 0341 — Salesforce as an Identity Provider

At fictional Bluebrook Agriculture 35A, the team managing OAuth token lifecycle reports: A confidential server-rendered web app needs Salesforce user authorization and developers propose placing access tokens in front-end source code. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.
  2. Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.
  3. Restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations.
  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:

Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage. Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.

Incorrect Answers

B:

Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model. The needed correction is to use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.

C:

Restrict redirect URIs to exact approved values and reject unregistered or ambiguously normalized callback destinations. The needed correction is to use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.

D:

Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements. The needed correction is to use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.

Question 0342 — Salesforce as an Identity Provider

At fictional Bluebrook Agriculture 35A, the team managing OAuth token lifecycle reports: A confidential server-rendered web app needs Salesforce user authorization and developers propose placing access tokens in front-end source code. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Show an ID token fails protected API authorization while an audience-scoped access token with appropriate grants succeeds.
  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. Trace a test callout using the approved credential principal with no reusable password in application code or logs.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments. The corresponding correction is to use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.

Incorrect Answers

A:

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 the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.

C:

Review individual connected-app grants to show each has unique ownership, scope and revocation controls. The useful check here is whether trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.

D:

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

Question 0343 — Salesforce as an Identity Provider

At fictional Bluebrook Agriculture 35A, the team managing OAuth token lifecycle reports: A confidential server-rendered web app needs Salesforce user authorization and developers propose placing access tokens in front-end source code. 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. Automated workload credentials should be independent of human interactive accounts and enforce least privilege.
  3. Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side.
  4. Independent relying applications should have isolatable least-privilege grants and governance.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side. Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.

Incorrect Answers

A:

Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications. Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side.

B:

Automated workload credentials should be independent of human interactive accounts and enforce least privilege. Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side.

D:

Independent relying applications should have isolatable least-privilege grants and governance. Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side.

Question 0344 — Salesforce as an Identity Provider

At fictional Bluebrook Agriculture 35A, the team managing OAuth token lifecycle reports: A confidential server-rendered web app needs Salesforce user authorization and developers propose placing access tokens in front-end source code. 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. Stale issuer acceptance can create federation outages or preserve obsolete trust paths.
  4. Exposed access tokens in browser code can be stolen and replayed by unauthorized parties.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Exposed access tokens in browser code can be stolen and replayed by unauthorized parties. Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.

Incorrect Answers

A:

Password replication multiplies credential exposure and obscures authoritative identity governance. Exposed access tokens in browser code can be stolen and replayed by unauthorized parties.

B:

Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs. Exposed access tokens in browser code can be stolen and replayed by unauthorized parties.

C:

Stale issuer acceptance can create federation outages or preserve obsolete trust paths. Exposed access tokens in browser code can be stolen and replayed by unauthorized parties.

Question 0345 — Salesforce as an Identity Provider

At fictional Bluebrook Agriculture 35A, the team managing OAuth token lifecycle 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. Scan build artifacts and redirect configurations for client credentials and token leakage.
  2. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.
  3. Rotate integration credentials and review non-interactive principal scope during service ownership changes.
  4. Rehearse My Domain issuer and metadata rollovers with every external service provider.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

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

B:

Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews. Scan build artifacts and redirect configurations for client credentials and token leakage.

C:

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.

D:

Rehearse My Domain issuer and metadata rollovers with every external service provider. Scan build artifacts and redirect configurations for client credentials and token leakage.

Question 0346 — 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 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 a server-side authorization code exchange with an approved redirect URI and secure backend token storage.
  3. Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.
  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:

Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage. Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.

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 use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.

C:

Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization. The needed correction is to use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.

D:

Separate application registration and authorization policies by trust boundary, accountable owner and required data scope. The needed correction is to use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.

Question 0347 — 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 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. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.
  3. Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.
  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:

Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments. The corresponding correction is to use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.

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 trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.

B:

Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access. The useful check here is whether trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.

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 trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.

Question 0348 — 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 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. Automated workload credentials should be independent of human interactive accounts and enforce least privilege.
  3. Identity-provider continuity requires controlled metadata changes and relying-party trust verification.
  4. Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side. Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.

Incorrect Answers

A:

Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate. Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side.

B:

Automated workload credentials should be independent of human interactive accounts and enforce least privilege. Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side.

C:

Identity-provider continuity requires controlled metadata changes and relying-party trust verification. Confidential clients can protect credentials when authorization tokens are exchanged and stored server-side.

Question 0349 — 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. 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. Extracted secrets and unbound codes create credential and authorization-code interception risks.
  3. Loose redirect validation can leak authorization codes to unintended recipients.
  4. Capturing credentials on untrusted shared devices enables theft and residual sessions.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Exposed access tokens in browser code can be stolen and replayed by unauthorized parties. Use a server-side authorization code exchange with an approved redirect URI and secure backend token storage.

Incorrect Answers

B:

Extracted secrets and unbound codes create credential and authorization-code interception risks. Exposed access tokens in browser code can be stolen and replayed by unauthorized parties.

C:

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

D:

Capturing credentials on untrusted shared devices enables theft and residual sessions. Exposed access tokens in browser code can be stolen and replayed by unauthorized parties.

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.

Certified Platform Identity and Access Management Architect Practice Tests