ServiceNow CIS-ITSM free question 10 / 10 · Domain 6: Configuration Management Database
An implementer is creating a custom CI class for load balancers and adding model-specific attributes. Which statement about the CMDB table structure in ServiceNow is correct?
- CI classes extend down from Configuration Item [cmdb_ci], inheriting attributes and adding their own
- CI classes extend the cmdb table directly, and cmdb_ci works as a view used only for reports
- Each CI class is a separate table with no link to cmdb_ci, and shared attributes are copied each time
- The class hierarchy has two fixed levels, hardware and software, and cannot be divided further
Show the answer and explanation
Answer: A
Why this is correct
The CMDB class hierarchy is a hierarchy of tables: Configuration Item [cmdb_ci] extends the Base Configuration Item [cmdb] class, and classes such as Hardware, Computer, and Server extend down from it. A child class inherits from its parent class, for example deriving its identification rule when it has none of its own.
Why the other options are wrong
"Each CI class is a separate table with no link to cmdb_ci, and shared attributes are copied each time" … Classes are linked through the hierarchy. Copying shared attributes into separate tables would let their meaning drift between classes.
"CI classes extend the cmdb table directly, and cmdb_ci works as a view used only for reports" … cmdb_ci is a class with its own attributes, and it is the class that extends cmdb. It is not a reporting view.
"The class hierarchy has two fixed levels, hardware and software, and cannot be divided further" … The hierarchy goes deeper, for example Hardware, Computer, and Server, and the CMDB CI Class Models app adds class models that extend it further.
Key point
When you create a custom class, extend the nearest existing class. Extending cmdb_ci directly would mean recreating attributes that could have been inherited.
Go to the ServiceNow CIS-ITSM practice app (10 free questions; purchase unlocks all questions)