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 59

Question 580

A consulting firm asks whether an identity-only Salesforce license grants access to sales opportunity objects. Best complete IAM decision record?

  1. Action: Use a persona-by-capability licensing matrix and verify the currently supported Identity and Experience Cloud SKUs. Verification: Check current Salesforce retirement notice, synchronization owners, affected users and replacement provisioning flows. Boundary: Authentication entitlement does not by itself guarantee full CRM feature or data access.
  2. Action: Match license entitlements to actual authentication and Salesforce business-object usage before choosing a SKU. Verification: Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation. Boundary: User status updates must be tested end to end rather than inferred from an upstream directory change.
  3. Action: Match license entitlements to actual authentication and Salesforce business-object usage before choosing a SKU. Verification: Validate license type, permission-set eligibility, allowed objects and user acceptance tests. Boundary: Authentication entitlement does not by itself guarantee full CRM feature or data access.
  4. Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Validate license type, permission-set eligibility, allowed objects and user acceptance tests. Boundary: A directory audit without Salesforce permission evidence cannot prove application access was correctly controlled.

Explanation

Correct Answer

C:

“Action: Match license entitlements to actual authentication and Salesforce business-object usage before choosing a SKU. Verification: Validate license type, permission-set eligibility, allowed objects and user acceptance tests. Boundary: Authentication entitlement does not by itself guarantee full CRM feature or data access” addresses the access-design responsibilities in a consulting firm asks whether an identity-only Salesforce license grants access to sales opportunity objects Test against validate license type, permission-set eligibility, allowed objects and user acceptance tests; authentication entitlement does not by itself guarantee full CRM feature or data access.

Incorrect Answers

A:

“Action: Use a persona-by-capability licensing matrix and verify the currently supported Identity and Experience Cloud SKUs. Verification: Check current Salesforce retirement notice, synchronization owners, affected users and replacement provisioning flows. Boundary: Authentication entitlement does not by itself guarantee full CRM feature or data access” may apply to a related identity task, but it does not establish validate license type, permission-set eligibility, allowed objects and user acceptance tests for a consulting firm asks whether an identity-only Salesforce license grants access to sales opportunity objects The controlling boundary is: Authentication entitlement does not by itself guarantee full CRM feature or data access.

B:

“Action: Match license entitlements to actual authentication and Salesforce business-object usage before choosing a SKU. Verification: Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation. Boundary: User status updates must be tested end to end rather than inferred from an upstream directory change” may apply to a related identity task, but it does not establish validate license type, permission-set eligibility, allowed objects and user acceptance tests for a consulting firm asks whether an identity-only Salesforce license grants access to sales opportunity objects The controlling boundary is: Authentication entitlement does not by itself guarantee full CRM feature or data access.

D:

“Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Validate license type, permission-set eligibility, allowed objects and user acceptance tests. Boundary: A directory audit without Salesforce permission evidence cannot prove application access was correctly controlled” may apply to a related identity task, but it does not establish validate license type, permission-set eligibility, allowed objects and user acceptance tests for a consulting firm asks whether an identity-only Salesforce license grants access to sales opportunity objects The controlling boundary is: Authentication entitlement does not by itself guarantee full CRM feature or data access.

Question 581

A customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports. Best next IAM response?

  1. Use a persona-by-capability licensing matrix and verify the currently supported Identity and Experience Cloud SKUs
  2. Publish an identity architecture responsibility matrix with accountable controls and escalation paths
  3. Match license entitlements to actual authentication and Salesforce business-object usage before choosing a SKU
  4. Choose supported internal or external user licensing based on person population and required app capabilities

Explanation

Correct Answer

C:

“Match license entitlements to actual authentication and Salesforce business-object usage before choosing a SKU” addresses the access-design responsibilities in a customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports Test against validate license type, permission-set eligibility, allowed objects and user acceptance tests; authentication entitlement does not by itself guarantee full CRM feature or data access.

