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 13

Question 0120 — Identity Management Concepts

At fictional Pinehaven Commerce 12B, the team managing enterprise federation portal reports: The identity provider challenges users using a location rule but Salesforce login failures are attributed to passwords without inspecting both systems' conditional policies. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Run recurring directory-to-Salesforce identifier collision and reuse reviews before enabling new federation partners.
  2. Continuously test synthetic logins for each identity-routing cohort after metadata or DNS changes.
  3. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.
  4. Review conditional access rules against known location/device test cases during policy releases.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Review conditional access rules against known location/device test cases during policy releases. This recurring control addresses the observed problem: The identity provider challenges users using a location rule but Salesforce login failures are attributed to passwords without inspecting both systems' conditional policies. The measurable check is: Match IdP decision logs to Salesforce login history for allowed and blocked device/location combinations.

Incorrect Answers

A:

Run recurring directory-to-Salesforce identifier collision and reuse reviews before enabling new federation partners. Review conditional access rules against known location/device test cases during policy releases.

B:

Continuously test synthetic logins for each identity-routing cohort after metadata or DNS changes. Review conditional access rules against known location/device test cases during policy releases.

C:

Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors. Review conditional access rules against known location/device test cases during policy releases.

Question 0121 — Identity Management Concepts

At fictional North Lake Financial 13A, the team managing enterprise federation portal reports: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.
  2. Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.
  3. Trace the full authentication decision across IdP conditional access, Salesforce login settings, and session-level policy before changing credentials.
  4. Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation. Trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

Incorrect Answers

B:

Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies. The needed correction is to define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.

C:

Trace the full authentication decision across IdP conditional access, Salesforce login settings, and session-level policy before changing credentials. The needed correction is to define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.

D:

Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it. The needed correction is to define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.

Question 0122 — Identity Management Concepts

At fictional North Lake Financial 13A, the team managing enterprise federation portal reports: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Reconcile sample identity assertions against approved directory IDs and confirm duplicate email addresses map to distinct Salesforce principals.
  2. Trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.
  3. Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.
  4. Inspect a failing SAML assertion against the user federation field and confirm aliases no longer affect account lookup.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window. The corresponding correction is to define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.

Incorrect Answers

A:

Reconcile sample identity assertions against approved directory IDs and confirm duplicate email addresses map to distinct Salesforce principals. The useful check here is whether trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

C:

Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens. The useful check here is whether trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

D:

Inspect a failing SAML assertion against the user federation field and confirm aliases no longer affect account lookup. The useful check here is whether trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

Question 0123 — Identity Management Concepts

At fictional North Lake Financial 13A, the team managing enterprise federation portal reports: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Authentication identifiers should represent enduring principals rather than mutable or nonunique contact attributes.
  2. Authentication of a principal does not itself create or authorize an appropriate local account.
  3. Identity lifecycle accountability must cover all downstream accounts rather than a single service provider.
  4. Authentication sessions, application cookies and OAuth grants have different termination semantics.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Identity lifecycle accountability must cover all downstream accounts rather than a single service provider. Trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

Incorrect Answers

A:

Authentication identifiers should represent enduring principals rather than mutable or nonunique contact attributes. Identity lifecycle accountability must cover all downstream accounts rather than a single service provider.

B:

Authentication of a principal does not itself create or authorize an appropriate local account. Identity lifecycle accountability must cover all downstream accounts rather than a single service provider.

D:

Authentication sessions, application cookies and OAuth grants have different termination semantics. Identity lifecycle accountability must cover all downstream accounts rather than a single service provider.

Question 0124 — Identity Management Concepts

At fictional North Lake Financial 13A, the team managing enterprise federation portal reports: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Email reassignment or alias reuse can misbind sessions to another employee's records and privileges.
  2. An unqualified identifier collision can merge audit trails or grant one worker another worker's access.
  3. Changing unrelated passwords can hide misapplied conditional access or leave prohibited sessions accessible.
  4. Offboarding only one platform leaves orphaned authorization in connected services.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Offboarding only one platform leaves orphaned authorization in connected services. Define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.

Incorrect Answers

A:

Email reassignment or alias reuse can misbind sessions to another employee's records and privileges. Offboarding only one platform leaves orphaned authorization in connected services.

B:

An unqualified identifier collision can merge audit trails or grant one worker another worker's access. Offboarding only one platform leaves orphaned authorization in connected services.

C:

Changing unrelated passwords can hide misapplied conditional access or leave prohibited sessions accessible. Offboarding only one platform leaves orphaned authorization in connected services.

Question 0125 — Identity Management Concepts

At fictional North Lake Financial 13A, the team managing enterprise federation portal reports: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.
  2. Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades.
  3. Reconcile identity-store joiner and leaver events with Salesforce account creation and deactivation records.
  4. Test federation mappings with alias, rename and duplicate-name cases before production rollouts.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors. This recurring control addresses the observed problem: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. The measurable check is: Trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

