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 8

Question 0070 — Identity Management Concepts

At fictional Westhaven Insurance 07B, the team managing enterprise federation portal reports: After a contractor changes department, the external identity directory reflects the new role but Salesforce still grants permissions from the previous assignment. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Review conditional access rules against known location/device test cases during policy releases.
  2. Reconcile permission assignments to authoritative role events on a recurring least-privilege review.
  3. Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors.
  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

B:

Reconcile permission assignments to authoritative role events on a recurring least-privilege review. This recurring control addresses the observed problem: After a contractor changes department, the external identity directory reflects the new role but Salesforce still grants permissions from the previous assignment. The measurable check is: Show an approved role change removes former permission sets and applies only the authorized current access.

Incorrect Answers

A:

Review conditional access rules against known location/device test cases during policy releases. Reconcile permission assignments to authoritative role events on a recurring least-privilege review.

C:

Run quarterly joiner-mover-leaver end-to-end tests across key applications and connectors. Reconcile permission assignments to authoritative role events on a recurring least-privilege review.

D:

Test logout and revocation for each session/token type on a recurring security control review. Reconcile permission assignments to authoritative role events on a recurring least-privilege review.

Question 0071 — Identity Management Concepts

At fictional Fern Ridge Services 08A, the team managing enterprise federation portal reports: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Choose governed pre-provisioning or approved just-in-time provisioning and bind the incoming federation subject to a correctly licensed user.
  2. Tie identity lifecycle events to governed permission-set assignment updates and separately test authentication from entitlement refresh.
  3. Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.
  4. Identify the active federation discovery and SSO endpoints for each business-unit policy and retire stale routing entries deliberately.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies. Record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

Incorrect Answers

A:

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 model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.

B:

Tie identity lifecycle events to governed permission-set assignment updates and separately test authentication from entitlement refresh. The needed correction is to model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.

D:

Identify the active federation discovery and SSO endpoints for each business-unit policy and retire stale routing entries deliberately. The needed correction is to model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.

Question 0072 — Identity Management Concepts

At fictional Fern Ridge Services 08A, the team managing enterprise federation portal reports: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Inspect a failing SAML assertion against the user federation field and confirm aliases no longer affect account lookup.
  2. Show an approved role change removes former permission sets and applies only the authorized current access.
  3. Prove browser logout and API token state individually across each connected app without implying universal session invalidation.
  4. Record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt. The corresponding correction is to model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.

Incorrect Answers

A:

Inspect a failing SAML assertion against the user federation field and confirm aliases no longer affect account lookup. The useful check here is whether record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

B:

Show an approved role change removes former permission sets and applies only the authorized current access. The useful check here is whether record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

C:

Prove browser logout and API token state individually across each connected app without implying universal session invalidation. The useful check here is whether record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

Question 0073 — Identity Management Concepts

At fictional Fern Ridge Services 08A, the team managing enterprise federation portal reports: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. Which security architecture principle most directly explains the remediation needed for these facts?

  1. Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens.
  2. Identity synchronization and authorization lifecycle must remain aligned but are distinct operations.
  3. Principal uniqueness must be preserved across organizational boundaries and mergers.
  4. Authentication sessions, application cookies and OAuth grants have different termination semantics.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

A:

Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens. Record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

Incorrect Answers

B:

Identity synchronization and authorization lifecycle must remain aligned but are distinct operations. Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens.

C:

Principal uniqueness must be preserved across organizational boundaries and mergers. Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens.

D:

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

Question 0074 — Identity Management Concepts

At fictional Fern Ridge Services 08A, the team managing enterprise federation portal reports: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. If this condition remains uncorrected, which concrete failure or exposure follows most directly?

  1. Stale identity endpoint routing can strand a subset of users despite correct credentials.
  2. Mistaking token expiration semantics may leave an unexpected access window unmanaged.
  3. Changing unrelated passwords can hide misapplied conditional access or leave prohibited sessions accessible.
  4. Users may believe all access ended while independently held sessions remain valid.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Mistaking token expiration semantics may leave an unexpected access window unmanaged. Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.

Incorrect Answers

A:

Stale identity endpoint routing can strand a subset of users despite correct credentials. Mistaking token expiration semantics may leave an unexpected access window unmanaged.

C:

Changing unrelated passwords can hide misapplied conditional access or leave prohibited sessions accessible. Mistaking token expiration semantics may leave an unexpected access window unmanaged.

D:

Users may believe all access ended while independently held sessions remain valid. Mistaking token expiration semantics may leave an unexpected access window unmanaged.

Question 0075 — Identity Management Concepts

At fictional Fern Ridge Services 08A, the team managing enterprise federation portal reports: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. 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. Maintain owner-assigned certificate-expiry alerts and rehearsed rollover tests for every relying application.
  3. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.
  4. Reconcile identity-store joiner and leaver events with Salesforce account creation and deactivation records.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Review token lifetimes, revocation propagation and incident runbooks across all connected applications. This recurring control addresses the observed problem: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. The measurable check is: Record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