Incorrect Answers

A:

“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 validate license type, permission-set eligibility, allowed objects and user acceptance tests for a customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports The controlling boundary is: Authentication entitlement does not by itself guarantee full CRM feature or data access.

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 validate license type, permission-set eligibility, allowed objects and user acceptance tests for a customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports The controlling boundary is: Authentication entitlement does not by itself guarantee full CRM feature or data access.

D:

“Choose supported internal or external user licensing based on person population and required app capabilities” may apply to a related identity task, but it does not establish validate license type, permission-set eligibility, allowed objects and user acceptance tests for a customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports The controlling boundary is: Authentication entitlement does not by itself guarantee full CRM feature or data access.

Question 582

A customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports. Most decisive verification?

  1. Check current Salesforce retirement notice, synchronization owners, affected users and replacement provisioning flows
  2. Audit source deactivation time, Salesforce active flag, tokens and effective API access
  3. Validate license type, permission-set eligibility, allowed objects and user acceptance tests
  4. Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation

Explanation

Correct Answer

C:

“Validate license type, permission-set eligibility, allowed objects and user acceptance tests” distinguishes sign-in from entitlement administration in a customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports It checks whether match license entitlements to actual authentication and Salesforce business-object usage before choosing a SKU.

Incorrect Answers

A:

“Check current Salesforce retirement notice, synchronization owners, affected users and replacement provisioning flows” needs to be evaluated against A customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports. The relevant check is Validate license type, permission-set eligibility, allowed objects and user acceptance tests; Authentication entitlement does not by itself guarantee full CRM feature or data access.

B:

“Audit source deactivation time, Salesforce active flag, tokens and effective API access” needs to be evaluated against A customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports. The relevant check is Validate license type, permission-set eligibility, allowed objects and user acceptance tests; Authentication entitlement does not by itself guarantee full CRM feature or data access.

D:

“Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation” needs to be evaluated against A customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports. The relevant check is Validate license type, permission-set eligibility, allowed objects and user acceptance tests; Authentication entitlement does not by itself guarantee full CRM feature or data access.

Question 583

A customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports. Key caution for this case?

  1. User status updates must be tested end to end rather than inferred from an upstream directory change
  2. Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership
  3. Authentication entitlement does not by itself guarantee full CRM feature or data access
  4. A directory audit without Salesforce permission evidence cannot prove application access was correctly controlled

Explanation

Correct Answer

C:

“Authentication entitlement does not by itself guarantee full CRM feature or data access” needs to be evaluated against A customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports. The relevant check is Validate license type, permission-set eligibility, allowed objects and user acceptance tests; Authentication entitlement does not by itself guarantee full CRM feature or data access.

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 A customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports. The relevant check is Validate license type, permission-set eligibility, allowed objects and user acceptance tests; Authentication entitlement does not by itself guarantee full CRM feature or data access.

B:

“Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership” needs to be evaluated against A customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports. The relevant check is Validate license type, permission-set eligibility, allowed objects and user acceptance tests; Authentication entitlement does not by itself guarantee full CRM feature or data access.

D:

“A directory audit without Salesforce permission evidence cannot prove application access was correctly controlled” needs to be evaluated against A customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports. The relevant check is Validate license type, permission-set eligibility, allowed objects and user acceptance tests; Authentication entitlement does not by itself guarantee full CRM feature or data access.

Question 584

A customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports. Best complete IAM decision record?

  1. Action: Use a persona-by-capability licensing matrix and verify the currently supported Identity and Experience Cloud SKUs. Verification: Check current Salesforce retirement notice, synchronization owners, affected users and replacement provisioning flows. Boundary: Authentication entitlement does not by itself guarantee full CRM feature or data access.
  2. Action: Match license entitlements to actual authentication and Salesforce business-object usage before choosing a SKU. Verification: Validate license type, permission-set eligibility, allowed objects and user acceptance tests. Boundary: Authentication entitlement does not by itself guarantee full CRM feature or data access.
  3. Action: Match license entitlements to actual authentication and Salesforce business-object usage before choosing a SKU. Verification: Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation. Boundary: User status updates must be tested end to end rather than inferred from an upstream directory change.
  4. Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Validate license type, permission-set eligibility, allowed objects and user acceptance tests. Boundary: A directory audit without Salesforce permission evidence cannot prove application access was correctly controlled.

Explanation

Correct Answer

B:

“Action: Match license entitlements to actual authentication and Salesforce business-object usage before choosing a SKU. Verification: Validate license type, permission-set eligibility, allowed objects and user acceptance tests. Boundary: Authentication entitlement does not by itself guarantee full CRM feature or data access” addresses the access-design responsibilities in a customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports Test against validate license type, permission-set eligibility, allowed objects and user acceptance tests; authentication entitlement does not by itself guarantee full CRM feature or data access.

Incorrect Answers

A:

“Action: Use a persona-by-capability licensing matrix and verify the currently supported Identity and Experience Cloud SKUs. Verification: Check current Salesforce retirement notice, synchronization owners, affected users and replacement provisioning flows. Boundary: Authentication entitlement does not by itself guarantee full CRM feature or data access” may apply to a related identity task, but it does not establish validate license type, permission-set eligibility, allowed objects and user acceptance tests for a customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports The controlling boundary is: Authentication entitlement does not by itself guarantee full CRM feature or data access.

C:

“Action: Match license entitlements to actual authentication and Salesforce business-object usage before choosing a SKU. Verification: Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation. Boundary: User status updates must be tested end to end rather than inferred from an upstream directory change” may apply to a related identity task, but it does not establish validate license type, permission-set eligibility, allowed objects and user acceptance tests for a customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports The controlling boundary is: Authentication entitlement does not by itself guarantee full CRM feature or data access.

D:

“Action: Choose supported internal or external user licensing based on person population and required app capabilities. Verification: Validate license type, permission-set eligibility, allowed objects and user acceptance tests. Boundary: A directory audit without Salesforce permission evidence cannot prove application access was correctly controlled” may apply to a related identity task, but it does not establish validate license type, permission-set eligibility, allowed objects and user acceptance tests for a customer signs in to an identity hub and staff propose reusing that license to run unrestricted CRM reports The controlling boundary is: Authentication entitlement does not by itself guarantee full CRM feature or data access.

Question 585

A group wants one login directory to connect several Salesforce orgs and non-Salesforce apps. Best next IAM response?

  1. Define lifecycle observability and reconcile IAM evidence across directory, federation and Salesforce application layers
  2. Define authoritative identity directories, sync rules, change ownership and reconciliation checkpoints
  3. Evaluate the Salesforce Identity role within a broader Customer 360 architecture without assuming it replaces every external IdP
  4. Treat subscription expiration as a migration deadline and document affected features and user controls

Explanation

Correct Answer

C:

“Evaluate the Salesforce Identity role within a broader Customer 360 architecture without assuming it replaces every external IdP” addresses the access-design responsibilities in a group wants one login directory to connect several Salesforce orgs and non-Salesforce apps Test against map identity source, federation roles, app audiences, license needs and lifecycle ownership; customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Incorrect Answers

A:

“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 map identity source, federation roles, app audiences, license needs and lifecycle ownership for a group wants one login directory to connect several Salesforce orgs and non-Salesforce apps The controlling boundary is: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

B:

“Define authoritative identity directories, sync rules, change ownership and reconciliation checkpoints” may apply to a related identity task, but it does not establish map identity source, federation roles, app audiences, license needs and lifecycle ownership for a group wants one login directory to connect several Salesforce orgs and non-Salesforce apps The controlling boundary is: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

D:

“Treat subscription expiration as a migration deadline and document affected features and user controls” may apply to a related identity task, but it does not establish map identity source, federation roles, app audiences, license needs and lifecycle ownership for a group wants one login directory to connect several Salesforce orgs and non-Salesforce apps The controlling boundary is: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Question 586

A group wants one login directory to connect several Salesforce orgs and non-Salesforce apps. Most decisive verification?

  1. Verify subscription end date, identity sync, deactivation behavior and SSO fallback
  2. Map identity source, federation roles, app audiences, license needs and lifecycle ownership
  3. Inspect source object IDs, provisioning feed, conflicts, deactivate path and stale account checks
  4. Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation

Explanation

Correct Answer

B:

“Map identity source, federation roles, app audiences, license needs and lifecycle ownership” distinguishes sign-in from entitlement administration in a group wants one login directory to connect several Salesforce orgs and non-Salesforce apps It checks whether evaluate the Salesforce Identity role within a broader Customer 360 architecture without assuming it replaces every external IdP.

Incorrect Answers

A:

“Verify subscription end date, identity sync, deactivation behavior and SSO fallback” needs to be evaluated against A group wants one login directory to connect several Salesforce orgs and non-Salesforce apps. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

C:

“Inspect source object IDs, provisioning feed, conflicts, deactivate path and stale account checks” needs to be evaluated against A group wants one login directory to connect several Salesforce orgs and non-Salesforce apps. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

D:

“Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation” needs to be evaluated against A group wants one login directory to connect several Salesforce orgs and non-Salesforce apps. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Question 587

A group wants one login directory to connect several Salesforce orgs and non-Salesforce apps. Key caution for this case?

  1. Identity Connect support and behavior after subscription expiration must not be guessed from old training material
  2. Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership
  3. Switching sync tools without controlling identity continuity can create duplicate users or orphan permissions
  4. Salesforce announced Identity Connect retirement in October 2026 and does not plan a direct replacement product

Explanation

Correct Answer

B:

“Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership” needs to be evaluated against A group wants one login directory to connect several Salesforce orgs and non-Salesforce apps. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Incorrect Answers

A:

“Identity Connect support and behavior after subscription expiration must not be guessed from old training material” needs to be evaluated against A group wants one login directory to connect several Salesforce orgs and non-Salesforce apps. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

C:

“Switching sync tools without controlling identity continuity can create duplicate users or orphan permissions” needs to be evaluated against A group wants one login directory to connect several Salesforce orgs and non-Salesforce apps. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

D:

“Salesforce announced Identity Connect retirement in October 2026 and does not plan a direct replacement product” needs to be evaluated against A group wants one login directory to connect several Salesforce orgs and non-Salesforce apps. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Question 588

A group wants one login directory to connect several Salesforce orgs and non-Salesforce apps. Best complete IAM decision record?

  1. Action: Treat subscription expiration as a migration deadline and document affected features and user controls. Verification: Map identity source, federation roles, app audiences, license needs and lifecycle ownership. Boundary: Switching sync tools without controlling identity continuity can create duplicate users or orphan permissions.
  2. Action: Evaluate the Salesforce Identity role within a broader Customer 360 architecture without assuming it replaces every external IdP. Verification: Map identity source, federation roles, app audiences, license needs and lifecycle ownership. Boundary: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.
  3. Action: Define authoritative identity directories, sync rules, change ownership and reconciliation checkpoints. Verification: Verify subscription end date, identity sync, deactivation behavior and SSO fallback. Boundary: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.
  4. Action: Evaluate the Salesforce Identity role within a broader Customer 360 architecture without assuming it replaces every external IdP. Verification: Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation. Boundary: Identity Connect support and behavior after subscription expiration must not be guessed from old training material.

Explanation

Correct Answer

B:

