InServiceNow, Dynamic CI Groups are a coreData Foundationscapability used to automatically manage CI membership based on rules rather than manual maintenance. WhenTechnology Management Service Offerings (Technical Service Offerings)are related to Dynamic CI Groups, ServiceNow uses those relationships tosynchronize operational support attributesto the member CIs.
The two CI attributes that are intentionally designed to sync in this model are theManaged by Groupand theSupport Group. These groups directly influenceoperational ownership and support routing, which is why they are automatically aligned when Dynamic CI Groups are used. This ensures that incidents, changes, problems, and operational tasks are routed consistently as CI membership changes over time.
TheSupport Groupdefines who provides day-to-day operational support and is critical for Incident and Request Management workflows. TheManaged by Grouprepresents the team responsible for the technical lifecycle and operational health of the CI. Synchronizing these attributes eliminates manual updates and reduces misrouted tickets, which is a key goal of Configuration Management maturity.
TheApproval Group(Option A) is not synced because approvals are process-driven and often context-specific rather than CI-driven. Similarly, theOwned by Group(Option C) represents accountability or financial ownership, which is intentionally decoupled from dynamic operational grouping to avoid unintended governance changes.
Therefore, the correct answers areB (Managed by Group)andD (Support Group).
