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 23

Question 0220 — Accepting Third-Party Identity in Salesforce

At fictional Pinehaven Commerce 22B, the team managing B2E federation integration reports: An external IdP rotates its SAML signing keys without coordinating Salesforce identity configuration, and some users can log in only through cached sessions. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Include suspended and terminated users in JIT handler negative testing.
  2. Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance.
  3. Check sandbox/production metadata independently after My Domain and domain-management changes.
  4. Maintain proactive signing-key expiry monitoring and cross-party change ownership.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Maintain proactive signing-key expiry monitoring and cross-party change ownership. This recurring control addresses the observed problem: An external IdP rotates its SAML signing keys without coordinating Salesforce identity configuration, and some users can log in only through cached sessions. The measurable check is: Compare certificate fingerprints, test a new assertion after rotation and confirm the retired signature is no longer accepted.

Incorrect Answers

A:

Include suspended and terminated users in JIT handler negative testing. Maintain proactive signing-key expiry monitoring and cross-party change ownership.

B:

Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance. Maintain proactive signing-key expiry monitoring and cross-party change ownership.

C:

Check sandbox/production metadata independently after My Domain and domain-management changes. Maintain proactive signing-key expiry monitoring and cross-party change ownership.

Question 0221 — Accepting Third-Party Identity in Salesforce

At fictional North Lake Financial 23A, the team managing B2E federation integration reports: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.
  2. Trace the complete SP-initiated SAML exchange and repair relay-state/redirect handling at the approved identity gateway.
  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:

Enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval. Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

Incorrect Answers

B:

Trace the complete SP-initiated SAML exchange and repair relay-state/redirect handling at the approved identity gateway. The needed correction is to enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.

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 enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.

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 enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.

Question 0222 — Accepting Third-Party Identity in Salesforce

At fictional North Lake Financial 23A, the team managing B2E federation integration reports: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Launch a test workflow from the IdP and demonstrate safe navigation to the intended authorized Salesforce resource.
  2. Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.
  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:

Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal. The corresponding correction is to enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.

Incorrect Answers

A:

Launch a test workflow from the IdP and demonstrate safe navigation to the intended authorized Salesforce resource. The useful check here is whether exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

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 exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

D:

Complete separate provider tests showing distinct issuers remain separated unless an approved account-link step succeeds. The useful check here is whether exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

Question 0223 — Accepting Third-Party Identity in Salesforce

At fictional North Lake Financial 23A, the team managing B2E federation integration reports: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Authentication destination routing must remain constrained to trusted application locations.
  2. SAML destination and audience validation must be environment-specific, not just signature-correct.
  3. Provisioning automation must respect lifecycle authority and explicit account-state controls.
  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:

Provisioning automation must respect lifecycle authority and explicit account-state controls. Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

Incorrect Answers

A:

Authentication destination routing must remain constrained to trusted application locations. Provisioning automation must respect lifecycle authority and explicit account-state controls.

B:

SAML destination and audience validation must be environment-specific, not just signature-correct. Provisioning automation must respect lifecycle authority and explicit account-state controls.

D:

Trust relationships require least privilege and lifecycle management as rigorously as user permissions. Provisioning automation must respect lifecycle authority and explicit account-state controls.

Question 0224 — Accepting Third-Party Identity in Salesforce

At fictional North Lake Financial 23A, the team managing B2E federation integration reports: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Uncoordinated key replacement causes new-login outages and pressure to weaken signature rules.
  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. Automatic account reactivation can undo administrative security decisions during identity federation.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Automatic account reactivation can undo administrative security decisions during identity federation. Enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.

Incorrect Answers

A:

Uncoordinated key replacement causes new-login outages and pressure to weaken signature rules. Automatic account reactivation can undo administrative security decisions during identity federation.

B:

Unreviewed social account linking can grant one provider access to another user's records. Automatic account reactivation can undo administrative security decisions during identity federation.

C:

Domain or environment mismatch causes user lockouts and potential assertion-routing confusion. Automatic account reactivation can undo administrative security decisions during identity federation.

Question 0225 — Accepting Third-Party Identity in Salesforce

