{"id":4239,"date":"2026-10-13T08:17:40","date_gmt":"2026-10-13T08:17:40","guid":{"rendered":"https:\/\/www.examtopics.biz\/blog\/servicenow-cis-df-data-manager-attestation-certification-retirement\/"},"modified":"2026-10-20T18:25:36","modified_gmt":"2026-10-20T18:25:36","slug":"servicenow-cis-df-data-manager-attestation-certification-retirement","status":"publish","type":"post","link":"https:\/\/www.examtopics.biz\/blog\/servicenow-cis-df-data-manager-attestation-certification-retirement\/","title":{"rendered":"ServiceNow CIS-DF: Data Manager Attestation and Retirement"},"content":{"rendered":"

Retiring a CI is not the same as deleting its evidence. Imagine a fleet of virtual servers: some are decommissioned, others have not reported because a connector failed, and a third group still supports a regulated service whose history must be retained. A Data Manager policy needs a class-specific retirement definition, review owner, proposed outcome, exclusions and verification of dependent records before it can safely archive or remove anything. An unused-looking CI may remain relevant to incidents, changes or service mappings. In Independent CIS-DF lifecycle-governance practice cases<\/a>, compare attestation, certification, retirement, archival and deletion by the evidence required and reversibility of the operation. The official ServiceNow blueprint determines the exam scope; a third-party question offering cannot prove that a live retention policy was executed safely.<\/p>\n

CMDB Data Manager<\/a> provides a policy-driven approach to attestation, certification and lifecycle operations. These actions have distinct meanings and prerequisites. The right choice depends on whether the business needs a human to confirm existence, a reviewer to verify attribute values, or an approved process to retire, archive or permanently remove configuration records. A safe implementation names who makes each decision, how exceptions are handled and what happens to dependent CIs.<\/p>\n

Separate attestation from certification<\/h2>\n

Attestation asks an authorized reviewer to confirm whether an object or infrastructure element still exists or remains valid for the organization. Certification focuses on whether selected attributes have correct values under a defined standard. These are not synonyms. A team can agree that a server exists while rejecting the support group currently shown on its CI. Conversely, an attribute can have a plausible value on a stale CI that should no longer represent an active system.<\/p>\n

In a synthetic data-center review, assign attestation of a group of hosts to the infrastructure owner, and certification of business-criticality fields to the accountable service manager. The output should distinguish accepted records, rejected records, missing responses and exceptions needing additional evidence. The CMDB Data Manager policy documentation<\/a> supports both kinds of policy, including assignment of reviewers and certification-field choices. Verify the target release’s supported policy settings before defining the process.<\/p>\n

Understand retire, archive and delete as different operations<\/h2>\n

Retiring a CI marks its lifecycle state as retired according to the configured rules, while keeping it present for relevant views and health processes. Archiving moves eligible retired records out of active CMDB tables for a retention interval, with restoration available during that interval under the documented archiving capability. Deleting permanently removes the target CI from its active record set and should be approached as an irreversible operation. A request to make a dashboard cleaner is not sufficient justification for deleting operational evidence.<\/p>\n

The ServiceNow Data Manager overview<\/a> explains these differences and the supported types of policy. In the data-center example, an old VM that still supports a historical investigation may be a candidate for retirement or controlled archival, not immediate deletion. A second record that refers to a real active server but has not been discovered due to expired credentials should not be treated as retired at all. Design the decision path to recognize those cases.<\/p>\n

Configure retirement definitions before lifecycle policies<\/h2>\n

The Retire, Archive and Delete policy types require an active retirement definition for each targeted class. ServiceNow retirement definitions<\/a> determine how a particular class is considered retired, including inheritance or specific rules for relevant subclasses. Without that definition, attempts to create some lifecycle policies can fail or target a population incorrectly. An administrator should confirm the configuration rather than guessing that a generic status string is always sufficient.<\/p>\n

Design a class matrix for virtual machines, databases and network components<\/a>. Record how retirement is represented, which inherited definitions apply and which classes need their own lifecycle interpretation. Test a filter selecting a CI not yet retired and a second filter selecting an already retired CI. Then verify that the policy affects only the expected population. A broad inherited rule can be convenient but dangerous when a subclass has a materially different lifecycle or dependencies.<\/p>\n

Preview targeted records and protect exceptions<\/h2>\n

Before a policy can be published, inspect the population that matches its class and conditions, the assigned reviewers, approval configuration and exclusions. The Data Manager interface includes included and excluded record handling for supported policy types. A small mistake in a date comparison or status filter can target thousands of CIs. A preview is therefore a safety boundary, not just a step required by a wizard.<\/p>\n

Imagine a batch that accidentally selects all devices without recent discovery, including a lab network that is purposely isolated from automated collection. Exclude those items through an approved rule or correct the policy scope, then document the reason so an operator does not silently reinclude them during a later revision. Assign policy decisions to a real group with business context. When the relevant \u201cManaged by Group\u201d value is missing, ServiceNow may route approval work to an administrator, a fallback that creates bottlenecks if data ownership is incomplete.<\/p>\n

Define task ownership, approvals and evidence<\/h2>\n

A policy that automatically assigns tasks has not delegated accountability unless the receiving team can make and document a legitimate decision. The reviewer needs to know which source last reported the CI, its service dependencies, proposed lifecycle action and business impact. High-consequence deletion or archiving may require additional approval beyond the default process, especially when the affected CI is part of a regulated or customer-facing service.<\/p>\n

Keep the policy version, target evaluation, assigned task, approval result and actual lifecycle change tied to stable identifiers. Do not present a scheduled job’s successful completion as proof every record was appropriate for deletion. Check the final CI state and any relation-handling logs. Design escalation for missing owners and overdue tasks, and ensure that an exception does not silently become a permanent bypass of governance. This is where CMDB stewardship becomes an operational role rather than a title in a responsibility chart.<\/p>\n

Protect dependent CIs and service relationships<\/h2>\n

A server CI can host components or depend on shared infrastructure. Retiring, archiving or deleting it may leave dependent records and relationships in an inconsistent state if the data model and lifecycle policy are not coordinated. ServiceNow documents dependent CI handling and policy processing for related entries; the correct behavior depends on the configured classes, retirement definitions and relevant features. Never infer that removing one parent row safely removes all descendants and preserves audit needs automatically.<\/p>\n

Build a synthetic topology with a host, its network adapters, a runtime application component and a service offering<\/a> that depends on the runtime service. Propose retiring the host. Review which dependent records should retire, remain visible, be investigated or be reassigned. An archival task that causes a service-impact map to lose its only known connection may require controlled relationship cleanup before approval. Use test instances and rollback evidence for these cases; do not run destructive experiments against real customer data.<\/p>\n

Schedule processing without mistaking scheduling for governance<\/h2>\n

Published lifecycle policies are processed by relevant Data Manager jobs, and documentation describes different processing behaviors for Retire versus Archive and Delete. There are operational controls for task staleness and policy execution, but the existence of a scheduled job does not imply that target records have been validated, approved or successfully changed. Confirm job health, run history, exception counts and the final state of sampled CIs.<\/p>\n

Measure the age of queued decisions, the percentage rejected because the owner could not be found, and reappearance of CIs after retirement. A discovery source might restore a CI’s old state if source and lifecycle contracts are not aligned. Investigate that condition before changing a deletion rule. Also review performance implications for large policy batches and retention obligations. The objective is predictable lifecycle management that survives failures, not the largest possible number of records removed per day.<\/p>\n

Test a Data Manager policy with reversible scenarios<\/h2>\n

A useful acceptance dataset has an active server, a definitively decommissioned server, a stale-looking server with a failed collector, a retired CI that must be archived, and a CI with an unsettled dependent relationship. For each, record expected actions and who must approve them. Run the assessment path in a safe nonproduction instance, verify task assignment, exclusions, state changes and the effect on reports. Test a missing approver and a rejected task rather than designing solely for a yes-to-everything demonstration.<\/p>\n

The most valuable control in a lifecycle policy review can be a counterexample. Include one CI whose last discovery is old because a site lost network connectivity, one whose source is authoritative and confirms decommissioning, and one whose service owner refuses retirement because a dependency remains. A valid procedure handles all three differently even if a simple stale-age filter selects them together. Record why an approved exception was retained and when it must be revisited. This reduces the temptation to treat a policy preview as permission to remove an entire batch without reviewing the operational cost of a mistake.<\/p>\n

The broader ServiceNow CMDB Health article<\/a> explains quality indicators, but it should not be confused with lifecycle policy authority. A stale record can be a candidate for investigation without yet being a valid delete target. CIS-DF implementation readiness means understanding that attestation establishes continued existence, certification checks business-critical attributes, retirement changes lifecycle state, archival retains recoverable history temporarily, and deletion requires an explicit irreversible decision. Every action should be grounded in source evidence, approval and its effect on the service model.<\/p>\n","protected":false},"excerpt":{"rendered":"

The CMDB accumulated twelve years of virtual servers. Many are no longer active, but some still appear on dashboards and incident forms; others have no clearly assigned owner. A cleanup<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29,34,54],"tags":[],"class_list":["post-4239","post","type-post","status-publish","format-standard","hentry","category-certifications","category-data-engineering-analytics","category-servicenow-certifications"],"_links":{"self":[{"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/posts\/4239","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/comments?post=4239"}],"version-history":[{"count":3,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/posts\/4239\/revisions"}],"predecessor-version":[{"id":5551,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/posts\/4239\/revisions\/5551"}],"wp:attachment":[{"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/media?parent=4239"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/categories?post=4239"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examtopics.biz\/blog\/wp-json\/wp\/v2\/tags?post=4239"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}