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 14

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.

Question 0131 — Identity Management Concepts

At fictional Oakridge Hospitality 14A, the team managing workforce access gateway 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 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. Correct the assertion AudienceRestriction and recipient values to the designated Salesforce environment and validate endpoint isolation.
  3. Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.
  4. Define a cross-system deprovisioning contract covering directory, Salesforce, and downstream relying applications, including token revocation.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it. Prove browser logout and API token state individually across each connected app without implying universal session invalidation.

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 document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

B:

Correct the assertion AudienceRestriction and recipient values to the designated Salesforce environment and validate endpoint isolation. The needed correction is to document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

D:

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

Question 0132 — Identity Management Concepts

At fictional Oakridge Hospitality 14A, the team managing workforce access gateway 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 independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Compare failed assertion timestamps with trusted UTC logs and complete a successful time-bounded end-to-end SSO test.
  2. Verify both parties' metadata thumbprints and show successful SSO with the active key after retiring the previous one.
  3. Match IdP decision logs to Salesforce login history for allowed and blocked device/location combinations.
  4. Prove browser logout and API token state individually across each connected app without implying universal session invalidation.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Prove browser logout and API token state individually across each connected app without implying universal session invalidation. The corresponding correction is to document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

Incorrect Answers

A:

Compare failed assertion timestamps with trusted UTC logs and complete a successful time-bounded end-to-end SSO test. The useful check here is whether prove browser logout and API token state individually across each connected app without implying universal session invalidation.

B:

Verify both parties' metadata thumbprints and show successful SSO with the active key after retiring the previous one. The useful check here is whether prove browser logout and API token state individually across each connected app without implying universal session invalidation.

C:

Match IdP decision logs to Salesforce login history for allowed and blocked device/location combinations. The useful check here is whether prove browser logout and API token state individually across each connected app without implying universal session invalidation.

Question 0133 — Identity Management Concepts

At fictional Oakridge Hospitality 14A, the team managing workforce access gateway 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 security architecture principle most directly explains the remediation needed for these facts?

  1. Authentication sessions, application cookies and OAuth grants have different termination semantics.
  2. Federated authentication depends on temporal trust and strict validation of assertion lifetimes.
  3. Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens.
  4. Principal uniqueness must be preserved across organizational boundaries and mergers.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Authentication sessions, application cookies and OAuth grants have different termination semantics. Prove browser logout and API token state individually across each connected app without implying universal session invalidation.

Incorrect Answers

B:

Federated authentication depends on temporal trust and strict validation of assertion lifetimes. Authentication sessions, application cookies and OAuth grants have different termination semantics.

C:

Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens. Authentication sessions, application cookies and OAuth grants have different termination semantics.

D:

Principal uniqueness must be preserved across organizational boundaries and mergers. Authentication sessions, application cookies and OAuth grants have different termination semantics.

Question 0134 — Identity Management Concepts

At fictional Oakridge Hospitality 14A, the team managing workforce access gateway 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. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Confusing token purposes allows token substitution and unsupported login conclusions.
  2. Users may believe all access ended while independently held sessions remain valid.
  3. Successful IdP authentication without lifecycle controls causes failed entry or overbroad default access.
  4. Stale entitlements allow previously authorized access to persist beyond a business change.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Users may believe all access ended while independently held sessions remain valid. Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

Incorrect Answers

A:

Confusing token purposes allows token substitution and unsupported login conclusions. Users may believe all access ended while independently held sessions remain valid.

C:

Successful IdP authentication without lifecycle controls causes failed entry or overbroad default access. Users may believe all access ended while independently held sessions remain valid.

D:

Stale entitlements allow previously authorized access to persist beyond a business change. Users may believe all access ended while independently held sessions remain valid.

Question 0135 — Identity Management Concepts

At fictional Oakridge Hospitality 14A, the team managing workforce access gateway 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. Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary.
  2. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.
  3. Test logout and revocation for each session/token type on a recurring security control review.
  4. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

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:

Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary. Test logout and revocation for each session/token type on a recurring security control review.

B:

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.

D:

Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors. Test logout and revocation for each session/token type on a recurring security control review.

Question 0136 — 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 authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Confirm IdP and Salesforce clock synchronization and review assertion NotBefore and NotOnOrAfter skew without indiscriminately increasing allowed session time.
  2. Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.
  3. Namespace workforce subjects by authoritative directory/tenant and maintain immutable crosswalk mappings instead of merging unrelated identifiers.
  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

D:

Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it. Prove browser logout and API token state individually across each connected app without implying universal session invalidation.

Incorrect Answers

A:

Confirm IdP and Salesforce clock synchronization and review assertion NotBefore and NotOnOrAfter skew without indiscriminately increasing allowed session time. The needed correction is to document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

B:

Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies. The needed correction is to document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

C:

Namespace workforce subjects by authoritative directory/tenant and maintain immutable crosswalk mappings instead of merging unrelated identifiers. The needed correction is to document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

Question 0137 — 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 independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Prove browser logout and API token state individually across each connected app without implying universal session invalidation.
  2. Demonstrate that the portal checks ID-token issuer, audience, signature and nonce while API calls use audience-scoped access tokens.
  3. Confirm a new authorized employee receives exactly one correctly mapped user and a separated employee is denied.
  4. Show an approved role change removes former permission sets and applies only the authorized current access.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Prove browser logout and API token state individually across each connected app without implying universal session invalidation. The corresponding correction is to document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

Incorrect Answers

B:

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 prove browser logout and API token state individually across each connected app without implying universal session invalidation.

C:

Confirm a new authorized employee receives exactly one correctly mapped user and a separated employee is denied. The useful check here is whether prove browser logout and API token state individually across each connected app without implying universal session invalidation.

D:

Show an approved role change removes former permission sets and applies only the authorized current access. The useful check here is whether prove browser logout and API token state individually across each connected app without implying universal session invalidation.

Question 0138 — 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 security architecture principle most directly explains the remediation needed for these facts?

  1. OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity.
  2. Authentication sessions, application cookies and OAuth grants have different termination semantics.
  3. Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens.
  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

B:

Authentication sessions, application cookies and OAuth grants have different termination semantics. Prove browser logout and API token state individually across each connected app without implying universal session invalidation.

Incorrect Answers

A:

OAuth and OpenID Connect provide different guarantees for resource authorization and authenticated user identity. Authentication sessions, application cookies and OAuth grants have different termination semantics.

C:

Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens. Authentication sessions, application cookies and OAuth grants have different termination semantics.

D:

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

Question 0139 — 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. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. An uncoordinated certificate cutover blocks users and can tempt teams to disable signature verification.
  2. Ambiguous NameID mapping can cause account mismatches and inconsistent access between users.
  3. Users may believe all access ended while independently held sessions remain valid.
  4. Changing unrelated passwords can hide misapplied conditional access or leave prohibited sessions accessible.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Users may believe all access ended while independently held sessions remain valid. Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.

Incorrect Answers

A:

An uncoordinated certificate cutover blocks users and can tempt teams to disable signature verification. Users may believe all access ended while independently held sessions remain valid.

B:

Ambiguous NameID mapping can cause account mismatches and inconsistent access between users. Users may believe all access ended while independently held sessions remain valid.

D:

Changing unrelated passwords can hide misapplied conditional access or leave prohibited sessions accessible. Users may believe all access ended while independently held sessions remain valid.

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.

Certified Platform Identity and Access Management Architect Practice Tests