“Action: Evaluate the Salesforce Identity role within a broader Customer 360 architecture without assuming it replaces every external IdP. Verification: Map identity source, federation roles, app audiences, license needs and lifecycle ownership. Boundary: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership” addresses the access-design responsibilities in a group wants one login directory to connect several Salesforce orgs and non-Salesforce apps Test against map identity source, federation roles, app audiences, license needs and lifecycle ownership; customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Incorrect Answers

A:

“Action: Treat subscription expiration as a migration deadline and document affected features and user controls. Verification: Map identity source, federation roles, app audiences, license needs and lifecycle ownership. 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 map identity source, federation roles, app audiences, license needs and lifecycle ownership for a group wants one login directory to connect several Salesforce orgs and non-Salesforce apps The controlling boundary is: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

C:

“Action: Define authoritative identity directories, sync rules, change ownership and reconciliation checkpoints. Verification: Verify subscription end date, identity sync, deactivation behavior and SSO fallback. 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 map identity source, federation roles, app audiences, license needs and lifecycle ownership for a group wants one login directory to connect several Salesforce orgs and non-Salesforce apps The controlling boundary is: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

D:

“Action: Evaluate the Salesforce Identity role within a broader Customer 360 architecture without assuming it replaces every external IdP. Verification: Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation. 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 map identity source, federation roles, app audiences, license needs and lifecycle ownership for a group wants one login directory to connect several Salesforce orgs and non-Salesforce apps The controlling boundary is: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Question 589

A service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems. Best next IAM response?

  1. Define lifecycle observability and reconcile IAM evidence across directory, federation and Salesforce application layers
  2. Treat subscription expiration as a migration deadline and document affected features and user controls
  3. Evaluate the Salesforce Identity role within a broader Customer 360 architecture without assuming it replaces every external IdP
  4. Define authoritative identity directories, sync rules, change ownership and reconciliation checkpoints

Explanation

Correct Answer

C:

“Evaluate the Salesforce Identity role within a broader Customer 360 architecture without assuming it replaces every external IdP” addresses the access-design responsibilities in a service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems Test against map identity source, federation roles, app audiences, license needs and lifecycle ownership; customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Incorrect Answers

A:

“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 map identity source, federation roles, app audiences, license needs and lifecycle ownership for a service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems The controlling boundary is: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

B:

“Treat subscription expiration as a migration deadline and document affected features and user controls” may apply to a related identity task, but it does not establish map identity source, federation roles, app audiences, license needs and lifecycle ownership for a service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems The controlling boundary is: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

D:

“Define authoritative identity directories, sync rules, change ownership and reconciliation checkpoints” may apply to a related identity task, but it does not establish map identity source, federation roles, app audiences, license needs and lifecycle ownership for a service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems The controlling boundary is: Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Question 590

A service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems. Most decisive verification?

  1. Inspect source object IDs, provisioning feed, conflicts, deactivate path and stale account checks
  2. Verify subscription end date, identity sync, deactivation behavior and SSO fallback
  3. Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation
  4. Map identity source, federation roles, app audiences, license needs and lifecycle ownership

Explanation

Correct Answer

D:

“Map identity source, federation roles, app audiences, license needs and lifecycle ownership” distinguishes sign-in from entitlement administration in a service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems It checks whether evaluate the Salesforce Identity role within a broader Customer 360 architecture without assuming it replaces every external IdP.

Incorrect Answers

A:

“Inspect source object IDs, provisioning feed, conflicts, deactivate path and stale account checks” needs to be evaluated against A service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

B:

“Verify subscription end date, identity sync, deactivation behavior and SSO fallback” needs to be evaluated against A service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

C:

“Test representative user rights, sharing, features and license cost assumptions with current Salesforce documentation” needs to be evaluated against A service company uses Salesforce as a central identity source for some apps but an existing IdP for regulated workforce systems. The relevant check is Map identity source, federation roles, app audiences, license needs and lifecycle ownership; Customer 360 identity architecture can involve multiple authorities and must not be conflated with universal credential ownership.

Certified Platform Identity and Access Management Architect Practice Tests