Salesforce Certified Platform Identity and Access Management Architect Practice Test 51
Question 500
An implementation team investigates this scenario: A customer wants to replace manual Salesforce user creation from a Windows directory with a modern supported workflow. Which finding would most directly justify a change to the integration architecture?
- A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance.
- Operations assume the vendor will extend feature support forever and have not tested another provisioning path.
- A newly imported directory user inherits permissions from a static mapping that no one has reviewed.
- The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login.
Explanation
Correct Answer
A:Best. The decisive observation is: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. This is why the design response should be: Explain that Identity Connect historically synchronized AD identities, then compare supported provisioning alternatives.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company has an existing Identity Connect subscription that ends next quarter. Its relevant condition is: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The present case instead turns on: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The direct answer here is: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An auditor finds that Identity Connect provisions accounts but does not enforce least-privilege Salesforce sharing. Its relevant condition is: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The present case instead turns on: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The direct answer here is: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise expects Salesforce Identity Connect to perform single sign-on authentication for its employees. Its relevant condition is: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The present case instead turns on: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The direct answer here is: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance.
Question 501
A solution review asks whether this control is effective: Explain that Identity Connect historically synchronized AD identities, then compare supported provisioning alternatives. The business setting is: A customer wants to replace manual Salesforce user creation from a Windows directory with a modern supported workflow. What should a demonstrable successful outcome be?
- Departing employees lose practical Salesforce access within the approved offboarding window.
- The replacement plan keeps lifecycle synchronization without depending on new Identity Connect feature development.
- The enterprise has a validated fallback for directory-driven user creation and deactivation.
- Existing subscribed synchronization remains governed while the enterprise builds a migration strategy.
Explanation
Correct Answer
B:Best. The verification target is: The replacement plan keeps lifecycle synchronization without depending on new Identity Connect feature development. It tests whether the chosen approach—Explain that Identity Connect historically synchronized AD identities, then compare supported provisioning alternatives.—actually resolves the specific finding: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An AD account is disabled for a departing employee but Salesforce retains a previously authorized API session. Its relevant condition is: The directory provisioning job updates user state only once each night and ignores issued tokens. The present case instead turns on: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The direct answer here is: The replacement plan keeps lifecycle synchronization without depending on new Identity Connect feature development.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company has an existing Identity Connect subscription that ends next quarter. Its relevant condition is: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The present case instead turns on: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The direct answer here is: The replacement plan keeps lifecycle synchronization without depending on new Identity Connect feature development.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturing firm still uses Salesforce Identity Connect to synchronize on-premises Active Directory users. Its relevant condition is: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The present case instead turns on: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The direct answer here is: The replacement plan keeps lifecycle synchronization without depending on new Identity Connect feature development.
Question 502
A Salesforce integration initiative faces this situation: A customer wants to replace manual Salesforce user creation from a Windows directory with a modern supported workflow. The critical observation is: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. What failure is most likely if it is ignored?
- Duplicate identities and conflicting group memberships create unexpected admin grants after the merger.
- A subscription expiration interrupts user onboarding because the old connector had no migration plan.
- A retiring connector becomes a permanent single point of provisioning failure for the workforce.
- An architect recommends a new long-term Identity Connect deployment as if the retired product were actively developed.
Explanation
Correct Answer
C:Best. The most direct failure is: A retiring connector becomes a permanent single point of provisioning failure for the workforce. It is a consequence of the documented condition: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. A mitigation is: Explain that Identity Connect historically synchronized AD identities, then compare supported provisioning alternatives.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A merged company runs two legacy AD forests and one Salesforce org using an Identity Connect-era provisioning design. Its relevant condition is: Users can appear in both forests with different directory identifiers and conflicting group assignments. The present case instead turns on: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The direct answer here is: A retiring connector becomes a permanent single point of provisioning failure for the workforce.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company has an existing Identity Connect subscription that ends next quarter. Its relevant condition is: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The present case instead turns on: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The direct answer here is: A retiring connector becomes a permanent single point of provisioning failure for the workforce.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturing firm still uses Salesforce Identity Connect to synchronize on-premises Active Directory users. Its relevant condition is: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The present case instead turns on: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The direct answer here is: A retiring connector becomes a permanent single point of provisioning failure for the workforce.
Question 503
In this fictional project, An auditor finds that Identity Connect provisions accounts but does not enforce least-privilege Salesforce sharing. The project team has uncovered that A newly imported directory user inherits permissions from a static mapping that no one has reviewed. Which action is best supported by those facts?
- Define canonical identity matching, authoritative lifecycle ownership and a vendor-supported migration route.
- Add explicit Salesforce role and permission-set governance to the provisioning and reconciliation process.
- Coordinate deactivation timing, access-token or session revocation and reconciliation independent of connector brand.
- Separate directory user provisioning from federated authentication and document the relevant integration roles.
Explanation
Correct Answer
B:Best. The most direct action is to add explicit Salesforce role and permission-set governance to the provisioning and reconciliation process. It is supported by the specific finding that A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The expected acceptance evidence is: New users receive needed accounts and separately approved Salesforce entitlements.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A merged company runs two legacy AD forests and one Salesforce org using an Identity Connect-era provisioning design. Its relevant condition is: Users can appear in both forests with different directory identifiers and conflicting group assignments. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: Add explicit Salesforce role and permission-set governance to the provisioning and reconciliation process.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An AD account is disabled for a departing employee but Salesforce retains a previously authorized API session. Its relevant condition is: The directory provisioning job updates user state only once each night and ignores issued tokens. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: Add explicit Salesforce role and permission-set governance to the provisioning and reconciliation process.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise expects Salesforce Identity Connect to perform single sign-on authentication for its employees. Its relevant condition is: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: Add explicit Salesforce role and permission-set governance to the provisioning and reconciliation process.
Question 504
An enterprise review begins with this business situation: An auditor finds that Identity Connect provisions accounts but does not enforce least-privilege Salesforce sharing. Which technical or process signal best identifies the obstacle?
- Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers.
- The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login.
- A newly imported directory user inherits permissions from a static mapping that no one has reviewed.
- The directory provisioning job updates user state only once each night and ignores issued tokens.
Explanation
Correct Answer
C:Best. The decisive observation is: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. This is why the design response should be: Add explicit Salesforce role and permission-set governance to the provisioning and reconciliation process.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturing firm still uses Salesforce Identity Connect to synchronize on-premises Active Directory users. Its relevant condition is: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: A newly imported directory user inherits permissions from a static mapping that no one has reviewed.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise expects Salesforce Identity Connect to perform single sign-on authentication for its employees. Its relevant condition is: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: A newly imported directory user inherits permissions from a static mapping that no one has reviewed.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An AD account is disabled for a departing employee but Salesforce retains a previously authorized API session. Its relevant condition is: The directory provisioning job updates user state only once each night and ignores issued tokens. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: A newly imported directory user inherits permissions from a static mapping that no one has reviewed.
Question 505
The team adopts this approach: Add explicit Salesforce role and permission-set governance to the provisioning and reconciliation process. The original project scenario is: An auditor finds that Identity Connect provisions accounts but does not enforce least-privilege Salesforce sharing. Which verification outcome best demonstrates that it worked?
- User records sync through a supported lifecycle process while SSO uses a defined trusted IdP.
- One Salesforce user maps to each employee, with clear provisioning source and minimal permissions.
- The enterprise has a validated fallback for directory-driven user creation and deactivation.
- New users receive needed accounts and separately approved Salesforce entitlements.
Explanation
Correct Answer
D:Best. The verification target is: New users receive needed accounts and separately approved Salesforce entitlements. It tests whether the chosen approach—Add explicit Salesforce role and permission-set governance to the provisioning and reconciliation process.—actually resolves the specific finding: A newly imported directory user inherits permissions from a static mapping that no one has reviewed.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise expects Salesforce Identity Connect to perform single sign-on authentication for its employees. Its relevant condition is: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: New users receive needed accounts and separately approved Salesforce entitlements.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A merged company runs two legacy AD forests and one Salesforce org using an Identity Connect-era provisioning design. Its relevant condition is: Users can appear in both forests with different directory identifiers and conflicting group assignments. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: New users receive needed accounts and separately approved Salesforce entitlements.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company has an existing Identity Connect subscription that ends next quarter. Its relevant condition is: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: New users receive needed accounts and separately approved Salesforce entitlements.
Question 506
A project manager declines to address this finding: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The related project is: An auditor finds that Identity Connect provisions accounts but does not enforce least-privilege Salesforce sharing. Which consequence most directly follows?
- A subscription expiration interrupts user onboarding because the old connector had no migration plan.
- An account-provisioning connector is incorrectly treated as the service that signs SAML assertions.
- Directory synchronization is mistaken for proof that every assigned application privilege is appropriate.
- An architect recommends a new long-term Identity Connect deployment as if the retired product were actively developed.
Explanation
Correct Answer
C:Best. The most direct failure is: Directory synchronization is mistaken for proof that every assigned application privilege is appropriate. It is a consequence of the documented condition: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. A mitigation is: Add explicit Salesforce role and permission-set governance to the provisioning and reconciliation process.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A company has an existing Identity Connect subscription that ends next quarter. Its relevant condition is: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: Directory synchronization is mistaken for proof that every assigned application privilege is appropriate.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise expects Salesforce Identity Connect to perform single sign-on authentication for its employees. Its relevant condition is: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: Directory synchronization is mistaken for proof that every assigned application privilege is appropriate.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A manufacturing firm still uses Salesforce Identity Connect to synchronize on-premises Active Directory users. Its relevant condition is: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The present case instead turns on: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The direct answer here is: Directory synchronization is mistaken for proof that every assigned application privilege is appropriate.
Question 507
In this fictional project, A company has an existing Identity Connect subscription that ends next quarter. The project team has uncovered that Operations assume the vendor will extend feature support forever and have not tested another provisioning path. Which action is best supported by those facts?
- Read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends.
- Explain that Identity Connect historically synchronized AD identities, then compare supported provisioning alternatives.
- Add explicit Salesforce role and permission-set governance to the provisioning and reconciliation process.
- Define canonical identity matching, authoritative lifecycle ownership and a vendor-supported migration route.
Explanation
Correct Answer
A:Best. The most direct action is to read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends. It is supported by the specific finding that Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The expected acceptance evidence is: The enterprise has a validated fallback for directory-driven user creation and deactivation.
Incorrect Answers
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A customer wants to replace manual Salesforce user creation from a Windows directory with a modern supported workflow. Its relevant condition is: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: Read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An auditor finds that Identity Connect provisions accounts but does not enforce least-privilege Salesforce sharing. Its relevant condition is: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: Read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A merged company runs two legacy AD forests and one Salesforce org using an Identity Connect-era provisioning design. Its relevant condition is: Users can appear in both forests with different directory identifiers and conflicting group assignments. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: Read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends.
Question 508
An enterprise review begins with this business situation: A company has an existing Identity Connect subscription that ends next quarter. Which technical or process signal best identifies the obstacle?
- The directory provisioning job updates user state only once each night and ignores issued tokens.
- A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance.
- Operations assume the vendor will extend feature support forever and have not tested another provisioning path.
- The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login.
Explanation
Correct Answer
C:Best. The decisive observation is: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. This is why the design response should be: Read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An AD account is disabled for a departing employee but Salesforce retains a previously authorized API session. Its relevant condition is: The directory provisioning job updates user state only once each night and ignores issued tokens. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: Operations assume the vendor will extend feature support forever and have not tested another provisioning path.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A customer wants to replace manual Salesforce user creation from a Windows directory with a modern supported workflow. Its relevant condition is: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: Operations assume the vendor will extend feature support forever and have not tested another provisioning path.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise expects Salesforce Identity Connect to perform single sign-on authentication for its employees. Its relevant condition is: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: Operations assume the vendor will extend feature support forever and have not tested another provisioning path.
Question 509
The team adopts this approach: Read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends. The original project scenario is: A company has an existing Identity Connect subscription that ends next quarter. Which verification outcome best demonstrates that it worked?
- The site supports permitted customer sign-in under eligible external identity or experience licensing.
- New users receive needed accounts and separately approved Salesforce entitlements.
- The enterprise has a validated fallback for directory-driven user creation and deactivation.
- One Salesforce user maps to each employee, with clear provisioning source and minimal permissions.
Explanation
Correct Answer
C:Best. The verification target is: The enterprise has a validated fallback for directory-driven user creation and deactivation. It tests whether the chosen approach—Read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends.—actually resolves the specific finding: Operations assume the vendor will extend feature support forever and have not tested another provisioning path.
Incorrect Answers
A:Not best for this scenario. This option is associated with another type of requirement: A digital ticketing company wants customers to authenticate but needs no CRM seats for general visitor sessions. Its relevant condition is: The team treats all authentication identities as though they require identical paid full users. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: The enterprise has a validated fallback for directory-driven user creation and deactivation.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An auditor finds that Identity Connect provisions accounts but does not enforce least-privilege Salesforce sharing. Its relevant condition is: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: The enterprise has a validated fallback for directory-driven user creation and deactivation.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A merged company runs two legacy AD forests and one Salesforce org using an Identity Connect-era provisioning design. Its relevant condition is: Users can appear in both forests with different directory identifiers and conflicting group assignments. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: The enterprise has a validated fallback for directory-driven user creation and deactivation.
Question 510
A project manager declines to address this finding: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The related project is: A company has an existing Identity Connect subscription that ends next quarter. Which consequence most directly follows?
- An account-provisioning connector is incorrectly treated as the service that signs SAML assertions.
- Directory synchronization is mistaken for proof that every assigned application privilege is appropriate.
- Duplicate identities and conflicting group memberships create unexpected admin grants after the merger.
- A subscription expiration interrupts user onboarding because the old connector had no migration plan.
Explanation
Correct Answer
D:Best. The most direct failure is: A subscription expiration interrupts user onboarding because the old connector had no migration plan. It is a consequence of the documented condition: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. A mitigation is: Read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise expects Salesforce Identity Connect to perform single sign-on authentication for its employees. Its relevant condition is: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: A subscription expiration interrupts user onboarding because the old connector had no migration plan.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An auditor finds that Identity Connect provisions accounts but does not enforce least-privilege Salesforce sharing. Its relevant condition is: A newly imported directory user inherits permissions from a static mapping that no one has reviewed. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: A subscription expiration interrupts user onboarding because the old connector had no migration plan.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A merged company runs two legacy AD forests and one Salesforce org using an Identity Connect-era provisioning design. Its relevant condition is: Users can appear in both forests with different directory identifiers and conflicting group assignments. The present case instead turns on: Operations assume the vendor will extend feature support forever and have not tested another provisioning path. The direct answer here is: A subscription expiration interrupts user onboarding because the old connector had no migration plan.