At fictional North Lake Financial 23A, the team managing B2E federation integration reports: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Include suspended and terminated users in JIT handler negative testing.
  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:

Include suspended and terminated users in JIT handler negative testing. This recurring control addresses the observed problem: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. The measurable check is: Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

Incorrect Answers

B:

Revalidate provider-routing rules after subsidiary and domain changes. Include suspended and terminated users in JIT handler negative testing.

C:

Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance. Include suspended and terminated users in JIT handler negative testing.

D:

Perform periodic issuer certificate and cohort authorization reviews for every Salesforce federation connection. Include suspended and terminated users in JIT handler negative testing.

Question 0226 — Accepting Third-Party Identity in Salesforce

At fictional Asterline Education 23B, the team managing partner SSO registration reports: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Validate the permitted SAML landing/start destination and configure only approved return destinations with correct encoding.
  2. Enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.
  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:

Enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval. Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

Incorrect Answers

A:

Validate the permitted SAML landing/start destination and configure only approved return destinations with correct encoding. The needed correction is to enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.

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 enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.

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 enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.

Question 0227 — Accepting Third-Party Identity in Salesforce

At fictional Asterline Education 23B, the team managing partner SSO registration reports: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. 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. Complete separate provider tests showing distinct issuers remain separated unless an approved account-link step succeeds.
  3. Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.
  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:

Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal. The corresponding correction is to enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.

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 exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

B:

Complete separate provider tests showing distinct issuers remain separated unless an approved account-link step succeeds. The useful check here is whether exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

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 exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

Question 0228 — Accepting Third-Party Identity in Salesforce

At fictional Asterline Education 23B, the team managing partner SSO registration reports: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. 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. Provisioning automation must respect lifecycle authority and explicit account-state controls.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Provisioning automation must respect lifecycle authority and explicit account-state controls. Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

Incorrect Answers

A:

IdP routing is an access-control design decision when multiple identity realms share one service. Provisioning automation must respect lifecycle authority and explicit account-state controls.

B:

OIDC relying parties must bind issuer and audience precisely to their trusted identity realm. Provisioning automation must respect lifecycle authority and explicit account-state controls.

C:

Trust relationships require least privilege and lifecycle management as rigorously as user permissions. Provisioning automation must respect lifecycle authority and explicit account-state controls.

Question 0229 — Accepting Third-Party Identity in Salesforce

At fictional Asterline Education 23B, the team managing partner SSO registration reports: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. 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. 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:

Automatic account reactivation can undo administrative security decisions during identity federation. Enforce account-state policy in JIT provisioning so authentication cannot override administrative suspension without approval.

Incorrect Answers

B:

First-login-only creation can leave stale accounts and entitlements after a partner separation. Automatic account reactivation can undo administrative security decisions during identity federation.

C:

Accepting unexpected issuers can permit token substitution while stale metadata blocks legitimate users. Automatic account reactivation can undo administrative security decisions during identity federation.

D:

Domain or environment mismatch causes user lockouts and potential assertion-routing confusion. Automatic account reactivation can undo administrative security decisions during identity federation.

Question 0230 — Accepting Third-Party Identity in Salesforce

At fictional Asterline Education 23B, the team managing partner SSO registration reports: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. 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. Include suspended and terminated users in JIT handler negative testing.
  3. Test duplicate-address and provider-switch cases in every self-registration or social-login change.
  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:

Include suspended and terminated users in JIT handler negative testing. This recurring control addresses the observed problem: A third-party assertion tries to reactivate an intentionally suspended Salesforce user automatically through an over-permissive JIT provisioning handler. The measurable check is: Exercise a suspended-user SSO attempt and verify the Salesforce account remains inactive with a traceable refusal.

Incorrect Answers

A:

Schedule certificate metadata audits and explicit rotation tests for each external identity provider. Include suspended and terminated users in JIT handler negative testing.

C:

Test duplicate-address and provider-switch cases in every self-registration or social-login change. Include suspended and terminated users in JIT handler negative testing.

D:

Monitor issuer and JWKS metadata drift as part of OIDC tenant-change governance. Include suspended and terminated users in JIT handler negative testing.

Certified Platform Identity and Access Management Architect Practice Tests