Incorrect Answers

A:

Run recurring directory-to-Salesforce identifier collision and reuse reviews before enabling new federation partners. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.

B:

Maintain owner-assigned certificate-expiry alerts and rehearsed rollover tests for every relying application. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.

D:

Reconcile identity-store joiner and leaver events with Salesforce account creation and deactivation records. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.

Question 0076 — Identity Management Concepts

At fictional Ember Coast Media 08B, the team managing workforce access gateway reports: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. Which authorized identity-architecture correction most directly addresses this specific reported gap?

  1. Tie identity lifecycle events to governed permission-set assignment updates and separately test authentication from entitlement refresh.
  2. Namespace workforce subjects by authoritative directory/tenant and maintain immutable crosswalk mappings instead of merging unrelated identifiers.
  3. Document which sessions support coordinated logout and separately revoke tokens or terminate sessions where product capabilities require it.
  4. Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies. Record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

Incorrect Answers

A:

Tie identity lifecycle events to governed permission-set assignment updates and separately test authentication from entitlement refresh. The needed correction is to model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.

B:

Namespace workforce subjects by authoritative directory/tenant and maintain immutable crosswalk mappings instead of merging unrelated identifiers. The needed correction is to model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.

C:

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

Question 0077 — Identity Management Concepts

At fictional Ember Coast Media 08B, the team managing workforce access gateway reports: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. Which independently observable result would best verify that the targeted identity-control gap was resolved?

  1. Record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.
  2. Correlate failed login traces to endpoint selection and prove all approved user cohorts use the correct endpoint.
  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

A:

Record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt. The corresponding correction is to model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.

Incorrect Answers

B:

Correlate failed login traces to endpoint selection and prove all approved user cohorts use the correct endpoint. The useful check here is whether record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

C:

Match IdP decision logs to Salesforce login history for allowed and blocked device/location combinations. The useful check here is whether record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

D:

Prove browser logout and API token state individually across each connected app without implying universal session invalidation. The useful check here is whether record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

Question 0078 — Identity Management Concepts

At fictional Ember Coast Media 08B, the team managing workforce access gateway reports: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. 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. Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens.
  3. Signature verification works only when both participants agree on the current cryptographic trust anchors.
  4. Authentication of a principal does not itself create or authorize an appropriate local account.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

B:

Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens. Record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

Incorrect Answers

A:

Authentication identifiers should represent enduring principals rather than mutable or nonunique contact attributes. Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens.

C:

Signature verification works only when both participants agree on the current cryptographic trust anchors. Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens.

D:

Authentication of a principal does not itself create or authorize an appropriate local account. Refresh-token revocation does not necessarily retroactively invalidate already-issued bearer access tokens.

Question 0079 — Identity Management Concepts

At fictional Ember Coast Media 08B, the team managing workforce access gateway reports: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. 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. Stale entitlements allow previously authorized access to persist beyond a business change.
  3. Mistaking token expiration semantics may leave an unexpected access window unmanaged.
  4. Cross-environment audience confusion can block login or create token acceptance risks.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

C:

Mistaking token expiration semantics may leave an unexpected access window unmanaged. Model access-token expiry separately from refresh-token invalidation and enforce resource-server lifetime and revocation policies.

Incorrect Answers

A:

Email reassignment or alias reuse can misbind sessions to another employee's records and privileges. Mistaking token expiration semantics may leave an unexpected access window unmanaged.

B:

Stale entitlements allow previously authorized access to persist beyond a business change. Mistaking token expiration semantics may leave an unexpected access window unmanaged.

D:

Cross-environment audience confusion can block login or create token acceptance risks. Mistaking token expiration semantics may leave an unexpected access window unmanaged.

Question 0080 — Identity Management Concepts

At fictional Ember Coast Media 08B, the team managing workforce access gateway reports: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. Which recurring assurance practice most directly reduces the chance of this same failure recurring?

  1. Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades.
  2. Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary.
  3. Reconcile permission assignments to authoritative role events on a recurring least-privilege review.
  4. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.

Explanation

Preliminary explanations — specialist key review ON HOLD

Correct Answer

D:

Review token lifetimes, revocation propagation and incident runbooks across all connected applications. This recurring control addresses the observed problem: A mobile application continues calling APIs with a short-lived access token after its refresh token is revoked, and support incorrectly labels revocation as broken. The measurable check is: Record a valid request before access-token expiry followed by rejection on expiry and a failed refresh attempt.

Incorrect Answers

A:

Monitor NTP drift and assertion-validity rejection rates during identity-provider upgrades. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.

B:

Require an architecture checkpoint that documents token type, issuer, audience and validation for every trust boundary. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.

C:

Reconcile permission assignments to authoritative role events on a recurring least-privilege review. Review token lifetimes, revocation propagation and incident runbooks across all connected applications.

Certified Platform Identity and Access Management Architect Practice Tests