Salesforce Certified Platform Identity and Access Management Architect Practice Test 52
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.
Question 511
Salesforce and its partners face the following situation: An AD account is disabled for a departing employee but Salesforce retains a previously authorized API session. The integration review notes: The directory provisioning job updates user state only once each night and ignores issued tokens. Which architectural step should take priority?
- 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.
- Read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends.
- Document its historical directory provisioning role and plan evaluation of supported alternative provisioning solutions.
Explanation
Correct Answer
A:Best. The most direct action is to coordinate deactivation timing, access-token or session revocation and reconciliation independent of connector brand. It is supported by the specific finding that the directory provisioning job updates user state only once each night and ignores issued tokens. The expected acceptance evidence is: Departing employees lose practical Salesforce access within the approved offboarding window.
Incorrect Answers
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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: Coordinate deactivation timing, access-token or session revocation and reconciliation independent of connector brand.
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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: Coordinate deactivation timing, access-token or session revocation and reconciliation independent of connector brand.
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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: Coordinate deactivation timing, access-token or session revocation and reconciliation independent of connector brand.
Question 512
An implementation team investigates this scenario: An AD account is disabled for a departing employee but Salesforce retains a previously authorized API session. Which finding would most directly justify a change to the integration architecture?
- 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.
- A newly imported directory user inherits permissions from a static mapping that no one has reviewed.
- Operations assume the vendor will extend feature support forever and have not tested another provisioning path.
Explanation
Correct Answer
A:Best. The decisive observation is: The directory provisioning job updates user state only once each night and ignores issued tokens. This is why the design response should be: Coordinate deactivation timing, access-token or session revocation and reconciliation independent of connector brand.
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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: The directory provisioning job updates user state only once each night and ignores issued tokens.
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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: The directory provisioning job updates user state only once each night and ignores issued tokens.
D: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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: The directory provisioning job updates user state only once each night and ignores issued tokens.
Question 513
A solution review asks whether this control is effective: Coordinate deactivation timing, access-token or session revocation and reconciliation independent of connector brand. The business setting is: An AD account is disabled for a departing employee but Salesforce retains a previously authorized API session. What should a demonstrable successful outcome be?
- User records sync through a supported lifecycle process while SSO uses a defined trusted IdP.
- The replacement plan keeps lifecycle synchronization without depending on new Identity Connect feature development.
- Departing employees lose practical Salesforce access within the approved offboarding window.
- The enterprise has a validated fallback for directory-driven user creation and deactivation.
Explanation
Correct Answer
C:Best. The verification target is: Departing employees lose practical Salesforce access within the approved offboarding window. It tests whether the chosen approach—Coordinate deactivation timing, access-token or session revocation and reconciliation independent of connector brand.—actually resolves the specific finding: The directory provisioning job updates user state only once each night and ignores issued tokens.
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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: Departing employees lose practical Salesforce access within the approved offboarding window.
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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: Departing employees lose practical Salesforce access within the approved offboarding window.
D: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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: Departing employees lose practical Salesforce access within the approved offboarding window.
Question 514
A Salesforce integration initiative faces this situation: An AD account is disabled for a departing employee but Salesforce retains a previously authorized API session. The critical observation is: The directory provisioning job updates user state only once each night and ignores issued tokens. What failure is most likely if it is ignored?
- Duplicate identities and conflicting group memberships create unexpected admin grants after the merger.
- A completed directory sync is falsely assumed to invalidate all previously issued tokens instantly.
- An architect recommends a new long-term Identity Connect deployment as if the retired product were actively developed.
- An account-provisioning connector is incorrectly treated as the service that signs SAML assertions.
Explanation
Correct Answer
B:Best. The most direct failure is: A completed directory sync is falsely assumed to invalidate all previously issued tokens instantly. It is a consequence of the documented condition: The directory provisioning job updates user state only once each night and ignores issued tokens. A mitigation is: Coordinate deactivation timing, access-token or session revocation and reconciliation independent of connector brand.
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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: A completed directory sync is falsely assumed to invalidate all previously issued tokens instantly.
C: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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: A completed directory sync is falsely assumed to invalidate all previously issued tokens instantly.
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: The directory provisioning job updates user state only once each night and ignores issued tokens. The direct answer here is: A completed directory sync is falsely assumed to invalidate all previously issued tokens instantly.
Question 515
An integration architect receives this requirement: A merged company runs two legacy AD forests and one Salesforce org using an Identity Connect-era provisioning design. A technical discovery also finds: Users can appear in both forests with different directory identifiers and conflicting group assignments. Which response most directly addresses the present constraint?
- Define canonical identity matching, authoritative lifecycle ownership and a vendor-supported migration route.
- Read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends.
- Coordinate deactivation timing, access-token or session revocation and reconciliation independent of connector brand.
- Explain that Identity Connect historically synchronized AD identities, then compare supported provisioning alternatives.
Explanation
Correct Answer
A:Best. The most direct action is to define canonical identity matching, authoritative lifecycle ownership and a vendor-supported migration route. It is supported by the specific finding that Users can appear in both forests with different directory identifiers and conflicting group assignments. The expected acceptance evidence is: One Salesforce user maps to each employee, with clear provisioning source and minimal permissions.
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: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: Define canonical identity matching, authoritative lifecycle ownership and a vendor-supported migration route.
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: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: Define canonical identity matching, authoritative lifecycle ownership and a vendor-supported migration route.
D: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: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: Define canonical identity matching, authoritative lifecycle ownership and a vendor-supported migration route.
Question 516
Consider the following hypothetical Salesforce initiative: A merged company runs two legacy AD forests and one Salesforce org using an Identity Connect-era provisioning design. Which evidence would most strongly explain the current integration weakness?
- A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance.
- A newly imported directory user inherits permissions from a static mapping that no one has reviewed.
- Operations assume the vendor will extend feature support forever and have not tested another provisioning path.
- Users can appear in both forests with different directory identifiers and conflicting group assignments.
Explanation
Correct Answer
D:Best. The decisive observation is: Users can appear in both forests with different directory identifiers and conflicting group assignments. This is why the design response should be: Define canonical identity matching, authoritative lifecycle ownership and a vendor-supported migration route.
Incorrect Answers
A: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: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: Users can appear in both forests with different directory identifiers and conflicting group assignments.
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: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: Users can appear in both forests with different directory identifiers and conflicting group assignments.
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: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: Users can appear in both forests with different directory identifiers and conflicting group assignments.
Question 517
Review this change: Define canonical identity matching, authoritative lifecycle ownership and a vendor-supported migration route. It addresses a project where A merged company runs two legacy AD forests and one Salesforce org using an Identity Connect-era provisioning design. Which result should appear in integration acceptance evidence?
- New users receive needed accounts and separately approved Salesforce entitlements.
- 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.
- Departing employees lose practical Salesforce access within the approved offboarding window.
Explanation
Correct Answer
B:Best. The verification target is: One Salesforce user maps to each employee, with clear provisioning source and minimal permissions. It tests whether the chosen approach—Define canonical identity matching, authoritative lifecycle ownership and a vendor-supported migration route.—actually resolves the specific finding: Users can appear in both forests with different directory identifiers and conflicting group assignments.
Incorrect Answers
A: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: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: One Salesforce user maps to each employee, with clear provisioning source and minimal permissions.
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: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: One Salesforce user maps to each employee, with clear provisioning source and minimal permissions.
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: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: One Salesforce user maps to each employee, with clear provisioning source and minimal permissions.
Question 518
Suppose the integration design proceeds without correcting this issue: Users can appear in both forests with different directory identifiers and conflicting group assignments. In the environment A merged company runs two legacy AD forests and one Salesforce org using an Identity Connect-era provisioning design. What should the risk register emphasize?
- Duplicate identities and conflicting group memberships create unexpected admin grants after the merger.
- Directory synchronization is mistaken for proof that every assigned application privilege is appropriate.
- An account-provisioning connector is incorrectly treated as the service that signs SAML assertions.
- A single CRM customer identifier is mistaken for an authenticated login credential.
Explanation
Correct Answer
A:Best. The most direct failure is: Duplicate identities and conflicting group memberships create unexpected admin grants after the merger. It is a consequence of the documented condition: Users can appear in both forests with different directory identifiers and conflicting group assignments. A mitigation is: Define canonical identity matching, authoritative lifecycle ownership and a vendor-supported migration route.
Incorrect Answers
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: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: Duplicate identities and conflicting group memberships create unexpected admin grants after the merger.
C: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: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: Duplicate identities and conflicting group memberships create unexpected admin grants after the merger.
D:Not best for this scenario. This option is associated with another type of requirement: A telecom provider wants customers to use one login across several branded service portals. Its relevant condition is: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The present case instead turns on: Users can appear in both forests with different directory identifiers and conflicting group assignments. The direct answer here is: Duplicate identities and conflicting group memberships create unexpected admin grants after the merger.
Question 519
Salesforce and its partners face the following situation: A retailer wants a unified customer profile across ecommerce and Salesforce but already has an enterprise IdP. The integration review notes: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. Which architectural step should take priority?
- Evaluate durable customer identifiers and supported identity resolution aligned to authentication policy.
- Separate customer identity resolution from partner authentication, delegated authorization and legal data sharing.
- Define customer authentication and identity-linking requirements independently of profile unification.
- Assess Customer 360 identity needs separately from federation and customer-data unification components.
Explanation
Correct Answer
D:Best. The most direct action is to assess Customer 360 identity needs separately from federation and customer-data unification components. It is supported by the specific finding that the architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The expected acceptance evidence is: The solution clearly assigns responsibility for login, matching, consent and profile data.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A public membership platform has customer records shared between commerce, support and loyalty services. Its relevant condition is: A user can have two email addresses but should retain one governed customer identity association. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: Assess Customer 360 identity needs separately from federation and customer-data unification components.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An insurance company wants to connect customer identity between service applications and external partners. Its relevant condition is: The diagram has one global customer record but no documented trust or permissions at partner boundaries. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: Assess Customer 360 identity needs separately from federation and customer-data unification components.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A telecom provider wants customers to use one login across several branded service portals. Its relevant condition is: Its proposed Customer 360 architecture includes CRM data federation but no shared authentication strategy. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: Assess Customer 360 identity needs separately from federation and customer-data unification components.
Question 520
An implementation team investigates this scenario: A retailer wants a unified customer profile across ecommerce and Salesforce but already has an enterprise IdP. Which finding would most directly justify a change to the integration architecture?
- Existing systems already perform strong authentication, but customer attributes are fragmented between many records.
- The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration.
- The portal and app authenticate at different providers but must link to an approved CRM contact.
- Marketing assumes that a unified profile permits every application to reuse all customer data for any purpose.
Explanation
Correct Answer
B:Best. The decisive observation is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. This is why the design response should be: Assess Customer 360 identity needs separately from federation and customer-data unification components.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A financial services architecture board evaluates whether Salesforce identity capabilities fit a mature customer data platform. Its relevant condition is: Existing systems already perform strong authentication, but customer attributes are fragmented between many records. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration.
C:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A customer registers in an Experience Cloud portal and later uses a mobile loyalty app. Its relevant condition is: The portal and app authenticate at different providers but must link to an approved CRM contact. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An enterprise wants to centralize customer consent alongside Salesforce Customer 360 use cases. Its relevant condition is: Marketing assumes that a unified profile permits every application to reuse all customer data for any purpose. The present case instead turns on: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration. The direct answer here is: The architecture team conflates identity proof, customer record matching, marketing consent and CRM data integration.