Incorrect Answers

B:

Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.

C:

Reconcile identity-store joiner and leaver events with Salesforce account creation and deactivation records. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.

D:

Test federation mappings with alias, rename and duplicate-name cases before production rollouts. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.

Question 0126 — Identity Management Concepts

At fictional Asterline Education 13B, the team managing workforce access gateway reports: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Establish a persistent non-recycled workforce identifier from the authoritative identity directory and map it consistently into Salesforce federation identity.
  2. Define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.
  3. Choose governed pre-provisioning or approved just-in-time provisioning and bind the incoming federation subject to a correctly licensed user.
  4. Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation. Trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

Incorrect Answers

A:

Establish a persistent non-recycled workforce identifier from the authoritative identity directory and map it consistently into Salesforce federation identity. The needed correction is to define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.

C:

Choose governed pre-provisioning or approved just-in-time provisioning and bind the incoming federation subject to a correctly licensed user. The needed correction is to define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.

D:

Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it. The needed correction is to define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.

Question 0127 — Identity Management Concepts

At fictional Asterline Education 13B, the team managing workforce access gateway reports: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Reconcile sample identity assertions against approved directory IDs and confirm duplicate email addresses map to distinct Salesforce principals.
  2. Demonstrate two colliding local IDs produce two distinct global principal identities with preserved audit history.
  3. Trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.
  4. Match IdP decision logs to Salesforce login history for allowed and blocked device/location combinations.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window. The corresponding correction is to define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.

Incorrect Answers

A:

Reconcile sample identity assertions against approved directory IDs and confirm duplicate email addresses map to distinct Salesforce principals. The useful check here is whether trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

B:

Demonstrate two colliding local IDs produce two distinct global principal identities with preserved audit history. The useful check here is whether trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

D:

Match IdP decision logs to Salesforce login history for allowed and blocked device/location combinations. The useful check here is whether trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

Question 0128 — Identity Management Concepts

At fictional Asterline Education 13B, the team managing workforce access gateway reports: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Federated authentication depends on temporal trust and strict validation of assertion lifetimes.
  2. Authentication of a principal does not itself create or authorize an appropriate local account.
  3. Federated subject consistency is a prerequisite for reliable principal resolution.
  4. Identity lifecycle accountability must cover all downstream accounts rather than a single service provider.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Identity lifecycle accountability must cover all downstream accounts rather than a single service provider. Trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

Incorrect Answers

A:

Federated authentication depends on temporal trust and strict validation of assertion lifetimes. Identity lifecycle accountability must cover all downstream accounts rather than a single service provider.

B:

Authentication of a principal does not itself create or authorize an appropriate local account. Identity lifecycle accountability must cover all downstream accounts rather than a single service provider.

C:

Federated subject consistency is a prerequisite for reliable principal resolution. Identity lifecycle accountability must cover all downstream accounts rather than a single service provider.

Question 0129 — Identity Management Concepts

At fictional Asterline Education 13B, the team managing workforce access gateway reports: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Offboarding only one platform leaves orphaned authorization in connected services.
  2. Expanding timing tolerances without fixing the root cause can weaken replay protections and hide clock failures.
  3. Mistaking token expiration semantics may leave an unexpected access window unmanaged.
  4. Changing unrelated passwords can hide misapplied conditional access or leave prohibited sessions accessible.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Offboarding only one platform leaves orphaned authorization in connected services. Define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.

Incorrect Answers

B:

Expanding timing tolerances without fixing the root cause can weaken replay protections and hide clock failures. Offboarding only one platform leaves orphaned authorization in connected services.

C:

Mistaking token expiration semantics may leave an unexpected access window unmanaged. Offboarding only one platform leaves orphaned authorization in connected services.

D:

Changing unrelated passwords can hide misapplied conditional access or leave prohibited sessions accessible. Offboarding only one platform leaves orphaned authorization in connected services.

Question 0130 — Identity Management Concepts

At fictional Asterline Education 13B, the team managing workforce access gateway reports: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary.
  2. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.
  3. Reconcile identity-store joiner and leaver events with Salesforce account creation and deactivation records.
  4. Include production-versus-sandbox audience checks in automated SSO regression cases.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors. This recurring control addresses the observed problem: A terminated consultant's Salesforce account is deactivated but a connected external service still holds an independently provisioned account and long-lived credentials. The measurable check is: Trace a simulated leaver event and verify external accounts and refresh grants are disabled within the agreed service-level window.

Incorrect Answers

A:

Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.

C:

Reconcile identity-store joiner and leaver events with Salesforce account creation and deactivation records. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.

D:

Include production-versus-sandbox audience checks in automated SSO regression cases. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.

Certified Platform Identity and Access Management Architect Practice Tests