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 15

Question 0140 — Identity Management Concepts

At fictional Lighthouse Nonprofit 14B, the team managing global identity policy reports: An architecture team plans a single sign-out button that claims to terminate all browser and API sessions, although its apps use separate session mechanisms. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Reconcile identity-store joiner and leaver events with Salesforce account creation and deactivation records.
  2. Test federation mappings with alias, rename and duplicate-name cases before production rollouts.
  3. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.
  4. Test logout and revocation for each session/token type on a recurring security control review.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Test logout and revocation for each session/token type on a recurring security control review. This recurring control addresses the observed problem: An architecture team plans a single sign-out button that claims to terminate all browser and API sessions, although its apps use separate session mechanisms. The measurable check is: Prove browser logout and API token state individually across each connected app without implying universal session invalidation.

Incorrect Answers

A:

Reconcile identity-store joiner and leaver events with Salesforce account creation and deactivation records. Test logout and revocation for each session/token type on a recurring security control review.

B:

Test federation mappings with alias, rename and duplicate-name cases before production rollouts. Test logout and revocation for each session/token type on a recurring security control review.

C:

Review token lifetimes, revocation propagation and incident runbooks across all connected applications. Test logout and revocation for each session/token type on a recurring security control review.

Question 0141 — Accepting Third-Party Identity in Salesforce

At fictional Bluebrook Agriculture 15A, the team managing external identity provisioning reports: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.
  2. Validate the permitted SAML landing/start destination and configure only approved return destinations with correct encoding.
  3. Select an identity lifecycle integration that addresses pre-provisioning, updates, termination and first-login behavior rather than treating JIT as full lifecycle sync.
  4. Update only approved OIDC issuer metadata and key discovery configuration after verifying the new tenant's subject mapping and trust.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes. Replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

Incorrect Answers

B:

Validate the permitted SAML landing/start destination and configure only approved return destinations with correct encoding. The needed correction is to configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.

C:

Select an identity lifecycle integration that addresses pre-provisioning, updates, termination and first-login behavior rather than treating JIT as full lifecycle sync. The needed correction is to configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.

D:

Update only approved OIDC issuer metadata and key discovery configuration after verifying the new tenant's subject mapping and trust. The needed correction is to configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.

Question 0142 — Accepting Third-Party Identity in Salesforce

At fictional Bluebrook Agriculture 15A, the team managing external identity provisioning reports: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Compare certificate fingerprints, test a new assertion after rotation and confirm the retired signature is no longer accepted.
  2. Replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.
  3. Test representative employee and partner cohorts and confirm each reaches only their approved provider without cross-domain leakage.
  4. Complete separate provider tests showing distinct issuers remain separated unless an approved account-link step succeeds.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user. The corresponding correction is to configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.

Incorrect Answers

A:

Compare certificate fingerprints, test a new assertion after rotation and confirm the retired signature is no longer accepted. The useful check here is whether replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

C:

Test representative employee and partner cohorts and confirm each reaches only their approved provider without cross-domain leakage. The useful check here is whether replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

D:

Complete separate provider tests showing distinct issuers remain separated unless an approved account-link step succeeds. The useful check here is whether replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

Question 0143 — Accepting Third-Party Identity in Salesforce

At fictional Bluebrook Agriculture 15A, the team managing external identity provisioning reports: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Reliance on federated authentication requires synchronized key lifecycle across issuer and service provider.
  2. SAML destination and audience validation must be environment-specific, not just signature-correct.
  3. Salesforce must verify a trusted external issuer before accepting a third-party authentication assertion.
  4. Trust relationships require least privilege and lifecycle management as rigorously as user permissions.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Salesforce must verify a trusted external issuer before accepting a third-party authentication assertion. Replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

Incorrect Answers

A:

Reliance on federated authentication requires synchronized key lifecycle across issuer and service provider. Salesforce must verify a trusted external issuer before accepting a third-party authentication assertion.

B:

SAML destination and audience validation must be environment-specific, not just signature-correct. Salesforce must verify a trusted external issuer before accepting a third-party authentication assertion.

D:

Trust relationships require least privilege and lifecycle management as rigorously as user permissions. Salesforce must verify a trusted external issuer before accepting a third-party authentication assertion.

Question 0144 — Accepting Third-Party Identity in Salesforce

At fictional Bluebrook Agriculture 15A, the team managing external identity provisioning reports: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Automatic account reactivation can undo administrative security decisions during identity federation.
  2. Unreviewed social account linking can grant one provider access to another user's records.
  3. Domain or environment mismatch causes user lockouts and potential assertion-routing confusion.
  4. Disabling signature validation to work around onboarding would open an untrusted assertion acceptance path.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Disabling signature validation to work around onboarding would open an untrusted assertion acceptance path. Configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.

Incorrect Answers

A:

Automatic account reactivation can undo administrative security decisions during identity federation. Disabling signature validation to work around onboarding would open an untrusted assertion acceptance path.

B:

Unreviewed social account linking can grant one provider access to another user's records. Disabling signature validation to work around onboarding would open an untrusted assertion acceptance path.

C:

Domain or environment mismatch causes user lockouts and potential assertion-routing confusion. Disabling signature validation to work around onboarding would open an untrusted assertion acceptance path.

Question 0145 — Accepting Third-Party Identity in Salesforce

At fictional Bluebrook Agriculture 15A, the team managing external identity provisioning reports: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. 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. Revalidate provider-routing rules after subsidiary and domain changes.
  3. Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance.
  4. Perform periodic issuer certificate and cohort authorization reviews for every Salesforce federation connection.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Schedule certificate metadata audits and explicit rotation tests for each external identity provider. This recurring control addresses the observed problem: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. The measurable check is: Replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

