In a healthcare environment, identifyingwho is impactedduring a critical incident is essential to patient safety and continuity of care. Within theCommon Service Data Model (CSDM), the most effective way to determine impacted users is throughService Offerings, particularly when they are definedby department or location.
Service Offeringsrepresent how a service is consumed by specific user groups. In this case, a patient management system may have different offerings for departments such as Emergency, Inpatient Care, or Outpatient Services, or be scoped by hospital location. These offerings explicitly defineconsumer context, allowing incident responders to immediately identify which clinicians, staff, or facilities are affected.
Option D (Affected CI related list) identifies technical impact but does not translate that impact intouser or consumer context. Option A provides historical insight but does not identify current impacted users. Option C (service environment) helps differentiate production vs non-production but does not identifywhois impacted.
By leveragingService Offerings by Department or Location, the provider can quickly notify the right users, prioritize response based on clinical impact, and coordinate mitigation effectively-aligning with CSDM and ITIL best practices.
Therefore, the correct answer isB - Service Offerings by Department or Location.

On theCMDB Health DashboardinServiceNow, health metrics are grouped into three primary scorecards:
Completeness, Correctness, and Compliance. Each scorecard focuses on a distinct aspect of data quality.
Duplicate CIs,Orphan CIs, andStale CIsare all indicators ofdata accuracy and reliability, which fall under theCorrectnessscorecard.
Duplicate CIsindicate multiple records representing the same real-world item.
Orphan CIsare missing required relationships.
Stale CIshave not been updated within an expected timeframe.
All three conditions reflect whether the CMDB data iscorrect and trustworthy, not whether it is complete or policy-compliant.
TheCompletenessscorecard focuses on missing required attributes or relationships. TheCompliancescorecard evaluates adherence to policies such as certifications, lifecycle rules, or patch compliance.
Since leadership reporting typically focuses ontrust and accuracy of CMDB data, theCorrectness scorecardis the authoritative source for these metrics.
Therefore, the correct answer isB - Correctness.

InServiceNow, ingesting custom CIs must be done with a strong focus onupgrade safety, governance, and long-term maintainability. Data Foundations guidance explicitly discourages repurposing or overloading base classes, as this creates technical debt and upgrade risk.
Option Bis a best practice because theCMDB CI Class Models Storedelivers ServiceNow-supported CI classes that align with platform evolution. Before creating or extending classes, administrators should verify whether a suitable class already exists or has been introduced in newer releases. This avoids duplication and ensures future compatibility.
Option Dis also correct. When no suitable class exists, extending anexisting CI class(under the appropriate parent) to add required attributes preserves inheritance, discovery behavior, reporting, and upgrade compatibility. This approach is preferred over creating entirely new, disconnected schemas.
Option A is incorrect because repurposing base classes and renaming attributes breaks standard semantics, causes confusion, and complicates upgrades. Option C is incorrect because extendingAssettables to represent CIs conflates ITAM and CMDB concerns; assets and CIs serve different purposes and lifecycles.
Therefore, the solutions that minimize technical debt and ensure upgrade compliance areB and D.

Removing obsolete or inactive CIs from the CMDB must be handled carefully to avoid data loss, audit issues, and unintended operational impact. InServiceNow, the recommended and governed approach is to use anarchive policy.
Archive policiesare designed to manageCI lifecycle cleanupbased on defined conditions such as class, last updated date, lifecycle status, or operational state. In this scenario, the condition would targetLinux Server CIsthat have not been updated in six months. Archive policies can either archive or permanently delete records in a controlled, auditable manner, ensuring compliance with data retention and governance standards.
Creating abusiness rule(Option A) is strongly discouraged for bulk CMDB cleanup because it introduces technical debt, upgrade risk, and unpredictable side effects. Ascheduled job(Option C) may automate execution but lacks governance logic and lifecycle awareness on its own.
Archive policies integrate withCMDB Data Manager, provide visibility into actions taken, and support approval and rollback where appropriate. This aligns fully with Data Foundations best practices for maintaining alean, accurate, and trusted CMDB.
Therefore, the correct and recommended action isB - Create an archive policy.

InServiceNow, validating whether Configuration Items (CIs) still exist is a coreCMDB governanceactivity.
Over time, environments change rapidly-servers are decommissioned, cloud resources are torn down, and applications are replaced. If existence validation is not enforced, the CMDB quickly fills with obsolete or
"ghost" CIs.
Attestation policiesare specifically designed to address this need. An attestation policy automatically generates and assigns tasks to responsible users or groups, asking them toconfirm that a CI still exists and is still relevant. This process focuses on acknowledgment rather than deep data validation, making it lightweight and scalable across large CMDBs.
Certification policies (Option A) are used whenspecific attributes must be validated, such as lifecycle status, support group, or environment. While important for data correctness, certification is not intended solely to confirm CI existence. Delete (Option B) and Retire (Option C) policies are lifecycle actions that remove or transition records, but they do not validate existence before taking action.
Attestation integrates cleanly with CMDB Workspace, assigns tasks automatically, and supports auditability- ensuring accountability for CI ownership. This makes it the correct and Data Foundations-aligned policy type for validating CI existence.
Therefore,Option D - Attestationis the correct answer.