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 33

Question 0320 — Salesforce as an Identity Provider

At fictional Pinehaven Commerce 32B, the team managing API integration authentication reports: An external partner portal must accept Salesforce employee identities via SAML, but the architecture team plans to make the partner authenticate against an untrusted copy of passwords. 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. Periodically test redirect URI matching and review changes to connected-app callback lists.
  3. Test token type/audience separation at resource servers and connected-app boundaries.
  4. Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis. This recurring control addresses the observed problem: An external partner portal must accept Salesforce employee identities via SAML, but the architecture team plans to make the partner authenticate against an untrusted copy of passwords. The measurable check is: Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

Incorrect Answers

A:

Scan build artifacts and redirect configurations for client credentials and token leakage. Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis.

B:

Periodically test redirect URI matching and review changes to connected-app callback lists. Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis.

C:

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

Question 0321 — Salesforce as an Identity Provider

At fictional North Lake Financial 33A, the team managing API integration authentication reports: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. 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. Configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.
  3. Issue or obtain access tokens intended for the resource API and use ID tokens only for their validated authentication purpose.
  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

A:

Use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret. Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

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 use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.

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 use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.

D:

Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment. The needed correction is to use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.

Question 0322 — Salesforce as an Identity Provider

At fictional North Lake Financial 33A, the team managing API integration authentication reports: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope.
  2. Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.
  3. Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.
  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:

Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier. The corresponding correction is to use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.

Incorrect Answers

A:

Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope. The useful check here is whether inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

C:

Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations. The useful check here is whether inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

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 inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

Question 0323 — Salesforce as an Identity Provider

At fictional North Lake Financial 33A, the team managing API integration authentication reports: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. 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. Independent relying applications should have isolatable least-privilege grants and governance.
  3. Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate.
  4. API authentication should be abstracted behind managed credentials with explicit principal authorization.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate. Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

Incorrect Answers

A:

Automated workload credentials should be independent of human interactive accounts and enforce least privilege. Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate.

B:

Independent relying applications should have isolatable least-privilege grants and governance. Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate.

D:

API authentication should be abstracted behind managed credentials with explicit principal authorization. Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate.

Question 0324 — Salesforce as an Identity Provider

At fictional North Lake Financial 33A, the team managing API integration authentication reports: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. 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. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.
  3. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.
  4. Extracted secrets and unbound codes create credential and authorization-code interception risks.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Extracted secrets and unbound codes create credential and authorization-code interception risks. Use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.

Incorrect Answers

A:

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

B:

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

C:

Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges. Extracted secrets and unbound codes create credential and authorization-code interception risks.

Question 0325 — Salesforce as an Identity Provider

At fictional North Lake Financial 33A, the team managing API integration authentication reports: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. 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. Reapprove connected-app scope sets during each API integration feature expansion.
  3. Validate selected flow type against client capabilities and security requirements before deploying integrations.
  4. Periodically test redirect URI matching and review changes to connected-app callback lists.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews. This recurring control addresses the observed problem: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. The measurable check is: Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

Incorrect Answers

B:

Reapprove connected-app scope sets during each API integration feature expansion. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.

C:

Validate selected flow type against client capabilities and security requirements before deploying integrations. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.

D:

Periodically test redirect URI matching and review changes to connected-app callback lists. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.

Question 0326 — Salesforce as an Identity Provider

At fictional Asterline Education 33B, the team managing external service identity reports: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization.
  2. Use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.
  3. Separate application registration and authorization policies by trust boundary, accountable owner and required data scope.
  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

B:

Use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret. Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

Incorrect Answers

A:

Evaluate a supported non-interactive machine-to-machine authentication pattern with dedicated integration principal and scoped authorization. The needed correction is to use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.

C:

Separate application registration and authorization policies by trust boundary, accountable owner and required data scope. The needed correction is to use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.

D:

Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment. The needed correction is to use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.

Question 0327 — Salesforce as an Identity Provider

At fictional Asterline Education 33B, the team managing external service identity reports: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Trace the browser callback and server exchange while confirming token secrets are absent from the HTML and browser URL fragments.
  2. Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access.
  3. Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.
  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

C:

Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier. The corresponding correction is to use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.

Incorrect Answers

A:

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 inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

B:

Run a controlled batch with machine authentication, server-side secret handling and least-privilege API access. The useful check here is whether inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

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 inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

Question 0328 — Salesforce as an Identity Provider

At fictional Asterline Education 33B, the team managing external service identity reports: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. 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. Machine workloads should not emulate user-agent browser sessions to obtain unattended access.
  3. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.
  4. Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate. Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

Incorrect Answers

A:

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

B:

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

C:

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

Question 0329 — Salesforce as an Identity Provider

At fictional Asterline Education 33B, the team managing external service identity reports: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. 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. Overlooking long-lived refresh grants extends access beyond intended offboarding controls.
  3. Misapplied browser flows create fragile token handling and unreviewed privileges in batch jobs.
  4. Capturing credentials on untrusted shared devices enables theft and residual sessions.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Extracted secrets and unbound codes create credential and authorization-code interception risks. Use authorization-code flow with PKCE and system-browser redirection for public mobile clients instead of shipping an extractable secret.

Incorrect Answers

B:

Overlooking long-lived refresh grants extends access beyond intended offboarding controls. Extracted secrets and unbound codes create credential and authorization-code interception risks.

C:

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

D:

Capturing credentials on untrusted shared devices enables theft and residual sessions. Extracted secrets and unbound codes create credential and authorization-code interception risks.

Question 0330 — Salesforce as an Identity Provider

At fictional Asterline Education 33B, the team managing external service identity reports: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Validate selected flow type against client capabilities and security requirements before deploying integrations.
  2. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.
  3. Test token type/audience separation at resource servers and connected-app boundaries.
  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:

Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews. This recurring control addresses the observed problem: A public native mobile application uses an embedded password flow and stores a client secret in the distributed application binary. The measurable check is: Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.

Incorrect Answers

A:

Validate selected flow type against client capabilities and security requirements before deploying integrations. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.

C:

Test token type/audience separation at resource servers and connected-app boundaries. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.

D:

Retest device-flow support, expiry and reauthorization rules when kiosk firmware or connected apps change. Validate PKCE enforcement and secure redirect handling in mobile connected-app reviews.

Certified Platform Identity and Access Management Architect Practice Tests