Salesforce Certified Platform Identity and Access Management Architect Practice Test 50
Question 490
An incident scenario concerns this architecture: An enterprise bans a previously trusted external app after detecting a vendor security incident. The team has discovered: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. Which project risk requires explicit mitigation?
- A former contractor uses stored refresh tokens long after the business relationship ends.
- A user with only basic authentication can enter the protected finance application.
- A hidden application keeps pulling records despite being removed from the user navigation.
- An unapproved employee grants the app API access to records beyond the organization's policy.
Explanation
Correct Answer
C:Best. The most direct failure is: A hidden application keeps pulling records despite being removed from the user navigation. It is a consequence of the documented condition: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. A mitigation is: Apply the supported connected-app block/revocation policy and inspect remaining token/session use.
Incorrect Answers
A:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A mobile connected app must not continue operating indefinitely after a contractor's account is disabled. Its relevant condition is: The application issues persistent refresh tokens and has no documented inactivity or revocation procedure. The present case instead turns on: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: A hidden application keeps pulling records despite being removed from the user navigation.
B:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: A Salesforce-connected finance app must require High Assurance when employees authorize new access. Its relevant condition is: The app's session policy is set to Standard despite handling highly sensitive payroll information. The present case instead turns on: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: A hidden application keeps pulling records despite being removed from the user navigation.
D:Not best for this scenario. This option is associated with a different requirement within the same syllabus objective: An external reporting app should be restricted to a vetted group of Salesforce employees. Its relevant condition is: Connected-app permitted-user policy allows all users to self-authorize new sessions without prior review. The present case instead turns on: Administrators only remove the app's menu item while OAuth refresh grants and active sessions remain. The direct answer here is: A hidden application keeps pulling records despite being removed from the user navigation.
Question 491
Salesforce and its partners face the following situation: A manufacturing firm still uses Salesforce Identity Connect to synchronize on-premises Active Directory users. The integration review notes: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. Which architectural step should take priority?
- Explain that Identity Connect historically synchronized AD identities, then compare supported provisioning alternatives.
- 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.
- Document its historical directory provisioning role and plan evaluation of supported alternative provisioning solutions.
Explanation
Correct Answer
D:Best. The most direct action is to document its historical directory provisioning role and plan evaluation of supported alternative provisioning solutions. It is supported by the specific finding that Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The expected acceptance evidence is: Existing subscribed synchronization remains governed while the enterprise builds a migration strategy.
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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: Document its historical directory provisioning role and plan evaluation of supported alternative provisioning solutions.
B: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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: Document its historical directory provisioning role and plan evaluation of supported alternative provisioning solutions.
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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: Document its historical directory provisioning role and plan evaluation of supported alternative provisioning solutions.
Question 492
An implementation team investigates this scenario: A manufacturing firm still uses Salesforce Identity Connect to synchronize on-premises Active Directory users. 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.
- Users can appear in both forests with different directory identifiers and conflicting group assignments.
- 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.
Explanation
Correct Answer
C:Best. The decisive observation is: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. This is why the design response should be: Document its historical directory provisioning role and plan evaluation of supported alternative provisioning solutions.
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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers.
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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers.
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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers.
Question 493
A solution review asks whether this control is effective: Document its historical directory provisioning role and plan evaluation of supported alternative provisioning solutions. The business setting is: A manufacturing firm still uses Salesforce Identity Connect to synchronize on-premises Active Directory users. What should a demonstrable successful outcome be?
- User records sync through a supported lifecycle process while SSO uses a defined trusted IdP.
- New users receive needed accounts and separately approved Salesforce entitlements.
- One Salesforce user maps to each employee, with clear provisioning source and minimal permissions.
- Existing subscribed synchronization remains governed while the enterprise builds a migration strategy.
Explanation
Correct Answer
D:Best. The verification target is: Existing subscribed synchronization remains governed while the enterprise builds a migration strategy. It tests whether the chosen approach—Document its historical directory provisioning role and plan evaluation of supported alternative provisioning solutions.—actually resolves the specific finding: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers.
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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: Existing subscribed synchronization remains governed while the enterprise builds a migration strategy.
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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: Existing subscribed synchronization remains governed while the enterprise builds a migration strategy.
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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: Existing subscribed synchronization remains governed while the enterprise builds a migration strategy.
Question 494
A Salesforce integration initiative faces this situation: A manufacturing firm still uses Salesforce Identity Connect to synchronize on-premises Active Directory users. The critical observation is: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. What failure is most likely if it is ignored?
- A subscription expiration interrupts user onboarding because the old connector had no migration plan.
- Directory synchronization is mistaken for proof that every assigned application privilege is appropriate.
- 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.
Explanation
Correct Answer
D:Best. The most direct failure is: An architect recommends a new long-term Identity Connect deployment as if the retired product were actively developed. It is a consequence of the documented condition: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. A mitigation is: Document its historical directory provisioning role and plan evaluation of supported alternative provisioning solutions.
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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: An architect recommends a new long-term Identity Connect deployment as if the retired product were actively developed.
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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: An architect recommends a new long-term Identity Connect deployment as if the retired product were actively developed.
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: Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers. The direct answer here is: An architect recommends a new long-term Identity Connect deployment as if the retired product were actively developed.
Question 495
An integration architect receives this requirement: An enterprise expects Salesforce Identity Connect to perform single sign-on authentication for its employees. A technical discovery also finds: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. Which response most directly addresses the present constraint?
- 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.
- Read current Salesforce retirement terms and begin migration assessment before the subscribed support window ends.
- Separate directory user provisioning from federated authentication and document the relevant integration roles.
Explanation
Correct Answer
D:Best. The most direct action is to separate directory user provisioning from federated authentication and document the relevant integration roles. It is supported by the specific finding that the inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The expected acceptance evidence is: User records sync through a supported lifecycle process while SSO uses a defined trusted IdP.
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: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: Separate directory user provisioning from federated authentication and document the relevant integration roles.
B: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: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: Separate directory user provisioning from federated authentication and document the relevant integration roles.
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 inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: Separate directory user provisioning from federated authentication and document the relevant integration roles.
Question 496
Consider the following hypothetical Salesforce initiative: An enterprise expects Salesforce Identity Connect to perform single sign-on authentication for its employees. Which evidence would most strongly explain the current integration weakness?
- Users can appear in both forests with different directory identifiers and conflicting group assignments.
- 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.
- Salesforce published an October 2026 retirement notice and limits Identity Connect to security updates for existing customers.
Explanation
Correct Answer
C:Best. The decisive observation is: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. This is why the design response should be: Separate directory user provisioning from federated authentication and document the relevant integration roles.
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 inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login.
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: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login.
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 inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login.
Question 497
Review this change: Separate directory user provisioning from federated authentication and document the relevant integration roles. It addresses a project where An enterprise expects Salesforce Identity Connect to perform single sign-on authentication for its employees. Which result should appear in integration acceptance evidence?
- Departing employees lose practical Salesforce access within the approved offboarding window.
- New users receive needed accounts and separately approved Salesforce entitlements.
- Existing subscribed synchronization remains governed while the enterprise builds a migration strategy.
- User records sync through a supported lifecycle process while SSO uses a defined trusted IdP.
Explanation
Correct Answer
D:Best. The verification target is: User records sync through a supported lifecycle process while SSO uses a defined trusted IdP. It tests whether the chosen approach—Separate directory user provisioning from federated authentication and document the relevant integration roles.—actually resolves the specific finding: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login.
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: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: User records sync through a supported lifecycle process while SSO uses a defined trusted IdP.
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: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: User records sync through a supported lifecycle process while SSO uses a defined trusted IdP.
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 inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: User records sync through a supported lifecycle process while SSO uses a defined trusted IdP.
Question 498
Suppose the integration design proceeds without correcting this issue: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. In the environment An enterprise expects Salesforce Identity Connect to perform single sign-on authentication for its employees. What should the risk register emphasize?
- 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 account-provisioning connector is incorrectly treated as the service that signs SAML assertions.
- A subscription expiration interrupts user onboarding because the old connector had no migration plan.
Explanation
Correct Answer
C:Best. The most direct failure is: An account-provisioning connector is incorrectly treated as the service that signs SAML assertions. It is a consequence of the documented condition: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. A mitigation is: Separate directory user provisioning from federated authentication and document the relevant integration roles.
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 inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: An account-provisioning connector is incorrectly treated as the service that signs SAML assertions.
B: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: The inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: An account-provisioning connector is incorrectly treated as the service that signs SAML assertions.
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 inherited environment actually uses Identity Connect for user synchronization and an independent SAML IdP for login. The direct answer here is: An account-provisioning connector is incorrectly treated as the service that signs SAML assertions.
Question 499
Salesforce and its partners face the following situation: A customer wants to replace manual Salesforce user creation from a Windows directory with a modern supported workflow. The integration review notes: A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. Which architectural step should take priority?
- Coordinate deactivation timing, access-token or session revocation and reconciliation independent of connector brand.
- Document its historical directory provisioning role and plan evaluation of supported alternative provisioning solutions.
- 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.
Explanation
Correct Answer
C:Best. The most direct action is to explain that Identity Connect historically synchronized AD identities, then compare supported provisioning alternatives. It is supported by the specific finding that A legacy architecture diagram proposes Identity Connect without considering the publisher's retirement guidance. The expected acceptance evidence is: The replacement plan keeps lifecycle synchronization without depending on new Identity Connect feature development.
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: Explain that Identity Connect historically synchronized AD identities, then compare supported provisioning alternatives.
B: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: Explain that Identity Connect historically synchronized AD identities, then compare supported provisioning alternatives.
D: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: Explain that Identity Connect historically synchronized AD identities, then compare supported provisioning alternatives.
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.