Incorrect Answers

B:

Revalidate provider-routing rules after subsidiary and domain changes. Schedule certificate metadata audits and explicit rotation tests for each external identity provider.

C:

Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance. Schedule certificate metadata audits and explicit rotation tests for each external identity provider.

D:

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

Question 0146 — Accepting Third-Party Identity in Salesforce

At fictional Sagebridge Manufacturing 15B, the team managing third-party IdP onboarding reports: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Coordinate the IdP certificate rollover with Salesforce SP trust and validate fresh login sessions rather than relying on existing browser cookies.
  2. Configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.
  3. Update the external IdP service-provider configuration to the supported current Salesforce ACS, entity identifier and production My Domain.
  4. Maintain an explicit, owner-approved allowlist of IdP entity IDs, keys and permitted user cohorts, and retire unsupported federation relationships.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes. Replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

Incorrect Answers

A:

Coordinate the IdP certificate rollover with Salesforce SP trust and validate fresh login sessions rather than relying on existing browser cookies. The needed correction is to configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.

C:

Update the external IdP service-provider configuration to the supported current Salesforce ACS, entity identifier and production My Domain. The needed correction is to configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.

D:

Maintain an explicit, owner-approved allowlist of IdP entity IDs, keys and permitted user cohorts, and retire unsupported federation relationships. The needed correction is to configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.

Question 0147 — Accepting Third-Party Identity in Salesforce

At fictional Sagebridge Manufacturing 15B, the team managing third-party IdP onboarding reports: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.
  2. Complete separate provider tests showing distinct issuers remain separated unless an approved account-link step succeeds.
  3. Replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.
  4. Compare signed assertion recipient and issuer against the production service metadata and verify old sandbox recipient attempts fail.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user. The corresponding correction is to configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.

Incorrect Answers

A:

Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal. The useful check here is whether replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

B:

Complete separate provider tests showing distinct issuers remain separated unless an approved account-link step succeeds. The useful check here is whether replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

D:

Compare signed assertion recipient and issuer against the production service metadata and verify old sandbox recipient attempts fail. The useful check here is whether replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

Question 0148 — Accepting Third-Party Identity in Salesforce

At fictional Sagebridge Manufacturing 15B, the team managing third-party IdP onboarding reports: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. Which security architecture principle most directly explains the remediation needed for these facts?

  1. IdP routing is an access-control design decision when multiple identity realms share one service.
  2. OIDC relying parties must bind issuer and audience precisely to their trusted identity realm.
  3. Trust relationships require least privilege and lifecycle management as rigorously as user permissions.
  4. Salesforce must verify a trusted external issuer before accepting a third-party authentication assertion.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Salesforce must verify a trusted external issuer before accepting a third-party authentication assertion. Replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

Incorrect Answers

A:

IdP routing is an access-control design decision when multiple identity realms share one service. Salesforce must verify a trusted external issuer before accepting a third-party authentication assertion.

B:

OIDC relying parties must bind issuer and audience precisely to their trusted identity realm. Salesforce must verify a trusted external issuer before accepting a third-party authentication assertion.

C:

Trust relationships require least privilege and lifecycle management as rigorously as user permissions. Salesforce must verify a trusted external issuer before accepting a third-party authentication assertion.

Question 0149 — Accepting Third-Party Identity in Salesforce

At fictional Sagebridge Manufacturing 15B, the team managing third-party IdP onboarding reports: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Disabling signature validation to work around onboarding would open an untrusted assertion acceptance path.
  2. First-login-only creation can leave stale accounts and entitlements after a partner separation.
  3. Accepting unexpected issuers can permit token substitution while stale metadata blocks legitimate users.
  4. Domain or environment mismatch causes user lockouts and potential assertion-routing confusion.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Disabling signature validation to work around onboarding would open an untrusted assertion acceptance path. Configure Salesforce as the SAML service provider with the IdP's trusted signing certificate and verify all mandatory assertion attributes.

Incorrect Answers

B:

First-login-only creation can leave stale accounts and entitlements after a partner separation. Disabling signature validation to work around onboarding would open an untrusted assertion acceptance path.

C:

Accepting unexpected issuers can permit token substitution while stale metadata blocks legitimate users. Disabling signature validation to work around onboarding would open an untrusted assertion acceptance path.

D:

Domain or environment mismatch causes user lockouts and potential assertion-routing confusion. Disabling signature validation to work around onboarding would open an untrusted assertion acceptance path.

Question 0150 — Accepting Third-Party Identity in Salesforce

At fictional Sagebridge Manufacturing 15B, the team managing third-party IdP onboarding reports: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Test duplicate-address and provider-switch cases in every self-registration or social-login change.
  2. Schedule certificate metadata audits and explicit rotation tests for each external identity provider.
  3. Monitor creation errors, duplicate identities, and provisioning-role grants during partner growth.
  4. Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Schedule certificate metadata audits and explicit rotation tests for each external identity provider. This recurring control addresses the observed problem: A new workforce IdP signs Salesforce SAML assertions with an unregistered certificate, causing Salesforce to reject the login even though the email exists. The measurable check is: Replay an authorized test login and show signature validation succeeds only with the approved IdP key and mapped user.

Incorrect Answers

A:

Test duplicate-address and provider-switch cases in every self-registration or social-login change. Schedule certificate metadata audits and explicit rotation tests for each external identity provider.

C:

Monitor creation errors, duplicate identities, and provisioning-role grants during partner growth. Schedule certificate metadata audits and explicit rotation tests for each external identity provider.

D:

Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance. Schedule certificate metadata audits and explicit rotation tests for each external identity provider.

Certified Platform Identity and Access Management Architect Practice Tests