mcAfee Secure Website
exam =5
exam =6

Exam Code: Certified Platform Identity and Access Management Architect

Exam Name: Certified Platform Identity and Access Management Architect

Certification Provider: Salesforce

Salesforce Certified Platform Identity and Access Management Architect Questions & Answers

Reliable & Actual Study Materials for Certified Platform Identity and Access Management Architect Exam Success

58 Questions & Answers with Testing Engine

"Certified Platform Identity and Access Management Architect: Certified Platform Identity and Access Management Architect" Testing Engine covers all the knowledge points of the real Salesforce Certified Platform Identity and Access Management Architect exam.

The latest actual Certified Platform Identity and Access Management Architect Questions & Answers from Pass4sure. Everything you need to prepare and get best score at Certified Platform Identity and Access Management Architect exam easily and quickly.

exam =7
Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Salesforce Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Was: $137.49
Now: $124.99

Salesforce Certified Platform Identity and Access Management Architect Practice Test 63

Question 620

A vendor offers an Experience Cloud external user license to internal salaried employees who need the complete CRM console. Best complete IAM decision record?

  1. Action: Plan migration in phases, including account matching, permissions, authentication and deprovisioning tests. Verification: Audit source deactivation time, Salesforce active flag, tokens and effective API access. Boundary: A cheaper external identity license is not interchangeable with every internal Salesforce license.
  2. Action: Define lifecycle observability and reconcile IAM evidence across directory, federation and Salesforce application layers. Verification: Check permitted user category, license feature matrix, linked contact model and data visibility. Boundary: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.
  3. Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Check permitted user category, license feature matrix, linked contact model and data visibility. Boundary: A cheaper external identity license is not interchangeable with every internal Salesforce license.
  4. Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Map identity source, federation roles, app audiences, license needs and lifecycle ownership. Boundary: Federation of authentication alone does not synchronize all employment lifecycle events.

Explanation

Correct Answer

C:

“Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Check permitted user category, license feature matrix, linked contact model and data visibility. Boundary: A cheaper external identity license is not interchangeable with every internal Salesforce license” addresses the access-design responsibilities in a vendor offers an Experience Cloud external user license to internal salaried employees who need the complete CRM console Test against check permitted user category, license feature matrix, linked contact model and data visibility; a cheaper external identity license is not interchangeable with every internal Salesforce license.

Incorrect Answers

A:

“Action: Plan migration in phases, including account matching, permissions, authentication and deprovisioning tests. Verification: Audit source deactivation time, Salesforce active flag, tokens and effective API access. Boundary: A cheaper external identity license is not interchangeable with every internal Salesforce license” may apply to a related identity task, but it does not establish check permitted user category, license feature matrix, linked contact model and data visibility for a vendor offers an Experience Cloud external user license to internal salaried employees who need the complete CRM console The controlling boundary is: A cheaper external identity license is not interchangeable with every internal Salesforce license.

B:

“Action: Define lifecycle observability and reconcile IAM evidence across directory, federation and Salesforce application layers. Verification: Check permitted user category, license feature matrix, linked contact model and data visibility. Boundary: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership” may apply to a related identity task, but it does not establish check permitted user category, license feature matrix, linked contact model and data visibility for a vendor offers an Experience Cloud external user license to internal salaried employees who need the complete CRM console The controlling boundary is: A cheaper external identity license is not interchangeable with every internal Salesforce license.

D:

“Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Map identity source, federation roles, app audiences, license needs and lifecycle ownership. Boundary: Federation of authentication alone does not synchronize all employment lifecycle events” may apply to a related identity task, but it does not establish check permitted user category, license feature matrix, linked contact model and data visibility for a vendor offers an Experience Cloud external user license to internal salaried employees who need the complete CRM console The controlling boundary is: A cheaper external identity license is not interchangeable with every internal Salesforce license.

Question 621

A partnership project compares lightweight external identity access with business-object-intensive portal needs. Best next IAM response?

  1. Plan migration in phases, including account matching, permissions, authentication and deprovisioning tests
  2. Publish an identity architecture responsibility matrix with accountable controls and escalation paths
  3. Define lifecycle observability and reconcile IAM evidence across directory, federation and Salesforce application layers
  4. Choose supported internal or external user licensing based on person population and required app capabilities

Explanation

Correct Answer

D:

“Choose supported internal or external user licensing based on person population and required app capabilities” addresses the access-design responsibilities in a partnership project compares lightweight external identity access with business-object-intensive portal needs Test against check permitted user category, license feature matrix, linked contact model and data visibility; a cheaper external identity license is not interchangeable with every internal Salesforce license.

Incorrect Answers

A:

“Plan migration in phases, including account matching, permissions, authentication and deprovisioning tests” may apply to a related identity task, but it does not establish check permitted user category, license feature matrix, linked contact model and data visibility for a partnership project compares lightweight external identity access with business-object-intensive portal needs The controlling boundary is: A cheaper external identity license is not interchangeable with every internal Salesforce license.

B:

“Publish an identity architecture responsibility matrix with accountable controls and escalation paths” may apply to a related identity task, but it does not establish check permitted user category, license feature matrix, linked contact model and data visibility for a partnership project compares lightweight external identity access with business-object-intensive portal needs The controlling boundary is: A cheaper external identity license is not interchangeable with every internal Salesforce license.

C:

“Define lifecycle observability and reconcile IAM evidence across directory, federation and Salesforce application layers” may apply to a related identity task, but it does not establish check permitted user category, license feature matrix, linked contact model and data visibility for a partnership project compares lightweight external identity access with business-object-intensive portal needs The controlling boundary is: A cheaper external identity license is not interchangeable with every internal Salesforce license.

Question 622

A partnership project compares lightweight external identity access with business-object-intensive portal needs. Most decisive verification?

  1. Map identity source, federation roles, app audiences, license needs and lifecycle ownership
  2. Audit source deactivation time, Salesforce active flag, tokens and effective API access
  3. Check current Salesforce retirement notice, synchronization owners, affected users and replacement provisioning flows
  4. Check permitted user category, license feature matrix, linked contact model and data visibility

Explanation

Correct Answer

D:

“Check permitted user category, license feature matrix, linked contact model and data visibility” distinguishes sign-in from entitlement administration in a partnership project compares lightweight external identity access with business-object-intensive portal needs It checks whether choose supported internal or external user licensing based on person population and required app capabilities.

Incorrect Answers

A:

“Map identity source, federation roles, app audiences, license needs and lifecycle ownership” needs to be evaluated against A partnership project compares lightweight external identity access with business-object-intensive portal needs. The relevant check is Check permitted user category, license feature matrix, linked contact model and data visibility; A cheaper external identity license is not interchangeable with every internal Salesforce license.

B:

“Audit source deactivation time, Salesforce active flag, tokens and effective API access” needs to be evaluated against A partnership project compares lightweight external identity access with business-object-intensive portal needs. The relevant check is Check permitted user category, license feature matrix, linked contact model and data visibility; A cheaper external identity license is not interchangeable with every internal Salesforce license.

C:

“Check current Salesforce retirement notice, synchronization owners, affected users and replacement provisioning flows” needs to be evaluated against A partnership project compares lightweight external identity access with business-object-intensive portal needs. The relevant check is Check permitted user category, license feature matrix, linked contact model and data visibility; A cheaper external identity license is not interchangeable with every internal Salesforce license.

Question 623

A partnership project compares lightweight external identity access with business-object-intensive portal needs. Key caution for this case?

  1. A cheaper external identity license is not interchangeable with every internal Salesforce license
  2. Federation of authentication alone does not synchronize all employment lifecycle events
  3. A directory audit without Salesforce permission evidence cannot prove application access was correctly controlled
  4. Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership

Explanation

Correct Answer

A:

“A cheaper external identity license is not interchangeable with every internal Salesforce license” needs to be evaluated against A partnership project compares lightweight external identity access with business-object-intensive portal needs. The relevant check is Check permitted user category, license feature matrix, linked contact model and data visibility; A cheaper external identity license is not interchangeable with every internal Salesforce license.

Incorrect Answers

B:

“Federation of authentication alone does not synchronize all employment lifecycle events” needs to be evaluated against A partnership project compares lightweight external identity access with business-object-intensive portal needs. The relevant check is Check permitted user category, license feature matrix, linked contact model and data visibility; A cheaper external identity license is not interchangeable with every internal Salesforce license.

C:

“A directory audit without Salesforce permission evidence cannot prove application access was correctly controlled” needs to be evaluated against A partnership project compares lightweight external identity access with business-object-intensive portal needs. The relevant check is Check permitted user category, license feature matrix, linked contact model and data visibility; A cheaper external identity license is not interchangeable with every internal Salesforce license.

