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 32

Question 0310 — Accepting Third-Party Identity in Salesforce

At fictional Hollowbrook Logistics 31B, the team managing Experience Cloud customer authentication reports: A large enterprise trusts assertions from several external IdPs without a documented list of approved issuer/entity IDs, allowing an obsolete federation connection to persist. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Schedule certificate metadata audits and explicit rotation tests for each external identity provider.
  2. Perform periodic issuer certificate and cohort authorization reviews for every Salesforce federation connection.
  3. Test duplicate-address and provider-switch cases in every self-registration or social-login change.
  4. Retest provider subject persistence and identity-link authorization after social-login connector changes.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Perform periodic issuer certificate and cohort authorization reviews for every Salesforce federation connection. This recurring control addresses the observed problem: A large enterprise trusts assertions from several external IdPs without a documented list of approved issuer/entity IDs, allowing an obsolete federation connection to persist. The measurable check is: Reconcile current Salesforce SSO configurations to the signed issuer inventory and show a retired IdP is rejected.

Incorrect Answers

A:

Schedule certificate metadata audits and explicit rotation tests for each external identity provider. Perform periodic issuer certificate and cohort authorization reviews for every Salesforce federation connection.

C:

Test duplicate-address and provider-switch cases in every self-registration or social-login change. Perform periodic issuer certificate and cohort authorization reviews for every Salesforce federation connection.

D:

Retest provider subject persistence and identity-link authorization after social-login connector changes. Perform periodic issuer certificate and cohort authorization reviews for every Salesforce federation connection.

Question 0311 — Salesforce as an Identity Provider

At fictional Silver Orchard Care 32A, the team managing relying application federation 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 authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model.
  2. Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements.
  3. Configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.
  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

C:

Configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials. Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

Incorrect Answers

A:

Select a supported server-to-server credential flow appropriate to the connected app and integration-user entitlement model. The needed correction is to configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.

B:

Assess a supported device authorization flow and confirm product support, consent, token lifetime and device-session revocation requirements. The needed correction is to configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.

D:

Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment. The needed correction is to configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.

Question 0312 — Salesforce as an Identity Provider

At fictional Silver Orchard Care 32A, the team managing relying application federation 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 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. Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations.
  4. Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient. The corresponding correction is to configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.

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 complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

B:

Demonstrate an unattended token grant under approved integration identity with no personal password and auditable access scope. The useful check here is whether complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

C:

Verify a token can read the approved identity fields but cannot invoke unrelated administrative operations. The useful check here is whether complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

Question 0313 — Salesforce as an Identity Provider

At fictional Silver Orchard Care 32A, the team managing relying application federation 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 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. Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate.
  3. OAuth scope and local user permissions both constrain what a delegated token may do.
  4. API authentication should be abstracted behind managed credentials with explicit principal authorization.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications. Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

Incorrect Answers

B:

Public clients cannot reliably protect static client secrets, so proof-of-possession code exchange is appropriate. Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications.

C:

OAuth scope and local user permissions both constrain what a delegated token may do. Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications.

D:

API authentication should be abstracted behind managed credentials with explicit principal authorization. Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications.

Question 0314 — Salesforce as an Identity Provider

At fictional Silver Orchard Care 32A, the team managing relying application federation 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. 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. Password replication multiplies credential exposure and obscures authoritative identity governance.
  3. One compromised broad connected-app grant can expose multiple unrelated services and datasets.
  4. Capturing credentials on untrusted shared devices enables theft and residual sessions.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Password replication multiplies credential exposure and obscures authoritative identity governance. Configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.

Incorrect Answers

A:

Extracted secrets and unbound codes create credential and authorization-code interception risks. Password replication multiplies credential exposure and obscures authoritative identity governance.

C:

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

D:

Capturing credentials on untrusted shared devices enables theft and residual sessions. Password replication multiplies credential exposure and obscures authoritative identity governance.

Question 0315 — Salesforce as an Identity Provider

At fictional Silver Orchard Care 32A, the team managing relying application federation 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. Rotate integration credentials and review non-interactive principal scope during service ownership changes.
  2. Audit high-risk refresh grants and ensure leaver runbooks cover each connected app.
  3. Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis.
  4. Periodically test redirect URI matching and review changes to connected-app callback lists.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

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:

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

B:

Audit high-risk refresh grants and ensure leaver runbooks cover each connected app. Review IdP service-provider metadata, assertion audience and certificate rollover on a scheduled basis.

D:

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.

Question 0316 — 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 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. Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior.
  3. Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment.
  4. Configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials. Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

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 configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.

B:

Choose narrowly required connected-app scopes and enforce matching permission grants and reviewable consent behavior. The needed correction is to configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.

C:

Prefer a supported External Credential and Named Credential design with separately governed principals, auth parameters and permission assignment. The needed correction is to configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.

Question 0317 — 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 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. Inspect a mobile test authorization exchange that uses a verifier/challenge and rejects a substituted code without the verifier.
  3. Review individual connected-app grants to show each has unique ownership, scope and revocation controls.
  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

A:

Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient. The corresponding correction is to configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.

Incorrect Answers

B:

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 complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

C:

Review individual connected-app grants to show each has unique ownership, scope and revocation controls. The useful check here is whether complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

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 complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

Question 0318 — 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 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. Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications.
  3. OAuth grants and application sessions require explicit revocation semantics separate from browser login state.
  4. Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications. Complete an SP-initiated test showing valid Salesforce-issued assertions accepted only by the configured partner recipient.

Incorrect Answers

A:

Automated workload credentials should be independent of human interactive accounts and enforce least privilege. Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications.

C:

OAuth grants and application sessions require explicit revocation semantics separate from browser login state. Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications.

D:

Authorization-code delivery relies on precise callback allowlisting to prevent code exfiltration. Federation lets a trusted identity provider authenticate principals without sharing their passwords with relying applications.

Question 0319 — 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. 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. Capturing credentials on untrusted shared devices enables theft and residual sessions.
  3. Password replication multiplies credential exposure and obscures authoritative identity governance.
  4. Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Password replication multiplies credential exposure and obscures authoritative identity governance. Configure Salesforce as the approved identity provider and establish signed SAML trust with the partner service provider without exporting credentials.

Incorrect Answers

A:

Reusing an employee password creates outages and untraceable automation when employment status changes. Password replication multiplies credential exposure and obscures authoritative identity governance.

B:

Capturing credentials on untrusted shared devices enables theft and residual sessions. Password replication multiplies credential exposure and obscures authoritative identity governance.

D:

Embedded reusable credentials cause leakage, difficult rotation and hidden shared privileges. Password replication multiplies credential exposure and obscures authoritative identity governance.

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.

Certified Platform Identity and Access Management Architect Practice Tests