Explanation:

Within the Common Service Data Model (CSDM), service types are clearly defined to separate business- facing value, application logic, and technical enablement. Correct classification is foundational to impact analysis, ownership, reporting, and service visibility.
An Application Service is a logical representation of a deployed application or system stack. It models how an application runs, including servers, databases, middleware, and integrations. Application Services are typically created and maintained through Service Mapping and are primarily consumed by IT operations, DevOps, and support teams.
A Technology Management Service (also called a Technical Service) represents shared technical capabilities such as databases, authentication platforms, messaging systems, or cloud infrastructure. These services are published to Service Owners, not business users, and underpin one or more Application Services or Business Services. They are critical for understanding technical dependencies and risk but are not business-facing.
A Business Service is published to Business Users and directly supports business capabilities and outcomes. It represents what the business consumes , such as "Online Banking," "Order Fulfillment," or "Employee Onboarding." Business Services sit at the top of the CSDM hierarchy and are the anchor point for SLAs, experience, and value measurement.
Correctly distinguishing these service types ensures alignment with CSDM best practices, enables accurate impact analysis, and prevents common CMDB anti-patterns such as exposing technical services to business users or misrepresenting application stacks as business value.

In Data Foundations, "Govern" includes maintaining consistency between closely related data domains so that operational and asset lifecycle processes remain trustworthy. For hardware endpoints (and other asset-backed items), Asset and CI records often represent the same real-world item from two perspectives: financial
/lifecycle management (Asset) and operational/service context (CI). Automatic synchronization prevents drift such as different owners, locations, or statuses appearing in Asset vs CI, which can cause reporting errors, incorrect fulfillment decisions, and audit issues.
The platform supports synchronization through out-of-box synchronization logic (commonly implemented as business rules and related configuration) that updates the CI when an Asset changes, and updates the Asset when a CI changes-so the records stay aligned regardless of which team updates which record. Therefore, ensuring the Asset-to-CI update logic is active (A) and the CI-to-Asset update logic is active (B) is the right way to keep data synchronized automatically.
Option C is not required for synchronization; the intent is near real-time consistency driven by record changes, not batch jobs that run later. Scheduled jobs might exist for other maintenance activities, but they are not the primary mechanism for keeping Asset/CI synchronized. Option D is important as a data quality principle-ideally one Asset maps to one CI for physical items-but "ensuring one-to-one mapping" is not the automation mechanism itself. Automation is achieved through the active synchronization logic, which is why A and B are the correct answers.

A healthy and trusted CMDB that aligns with Data Foundations principles-covering accurate data ingestion, strong governance, and service-aware relationships-directly strengthens the insight available to Change Management. When discovered infrastructure data is integrated with well-maintained non-discoverable attributes (such as assignment groups, support groups, and ownership), the CMDB becomes a reliable source of truth for evaluating change risk and impact.
Option B is correct because Service Mapping establishes relationships between configuration items (CIs) and business services. This enables change practitioners to perform impact analysis, identifying which services, applications, and downstream components may be affected by a proposed change. Rather than relying on assumptions or tribal knowledge, change records can reference real dependency data, improving risk assessment, scheduling decisions, and stakeholder communication. This aligns directly with CSDM and CMDB best practices, where service context is essential for informed decision-making.
Option D is also correct because accurate, governed non-discoverable data-such as support and assignment groups-allows Change Management processes to dynamically route work. When a change is associated with a CI or service, the system can automatically populate the appropriate assignment group based on CMDB relationships. This improves efficiency, reduces manual errors, and ensures accountability across federated support models.
Options A and C are incorrect because a CMDB, regardless of maturity, cannot guarantee zero downtime, nor does it eliminate the need for human governance, approvals, and risk-based decision-making. Data Foundations enhance insight and control-not unchecked automation or absolute outcomes.

Explanation:

In ServiceNow, duplicate CI management spans detection, insight, and remediation:
The CMDB Health Dashboard - Correctness surfaces where duplicates exist and their impact, providing visibility and prioritization.
Certification Tasks support governed resolution, allowing assignment to individuals or groups to validate and correct data.
De-duplication Templates enable bulk remediation, ideal when standardized merge rules can be applied across many duplicates.
The Duplicate CI Remediator offers a guided, record-by-record wizard, preserving relationships and history for safer individual resolutions.
De-duplication Tasks are the work items generated by these processes, but they do not themselves represent an outcome-hence not applicable .
This mapping aligns with CMDB Data Foundations best practices, ensuring duplicates are identified, prioritized, and remediated efficiently and safely.

This question hinges on understanding class-specific Dynamic Reconciliation Rules in CMDB 360 / Multisource CMDB within ServiceNow.
Although two different dynamic rules are configured, the rule applied depends on the CI class being evaluated:
For the Server class, the configured rule is Largest value for the RAM attribute.
For the Windows Server class, the rule Most reported would apply-but only if the CI were evaluated as a Windows Server.
The question explicitly asks for the resulting RAM value for a Server CI, not a Windows Server CI.
Therefore, the Largest value rule governs the outcome.
Looking at the multisource values:
2,048 MB (LANDesk)
4,096 MB (Tivoli)
4,096 MB (ServiceNow)
8,192 MB (Altiris)
Under the Largest value dynamic reconciliation rule, the IRE selects the maximum numeric value, regardless of how frequently it is reported or which source provided it.
The Most reported logic (which would result in 4,096 MB) does not apply here because that rule is configured for a different class (Windows Server).
This scenario illustrates an important CMDB 360 principle: Dynamic reconciliation is evaluated per class, and child-class rules do not override parent-class rules unless the CI is actually classified under that child class.