D:

“Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership” needs to be evaluated against A partnership project compares lightweight external identity access with business-object-intensive portal needs. The relevant check is Check permitted user category, license feature matrix, linked contact model and data visibility; A cheaper external identity license is not interchangeable with every internal Salesforce license.

Question 624

A partnership project compares lightweight external identity access with business-object-intensive portal needs. Best complete IAM decision record?

  1. Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Map identity source, federation roles, app audiences, license needs and lifecycle ownership. Boundary: Federation of authentication alone does not synchronize all employment lifecycle events.
  2. Action: Plan migration in phases, including account matching, permissions, authentication and deprovisioning tests. Verification: Audit source deactivation time, Salesforce active flag, tokens and effective API access. Boundary: A cheaper external identity license is not interchangeable with every internal Salesforce license.
  3. Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Check permitted user category, license feature matrix, linked contact model and data visibility. Boundary: A cheaper external identity license is not interchangeable with every internal Salesforce license.
  4. Action: Define lifecycle observability and reconcile IAM evidence across directory, federation and Salesforce application layers. Verification: Check permitted user category, license feature matrix, linked contact model and data visibility. Boundary: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Explanation

Correct Answer

C:

“Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Check permitted user category, license feature matrix, linked contact model and data visibility. Boundary: A cheaper external identity license is not interchangeable with every internal Salesforce license” addresses the access-design responsibilities in a partnership project compares lightweight external identity access with business-object-intensive portal needs Test against check permitted user category, license feature matrix, linked contact model and data visibility; a cheaper external identity license is not interchangeable with every internal Salesforce license.

Incorrect Answers

A:

“Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Map identity source, federation roles, app audiences, license needs and lifecycle ownership. Boundary: Federation of authentication alone does not synchronize all employment lifecycle events” may apply to a related identity task, but it does not establish check permitted user category, license feature matrix, linked contact model and data visibility for a partnership project compares lightweight external identity access with business-object-intensive portal needs The controlling boundary is: A cheaper external identity license is not interchangeable with every internal Salesforce license.

B:

“Action: Plan migration in phases, including account matching, permissions, authentication and deprovisioning tests. Verification: Audit source deactivation time, Salesforce active flag, tokens and effective API access. Boundary: A cheaper external identity license is not interchangeable with every internal Salesforce license” may apply to a related identity task, but it does not establish check permitted user category, license feature matrix, linked contact model and data visibility for a partnership project compares lightweight external identity access with business-object-intensive portal needs The controlling boundary is: A cheaper external identity license is not interchangeable with every internal Salesforce license.

D:

“Action: Define lifecycle observability and reconcile IAM evidence across directory, federation and Salesforce application layers. Verification: Check permitted user category, license feature matrix, linked contact model and data visibility. Boundary: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership” may apply to a related identity task, but it does not establish check permitted user category, license feature matrix, linked contact model and data visibility for a partnership project compares lightweight external identity access with business-object-intensive portal needs The controlling boundary is: A cheaper external identity license is not interchangeable with every internal Salesforce license.

Question 625

An Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely. Best next IAM response?

  1. Publish an identity architecture responsibility matrix with accountable controls and escalation paths
  2. Inventory Identity Connect dependencies and design a supported migration before the existing subscription ends
  3. Use a persona-by-capability licensing matrix and verify the currently supported Identity and Experience Cloud SKUs
  4. Treat subscription expiration as a migration deadline and document affected features and user controls

Explanation

Correct Answer

D:

“Treat subscription expiration as a migration deadline and document affected features and user controls” addresses the access-design responsibilities in an Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely Test against verify subscription end date, identity sync, deactivation behavior and SSO fallback; identity Connect support and behavior after subscription expiration must not be guessed from old training material.

Incorrect Answers

A:

“Publish an identity architecture responsibility matrix with accountable controls and escalation paths” may apply to a related identity task, but it does not establish verify subscription end date, identity sync, deactivation behavior and SSO fallback for an Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely The controlling boundary is: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

B:

“Inventory Identity Connect dependencies and design a supported migration before the existing subscription ends” may apply to a related identity task, but it does not establish verify subscription end date, identity sync, deactivation behavior and SSO fallback for an Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely The controlling boundary is: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

C:

