Question 10
Network switch records are missing a nonmandatory rack identifier that data stewards want measured for completeness without blocking inserts. A governance reviewer wants outcome evidence rather than a configuration screenshot. Which observation is decisive?
- Compare sample firewall, router, and switch records in the class tree and confirm the corresponding specialized fields.
- Check two different server subclasses to confirm both expose the same inherited support-tier field.
- Run the recommended-field completeness calculation and inspect switch CIs missing that field.
- Test two different host CIs with same adapter name and verify two correctly related adapter CIs rather than a false match.
Explanation
Correct Answer
C:This inspects an observable outcome of class-specific recommended attributes: Run the recommended-field completeness calculation and inspect switch CIs missing that field.
Incorrect Answers
A:Network CI subclasses retain the specialized attributes and reporting of each device class. That check cannot demonstrate the switch class's recommended rack-identifier completeness rule.
B:A field defined on the Server parent is available to its child server classes; sibling-only fields are not inherited. Verification of this result involves running the recommended-field completeness calculation and inspect switch CIs missing that field.
D:This inspects an observable outcome of dependent ci lifecycle: Test two different host CIs with same adapter name and verify two correctly related adapter CIs rather than a false match.
Question 11
After deployment for class-specific recommended attributes, the team sees: Records import successfully but the dashboard never reports missing rack values because no recommended field rule exists. What explains this failure?
- The ingestion classification ignored the corresponding network subclasses and collapsed their schemas.
- The rack attribute was not selected in the class recommended-fields configuration.
- Dependent identification lacked the containing server context needed to distinguish adapter identity.
- The new table did not extend the appropriate storage CMDB parent class included in those reports.
Explanation
Correct Answer
B:The rack attribute was not selected in the class recommended-fields configuration.
Incorrect Answers
A:The ingestion classification ignored the corresponding network subclasses and collapsed their schemas. That mechanism cannot explain the switch class's recommended rack-identifier completeness rule.
C:A dependent adapter CI is identified in the context of its containing host, so repeated adapter names need not collide. The evidence points to the rack attribute was not selected in the class recommended-fields configuration.
D:Storage CIs need their supported CMDB parent class to preserve fields and relationships used by storage reports. That mechanism cannot explain the switch class's recommended rack-identifier completeness rule.
Question 12
Network switch records are missing a nonmandatory rack identifier that data stewards want measured for completeness without blocking inserts. Which continuing operational safeguard most directly protects the intended outcome?
- Ensure the relationship to the correct parent is supplied whenever dependent CI payloads are ingested.
- Keep extensions within the intended class tree and document class ownership before changing inherited fields.
- Review the hierarchy and impact on all descendants before changing a shared parent-class field.
- Use recommendations for quality measurement and reserve mandatory dictionary constraints for truly required fields.
Explanation
Correct Answer
D:The recurring risk is controlled by Use recommendations for quality measurement and reserve mandatory dictionary constraints for truly required fields. It preserves the class-specific recommended attributes decision when data sources, policies or operational owners change.
Incorrect Answers
A:A dependent adapter CI is identified in the context of its containing host, so repeated adapter names need not collide. Preventing this failure involves using recommendations for quality measurement and reserve mandatory dictionary constraints for truly required fields.
B:Keep extensions within the intended class tree and document class ownership before changing inherited fields. It would leave use recommendations for quality measurement and reserve mandatory dictionary constraints for truly required fields without the specified safeguard.
C:Review the hierarchy and impact on all descendants before changing a shared parent-class field. It would leave use recommendations for quality measurement and reserve mandatory dictionary constraints for truly required fields without the specified safeguard.
Question 13
A ServiceNow team is evaluating cmdb class taxonomy. A discovery feed places firewalls, routers, and switches into one generic Computer class, losing type-specific attributes and reporting. What should it implement?
- Define the shared support-tier column on the suitable parent server class instead of separately cloning it on every child.
- Model the adapter as a dependent CI with the required host relationship and its class-dependent identification rule.
- Extend an appropriate existing CMDB database class in CI Class Manager and add only the justified new field.
- Map incoming device types to the matching existing network CI subclasses and extend only where no suitable class exists.
Explanation
Correct Answer
D:Network CI subclasses retain the specialized attributes and reporting of each device class.
Incorrect Answers
A:A field defined on the Server parent is available to its child server classes; sibling-only fields are not inherited. The missing change involves mapping incoming device types to the matching existing network CI subclasses and extend only where no suitable class exists.
B:A dependent adapter CI is identified in the context of its containing host, so repeated adapter names need not collide. The missing change involves mapping incoming device types to the matching existing network CI subclasses and extend only where no suitable class exists.
C:A database CI subclass inherits the Database parent schema while adding needed vendor fields. That does not establish accurate CMDB classification of the specific network device types.
Question 14
A discovery feed places firewalls, routers, and switches into one generic Computer class, losing type-specific attributes and reporting. After the implementation, what evidence most directly demonstrates the intended result?
- Run the recommended-field completeness calculation and inspect switch CIs missing that field.
- Inspect the new class hierarchy and verify that parent fields plus the patch-level attribute are present on a test CI.
- Compare sample firewall, router, and switch records in the class tree and confirm the corresponding specialized fields.
- Check two different server subclasses to confirm both expose the same inherited support-tier field.
Explanation
Correct Answer
C:Compare sample firewall, router, and switch records in the class tree and confirm the corresponding specialized fields.
Incorrect Answers
A:This inspects an observable outcome of class-specific recommended attributes: Run the recommended-field completeness calculation and inspect switch CIs missing that field. That check cannot demonstrate accurate CMDB classification of the specific network device types.
B:Inspect the new class hierarchy and verify that parent fields plus the patch-level attribute are present on a test CI. That check cannot demonstrate accurate CMDB classification of the specific network device types.
D:A field defined on the Server parent is available to its child server classes; sibling-only fields are not inherited. Verification of this result involves comparing sample firewall, router, and switch records in the class tree and confirm the corresponding specialized fields.
Question 15
The cmdb class taxonomy implementation shows an unexpected result: Network-device reports cannot distinguish firewall-specific properties because all devices were inserted into generic Computer. Which underlying defect should be corrected?
- The ingestion classification ignored the corresponding network subclasses and collapsed their schemas.
- The supposed dependency was never modeled as an actual typed cmdb_rel_ci relationship.
- The new table did not extend the appropriate storage CMDB parent class included in those reports.
- The field was placed on a child rather than the common parent, preventing inheritance across siblings.
Explanation
Correct Answer
A:The ingestion classification ignored the corresponding network subclasses and collapsed their schemas.
Incorrect Answers
B:Typed CMDB relationships connect CI endpoints with an explicit supported relationship type and direction. That does not establish the ingestion classification ignored the corresponding network subclasses and collapsed their schemas.
C:The failure is in the retaining cis in appropriate classes path, not simply a reason to rerun an unrelated dashboard. The evidence points to the ingestion classification ignored the corresponding network subclasses and collapsed their schemas.
D:The failure is in the inherited ci field change path, not simply a reason to rerun an unrelated dashboard.
Question 16
A discovery feed places firewalls, routers, and switches into one generic Computer class, losing type-specific attributes and reporting. Source owners and platform configurations can change. Which control is most relevant to this case?
- Evaluate the existing schema and report inclusion rules before adding a redundant class.
- Review the hierarchy and impact on all descendants before changing a shared parent-class field.
- Ensure the relationship to the correct parent is supplied whenever dependent CI payloads are ingested.
- Review canonical class models before inventing duplicate custom classes for known device types.
Explanation
Correct Answer
D:Network CI subclasses retain the specialized attributes and reporting of each device class. The necessary intervention is to review canonical class models before inventing duplicate custom classes for known device types.
Incorrect Answers
A:Evaluate the existing schema and report inclusion rules before adding a redundant class. That does not establish accurate CMDB classification of the specific network device types.
B:Review the hierarchy and impact on all descendants before changing a shared parent-class field. That does not establish accurate CMDB classification of the specific network device types.
C:A dependent adapter CI is identified in the context of its containing host, so repeated adapter names need not collide. The missing change involves reviewing canonical class models before inventing duplicate custom classes for known device types.
Question 17
During the dependent ci lifecycle design review, the team describes this situation: A network adapter is identified by its name only within its containing physical server; two servers can each have an adapter called eth0. Which change should be selected?
- Prefer the supported storage class and add extension fields only when a real domain distinction warrants inheritance changes.
- Define the shared support-tier column on the suitable parent server class instead of separately cloning it on every child.
- Model the adapter as a dependent CI with the required host relationship and its class-dependent identification rule.
- Map incoming device types to the matching existing network CI subclasses and extend only where no suitable class exists.
Explanation
Correct Answer
C:A dependent adapter CI is identified in the context of its containing host, so repeated adapter names need not collide. The missing change involves modeling the adapter as a dependent CI with the required host relationship and its class-dependent identification rule.
Incorrect Answers
A:Storage CIs need their supported CMDB parent class to preserve fields and relationships used by storage reports. That does not establish a host-dependent CI identity and relationship.
B:A field defined on the Server parent is available to its child server classes; sibling-only fields are not inherited. The missing change involves modeling the adapter as a dependent CI with the required host relationship and its class-dependent identification rule.
D:Network CI subclasses retain the specialized attributes and reporting of each device class. That does not establish a host-dependent CI identity and relationship.
Question 18
A network adapter is identified by its name only within its containing physical server; two servers can each have an adapter called eth0. A governance reviewer wants outcome evidence rather than a configuration screenshot. Which observation is decisive?
- Inspect the new class hierarchy and verify that parent fields plus the patch-level attribute are present on a test CI.
- Compare storage health fields, relationships, and reports before and after the representative import.
- Run the recommended-field completeness calculation and inspect switch CIs missing that field.
- Test two different host CIs with same adapter name and verify two correctly related adapter CIs rather than a false match.
Explanation
Correct Answer
D:This inspects an observable outcome of dependent ci lifecycle: Test two different host CIs with same adapter name and verify two correctly related adapter CIs rather than a false match. Verification of this result involves testing two different host CIs with same adapter name and verify two correctly related adapter CIs rather than a false match.
Incorrect Answers
A:Inspect the new class hierarchy and verify that parent fields plus the patch-level attribute are present on a test CI. That check cannot demonstrate a host-dependent CI identity and relationship.
B:Storage CIs need their supported CMDB parent class to preserve fields and relationships used by storage reports. That check cannot demonstrate a host-dependent CI identity and relationship.
C:Recommended CMDB fields measure class-specific data completeness without making the attribute mandatory. Verification of this result involves testing two different host CIs with same adapter name and verify two correctly related adapter CIs rather than a false match.
Question 19
After deployment for dependent ci lifecycle, the team sees: An adapter was merged into another host's adapter because the feed omitted the hosting parent reference. What explains this failure?
- The custom table was created outside the CMDB class hierarchy, so it cannot inherit the parent CI schema.
- The field was placed on a child rather than the common parent, preventing inheritance across siblings.
- Dependent identification lacked the containing server context needed to distinguish adapter identity.
- The new table did not extend the appropriate storage CMDB parent class included in those reports.
Explanation
Correct Answer
C:Dependent identification lacked the containing server context needed to distinguish adapter identity.
Incorrect Answers
A:The custom table was created outside the CMDB class hierarchy, so it cannot inherit the parent CI schema. The underlying failure instead involves dependent identification lacked the containing server context needed to distinguish adapter identity.
B:A field defined on the Server parent is available to its child server classes; sibling-only fields are not inherited. The underlying failure instead involves dependent identification lacked the containing server context needed to distinguish adapter identity.
D:Storage CIs need their supported CMDB parent class to preserve fields and relationships used by storage reports. That mechanism cannot explain a host-dependent CI identity and relationship.
Question 20
A network adapter is identified by its name only within its containing physical server; two servers can each have an adapter called eth0. Which continuing operational safeguard most directly protects the intended outcome?
- Ensure the relationship to the correct parent is supplied whenever dependent CI payloads are ingested.
- Review the hierarchy and impact on all descendants before changing a shared parent-class field.
- Evaluate the existing schema and report inclusion rules before adding a redundant class.
- Keep extensions within the intended class tree and document class ownership before changing inherited fields.
Explanation
Correct Answer
A:Long-term integrity for dependent ci lifecycle depends on Ensure the relationship to the correct parent is supplied whenever dependent CI payloads are ingested.
Incorrect Answers
B:Review the hierarchy and impact on all descendants before changing a shared parent-class field. It would leave a host-dependent CI identity and relationship without the specified safeguard.
C:Evaluate the existing schema and report inclusion rules before adding a redundant class. It would leave a host-dependent CI identity and relationship without the specified safeguard.
D:Keep extensions within the intended class tree and document class ownership before changing inherited fields. It would leave a host-dependent CI identity and relationship without the specified safeguard.
Certified Implementation Specialist - Data Foundations (CMDB and CSDM) (CIS-DF) Practice Tests