ServiceNow Updated CIS-DF Exam Questions and Answers by jorgie

Data Foundations emphasizes that “ingest” must produce CMDB data that is standardized, supportable, and upgrade-safe. When introducing custom CIs, the best practice is to reuse the most appropriate existing CI class (or an approved industry-aligned model) and only add what is necessary—this keeps the data model aligned with platform expectations and reduces downstream rework.

Option B supports this directly: the CMDB CI Class Models application is intended to help teams select a suitable existing class rather than inventing new classes unnecessarily. Reusing existing classes improves consistency across integrations, Discovery/Service Mapping patterns, reporting, and CMDB Health rules—reducing technical debt and making future platform upgrades smoother.

Option A is also aligned with best practice when used correctly: once you have the right CI class, extending that class to add additional attributes (new fields) is a standard, upgrade-safe customization approach. It preserves the underlying platform data structures and avoids breaking out-of-box behaviors, identification/reconciliation practices, and CMDB Health evaluations.

Option C is not appropriate because Asset tables serve a different purpose (financial/lifecycle tracking) than CI tables (operational/service context). Mixing CI attributes into Asset classes creates confusion and process misalignment. Option D is strongly discouraged because repurposing and renaming base attributes creates long-term ambiguity, breaks shared semantics, and increases upgrade and maintenance risk.

Service Mapping (Top-down) → Recommended for mission-critical application services that require a precise approach using patterns

Tag-Based → Best fit to map cloud-native, container-based, or virtual machine environments

Service Mapping (Connection Suggestions) → Ideal for custom-built applications and leverages application fingerprinting to generate service maps in a timely manner

Dynamic CI Group → Ideal for small application services that can be easily grouped using filters and CMDB queries

In Data Foundations (CMDB + CSDM), an Application Service should be created using an approach that balances accuracy, speed, and maintainability, because the service map becomes the foundation for impact analysis, service visibility, and operational workflows.

Service Mapping (Top-down) is best for mission-critical services because it uses structured entry points and patterns to precisely discover infrastructure, dependencies, and communication paths. This produces high-fidelity maps suitable for strict governance, controlled change, and reliable outage impact analysis.

Tag-Based mapping is best for cloud-native and dynamic environments (containers, elastic virtual machines, and cloud resources) because tags/labels are the most stable identifiers in rapidly changing estates. It aligns well with modern cloud governance where ownership, environment, and service affiliation are expressed through standardized tagging strategies.

Service Mapping (Connection Suggestions) fits custom-built applications because it leverages observed connection data and application fingerprinting to propose likely dependencies. This accelerates service map creation when traditional pattern-first modeling would take longer, helping teams reach usable service visibility faster while still allowing validation and refinement.

Dynamic CI Group is ideal for smaller services where a full discovered map may be unnecessary. It groups CIs using filters and CMDB queries, providing a lightweight way to define “what’s in the service” for reporting, ownership, and basic impact without heavy mapping overhead.

The Unified Map is designed to provide enhanced visual insight and analysis across the CMDB by consolidating configuration item (CI) relationships from multiple sources—such as Discovery, Service Mapping, and manual relationships—into a single, interactive view. While traditional Service Mapping maps are optimized for modeling and understanding application-to-infrastructure dependencies, the Unified Map extends this capability with more flexible visualization and exploration features.

Option B is correct because the Unified Map allows users to zoom in and out, enabling both high-level overviews and detailed inspections of complex CI relationships. This capability is particularly valuable in large enterprise environments where services may span hundreds or thousands of infrastructure components. Zoom functionality supports impact analysis, troubleshooting, and architectural reviews without overwhelming the user with unnecessary detail.

Option C is also correct because the Unified Map supports filtering of map nodes based on user preferences. Administrators and analysts can filter by CI class, relationship type, lifecycle state, or other attributes, allowing them to focus on what is most relevant to their task—such as identifying only production CIs, security-relevant components, or a specific technology stack. This aligns strongly with Data Foundations principles by improving usability and decision-making without altering underlying data.

Option A is incorrect because modifying the number of levels displayed is a characteristic more closely associated with Service Mapping configuration rather than an added Unified Map capability. Option D is incorrect because visibility into an application and its host is a core Service Mapping function, not an enhancement unique to the Unified Map.

In summary, the Unified Map adds value by improving interactivity, flexibility, and user-driven insight across the CMDB.

In CSDM, Technology Services (and their Service Offerings) represent how technical capabilities are delivered and consumed by internal teams. When a server team requests a catalog item for infrastructure services (e.g., VM provisioning, storage, OS builds), the role responsible for initiating the request and defining requirements is the Technology Service Owner.

Technology Service Owners understand the operational capabilities, constraints, SLAs, and fulfillment workflows required to deliver infrastructure services. They define catalog requirements such as options, approvals, fulfillment tasks, and guardrails—ensuring the request aligns with standardization, security, and operational readiness.

Application Service Owners focus on how applications are delivered and supported, not on defining infrastructure catalog items. Enterprise Architects provide standards and guidance but do not initiate or define catalog request requirements.

Thus, the correct role is B – Technology Service Owners.