“Use a persona-by-capability licensing matrix and verify the currently supported Identity and Experience Cloud SKUs” may apply to a related identity task, but it does not establish verify subscription end date, identity sync, deactivation behavior and SSO fallback for an Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely The controlling boundary is: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

Question 626

An Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely. Most decisive verification?

  1. Verify subscription end date, identity sync, deactivation behavior and SSO fallback
  2. Compare pre/post migration roster, login success, disabled accounts and rollback path
  3. Map identity source, federation roles, app audiences, license needs and lifecycle ownership
  4. Verify ID links, profile merge policy, consent records and account ownership

Explanation

Correct Answer

A:

“Verify subscription end date, identity sync, deactivation behavior and SSO fallback” distinguishes sign-in from entitlement administration in an Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely It checks whether treat subscription expiration as a migration deadline and document affected features and user controls.

Incorrect Answers

B:

“Compare pre/post migration roster, login success, disabled accounts and rollback path” needs to be evaluated against An Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely. The relevant check is Verify subscription end date, identity sync, deactivation behavior and SSO fallback; Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

C:

“Map identity source, federation roles, app audiences, license needs and lifecycle ownership” needs to be evaluated against An Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely. The relevant check is Verify subscription end date, identity sync, deactivation behavior and SSO fallback; Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

D:

“Verify ID links, profile merge policy, consent records and account ownership” needs to be evaluated against An Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely. The relevant check is Verify subscription end date, identity sync, deactivation behavior and SSO fallback; Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

Question 627

An Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely. Key caution for this case?

  1. User status updates must be tested end to end rather than inferred from an upstream directory change
  2. Switching sync tools without controlling identity continuity can create duplicate users or orphan permissions
  3. Identity Connect support and behavior after subscription expiration must not be guessed from old training material
  4. Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership

Explanation

Correct Answer

C:

“Identity Connect support and behavior after subscription expiration must not be guessed from old training material” needs to be evaluated against An Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely. The relevant check is Verify subscription end date, identity sync, deactivation behavior and SSO fallback; Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

Incorrect Answers

A:

“User status updates must be tested end to end rather than inferred from an upstream directory change” needs to be evaluated against An Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely. The relevant check is Verify subscription end date, identity sync, deactivation behavior and SSO fallback; Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

B:

“Switching sync tools without controlling identity continuity can create duplicate users or orphan permissions” needs to be evaluated against An Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely. The relevant check is Verify subscription end date, identity sync, deactivation behavior and SSO fallback; Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

D:

“Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership” needs to be evaluated against An Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely. The relevant check is Verify subscription end date, identity sync, deactivation behavior and SSO fallback; Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

Question 628

An Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely. Best complete IAM decision record?

  1. Action: Treat subscription expiration as a migration deadline and document affected features and user controls. Verification: Verify subscription end date, identity sync, deactivation behavior and SSO fallback. Boundary: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.
  2. Action: Publish an identity architecture responsibility matrix with accountable controls and escalation paths. Verification: Verify subscription end date, identity sync, deactivation behavior and SSO fallback. Boundary: Switching sync tools without controlling identity continuity can create duplicate users or orphan permissions.
  3. Action: Inventory Identity Connect dependencies and design a supported migration before the existing subscription ends. Verification: Map identity source, federation roles, app audiences, license needs and lifecycle ownership. Boundary: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.
  4. Action: Treat subscription expiration as a migration deadline and document affected features and user controls. Verification: Compare pre/post migration roster, login success, disabled accounts and rollback path. Boundary: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Explanation

Correct Answer

A:

“Action: Treat subscription expiration as a migration deadline and document affected features and user controls. Verification: Verify subscription end date, identity sync, deactivation behavior and SSO fallback. Boundary: Identity Connect support and behavior after subscription expiration must not be guessed from old training material” addresses the access-design responsibilities in an Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely Test against verify subscription end date, identity sync, deactivation behavior and SSO fallback; identity Connect support and behavior after subscription expiration must not be guessed from old training material.

Incorrect Answers

B:

“Action: Publish an identity architecture responsibility matrix with accountable controls and escalation paths. Verification: Verify subscription end date, identity sync, deactivation behavior and SSO fallback. Boundary: Switching sync tools without controlling identity continuity can create duplicate users or orphan permissions” may apply to a related identity task, but it does not establish verify subscription end date, identity sync, deactivation behavior and SSO fallback for an Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely The controlling boundary is: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

C:

