Foundational Data Management Questions
Learn to manage foundational data across domains including reference data, choice lists, and shared configurations.
Newest question added: AI-assisted drafts, not yet individually reviewedHow questions are made
About Foundational Data Management
Foundational data includes reference data that may need to be shared across domains or domain-specific. Managing this data correctly ensures proper system behavior across all tenants.
Why This Matters for Your Exam
Foundational Data Management represents 20% of the CIS-SP exam. Understanding how to handle shared vs domain-specific data is crucial.
Key Concepts to Master
Know how to configure tables for domain separation, understand reference field behavior across domains, and learn about choice list domain separation.
Exam Tips
Remember that not all tables need domain separation. Know which system tables are typically domain-separated and how reference fields resolve across domain boundaries.
Practice Questions
20 questions availableIn a domain-separated GRC implementation, how is the domain determined for records that are automatically generated based on their parent object?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: C. Records inherit the domain of their parent object or creating user's domain
Records that are automatically generated either through scheduled jobs or background scripts are domain separated based on their parent object or user domain for all Policy and Compliance objects. Controls, risks, or risk assessments that are auto-generated based on the entities must also be domain separated following this rule.
- Why A is wrong: Domain assignment is deterministic based on parent object or user, not random
- Why B is wrong: There is no rule to place records in the lowest domain; it's based on parent/user domain
- Why D is wrong: Auto-generated records do not default to global domain; they follow parent/user domain
Which tables are used for reconciliation rules and DO have sys_domain, sys_overrides, and sys_domain_path fields? (Choose three)
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: A. Reconciliation Definition (cmdb_reconciliation_definition); C. Datasource Precedence (cmdb_datasource_precedence); E. Data Source Staleness Definitions (cmdb_datasource_staleness)
The reconciliation definition rules that are used during the reconciliation process can be defined for different domains. Tables with sys_domain field include: Reconciliation Definition (cmdb_reconciliation_definition), Datasource Precedence (cmdb_datasource_precedence), and Data Source Staleness Definitions (cmdb_datasource_staleness).
- Why B is wrong: Identifier (cmdb_identifier) does NOT have a sys_domain field; identification rules are global
- Why D is wrong: Identifier Entries (cmdb_identifier_entry) does NOT have a sys_domain field; these are global
How does the CMDB Health dashboard handle domain separation when displaying health failures and scores?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: A. It aggregates and reports based on user's domain visibility of CIs
If the Domain Support — Domain Extensions Installer plugin is activated, then the CMDB Health dashboard is domain aware. It aggregates and reports health failures and scores based on user's domain visibility of CIs. If domain visibility lets a user see a CI, then the audit rule in that user's domain applies to that CI.
- Why B is wrong: Domain filtering is automatic based on user visibility, not manual
- Why C is wrong: The dashboard shows data for the user's visible domains, not only global
- Why D is wrong: The dashboard respects domain visibility; it does not show all CI data