Configuration Questions
Build and manage CMDB schema, CI classes, identifiers, relationships, CSDM data model setup, and CMDB Workspace configuration.
Newest question added: AI-assisted drafts, not yet individually reviewedHow questions are made
About Configuration
The Configuration domain covers the foundational setup of the CMDB — its schema, class hierarchy, CI relationships, and integration with the Common Service Data Model (CSDM). This includes understanding how to use CI Class Manager, configure CMDB Workspace, and set up the data model that underpins all other CMDB operations.
Why This Matters for Your Exam
Configuration accounts for 15% of the CIS-DF exam. You need to understand the CMDB class hierarchy, how CIs relate to each other, and how CSDM organizes services across domains. This is the foundation everything else builds on.
Key Concepts to Master
Focus on the CMDB schema model (cmdb_ci base class and extensions), CI Class Manager for managing classes, CSDM domains (Foundation, Design, Sell/Consume, Manage Technical Services, Manage Business Services), CMDB Workspace views, and CI relationships.
Exam Tips
Know the difference between CSDM domains and what lives in each. Understand the CMDB class hierarchy — which classes extend which. Be familiar with CMDB Workspace views (Home, My Work, CMDB 360, Insights, Management).
Practice Questions
29 questions availableA CMDB manager finds that teams record asset and CI status in different fields, so reports disagree about which items are in use or retired. Which Foundation domain feature does CSDM provide to fix this?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: A. Life cycle stage and life cycle stage status pairs
The Foundation domain defines life-cycle value pairs (Life cycle stage and Life cycle stage status) that track the life cycles of products, assets, contracts, CIs, locations and other objects. Using these standard values consistently lets reporting reflect the actual states of CIs, such as usage, availability and end of support.
- Why B is wrong: A value stream is the set of actions that add value to a customer from initial request to realization of value. It describes how value is delivered, not the status of individual assets or CIs.
- Why C is wrong: A CMDB group is a collection of CIs based on saved Query Builder queries, encoded queries or manual entries, used to act on many CIs at once. It does not give CIs a standard status.
- Why D is wrong: Product models in cmdb_model (and its product model classes) describe a specific version or configuration of a product and are referenced by CIs through Model ID. They do not track where each CI is in its life cycle.
A process owner at a bank is recording the credit check process as a sub-process of the customer onboarding process. How should this hierarchy be captured in the CSDM Foundation domain?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: C. Set the Parent attribute on the credit check process
Business processes are stored in the cmdb_ci_business_process table, and in a parent-child relationship a business process can be identified by using its parent attribute as a reference to a parent business process. Setting Parent on the credit check process to customer onboarding records the hierarchy.
- Why A is wrong: A contract is a binding agreement between two parties, stored in [ast_contract], and is not a CI. In Service Level Management, contracts group together SLAs for a single vendor or customer and the related CIs, locations, groups and users, not business process hierarchies.
- Why B is wrong: A CMDB group is a collection of CIs used to apply an action to all members at once. It does not express that one process is a child of another.
- Why D is wrong: A value stream is aligned with your organization's business processes, but it describes the actions that add value to a customer. It is not how a parent-child link between two processes is recorded.
A configuration manager compares the life cycle stage choices for a laptop CI with those for a software license, which is an intangible/logical item. Which stages exist for tangible/physical CIs but not for intangible/logical entities?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: C. Defective and Missing
The tangible/physical life cycle includes a Defective stage (devices that have failed and need repair or replacement) and a Missing stage (Lost or Stolen). The intangible/logical life cycle has Ideation, Purchase, Inventory, Design, Deploy, Operational, End of Operation and End of Life, but no Defective or Missing stage.
- Why A is wrong: Both life cycles include Purchase (On Order, Preallocated) and Inventory. For software, Inventory means licenses are available for assignment.
- Why B is wrong: Both life cycles include Ideation and End of Life. For intangible items, End of Life holds the Retired and Obsolete statuses.
- Why D is wrong: Both life cycles include Deploy (with a Test status for software) and End of Operation (with an On Hold status).