“Action: Inventory Identity Connect dependencies and design a supported migration before the existing subscription ends. Verification: Map identity source, federation roles, app audiences, license needs and lifecycle ownership. Boundary: Identity Connect support and behavior after subscription expiration must not be guessed from old training material” may apply to a related identity task, but it does not establish verify subscription end date, identity sync, deactivation behavior and SSO fallback for an Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely The controlling boundary is: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

D:

“Action: Treat subscription expiration as a migration deadline and document affected features and user controls. Verification: Compare pre/post migration roster, login success, disabled accounts and rollback path. Boundary: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership” may apply to a related identity task, but it does not establish verify subscription end date, identity sync, deactivation behavior and SSO fallback for an Identity Connect contract is ending next quarter and a project manager assumes sync will continue indefinitely The controlling boundary is: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

Question 629

A team has stopped renewing Identity Connect but retains mission-critical AD-to-Salesforce account provisioning. Best next IAM response?

  1. Publish an identity architecture responsibility matrix with accountable controls and escalation paths
  2. Use a persona-by-capability licensing matrix and verify the currently supported Identity and Experience Cloud SKUs
  3. Treat subscription expiration as a migration deadline and document affected features and user controls
  4. Inventory Identity Connect dependencies and design a supported migration before the existing subscription ends

Explanation

Correct Answer

C:

“Treat subscription expiration as a migration deadline and document affected features and user controls” addresses the access-design responsibilities in a team has stopped renewing Identity Connect but retains mission-critical AD-to-Salesforce account provisioning Test against verify subscription end date, identity sync, deactivation behavior and SSO fallback; identity Connect support and behavior after subscription expiration must not be guessed from old training material.

Incorrect Answers

A:

“Publish an identity architecture responsibility matrix with accountable controls and escalation paths” may apply to a related identity task, but it does not establish verify subscription end date, identity sync, deactivation behavior and SSO fallback for a team has stopped renewing Identity Connect but retains mission-critical AD-to-Salesforce account provisioning The controlling boundary is: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

B:

“Use a persona-by-capability licensing matrix and verify the currently supported Identity and Experience Cloud SKUs” may apply to a related identity task, but it does not establish verify subscription end date, identity sync, deactivation behavior and SSO fallback for a team has stopped renewing Identity Connect but retains mission-critical AD-to-Salesforce account provisioning The controlling boundary is: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

D:

“Inventory Identity Connect dependencies and design a supported migration before the existing subscription ends” may apply to a related identity task, but it does not establish verify subscription end date, identity sync, deactivation behavior and SSO fallback for a team has stopped renewing Identity Connect but retains mission-critical AD-to-Salesforce account provisioning The controlling boundary is: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

Question 630

A team has stopped renewing Identity Connect but retains mission-critical AD-to-Salesforce account provisioning. Most decisive verification?

  1. Map identity source, federation roles, app audiences, license needs and lifecycle ownership
  2. Verify subscription end date, identity sync, deactivation behavior and SSO fallback
  3. Compare pre/post migration roster, login success, disabled accounts and rollback path
  4. Verify ID links, profile merge policy, consent records and account ownership

Explanation

Correct Answer

B:

“Verify subscription end date, identity sync, deactivation behavior and SSO fallback” distinguishes sign-in from entitlement administration in a team has stopped renewing Identity Connect but retains mission-critical AD-to-Salesforce account provisioning It checks whether treat subscription expiration as a migration deadline and document affected features and user controls.

Incorrect Answers

A:

“Map identity source, federation roles, app audiences, license needs and lifecycle ownership” needs to be evaluated against A team has stopped renewing Identity Connect but retains mission-critical AD-to-Salesforce account provisioning. The relevant check is Verify subscription end date, identity sync, deactivation behavior and SSO fallback; Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

C:

“Compare pre/post migration roster, login success, disabled accounts and rollback path” needs to be evaluated against A team has stopped renewing Identity Connect but retains mission-critical AD-to-Salesforce account provisioning. The relevant check is Verify subscription end date, identity sync, deactivation behavior and SSO fallback; Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

D:

“Verify ID links, profile merge policy, consent records and account ownership” needs to be evaluated against A team has stopped renewing Identity Connect but retains mission-critical AD-to-Salesforce account provisioning. The relevant check is Verify subscription end date, identity sync, deactivation behavior and SSO fallback; Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

Certified Platform Identity and Access Management Architect Practice Tests