Database Management and Platform Security
About 30% of the CSA exam — see all 6 domains.
What this domain covers
- Data Schema
- Application/Access Control
- Importing Data
- CMDB and CSDM
- Security Center
- Shared Responsibility Model
What it covers: the data schema, access control (ACLs), importing data, the CMDB/CSDM, the Security Center, and the shared responsibility model. Spend the most time here.
Data schema:
- Data is stored in tables; each row is a record, each column a field. Every table has a unique sys_id per record.
- Table extension (inheritance): a child table inherits all fields of its parent and adds its own. Example: Incident, Problem, and Change all extend Task. The CMDB base class is cmdb_ci.
- Field types matter: String, Choice, Reference, Date/Time, True/False, Journal, etc. A Reference field points to a record on another table; dot-walking lets you traverse from a reference to fields on the related record (e.g.,
caller_id.email).
Access control (security):
- Roles are containers of permissions assigned to users (directly or via groups).
admin,itil, etc. - Access Control Rules (ACLs) secure operations on tables/fields. An ACL is evaluated on table.field for an operation (read, write, create, delete). To grant access, the user must pass the required roles AND the condition AND the script — but within the required-roles list the logic is OR (holding any one listed role satisfies the role check; an empty role list passes that check). For field access ServiceNow uses a two-gate model: the table (row) ACL is evaluated first — if it fails, all fields are denied — and only if it passes is the field ACL evaluated; the user must pass both. (The phrase "most specific to most general" describes how candidate rules are matched to one object within a gate, not the table-then-field sequence.)
- Contextual security: ACLs are the foundation. If no matching ACL grants access, access is denied by default.
Importing data: the standard path is Import Set → Transform Map → target table.
- An Import Set is a staging table that temporarily holds incoming rows (from Excel/CSV/JDBC/web service).
- A Transform Map defines how staging columns map to target table fields, including coalesce (a field used to match existing records so imports update rather than duplicate) and field maps.
- Data sources define where the data comes from for scheduled/automated imports.
CMDB and CSDM:
- The CMDB stores Configuration Items (CIs) and their relationships, all extending cmdb_ci.
- CSDM (Common Service Data Model) is the standard, prescriptive framework for how to structure service and CI data in the CMDB.
Security Center gives a centralized view of the instance's security posture. The Shared Responsibility Model clarifies what ServiceNow secures (the platform/infrastructure) versus what the customer secures (their configuration, data, access, and integrations).
Sample questions from this domain
Three of the 90 in this domain, with the reasoning. The full set is in the question bank.
Incident, Problem, and Change Request all share fields such as Number, State, and Assigned to. What is the underlying reason these fields are common to all three?
- A. They are all in the same update set
- B. They all extend the Task table ✓
- C. They are all connected by a single business rule
- D. They all share one sys_id
Why: Incident, Problem, and Change extend the Task (task) table through table inheritance, so they inherit Task's fields. Each record still has its own unique sys_id. Business rules and update sets do not create shared schema.
A field on a form is a reference field pointing to the Caller (User) record. The admin wants to display the caller's email on the form without copying the value. What technique retrieves the email from the referenced User record?
- A. Coalescing
- B. Impersonation
- C. Dot-walking ✓
- D. Cascading delete
Why: Dot-walking traverses a reference field to access fields on the related record, e.g., caller_id.email. Coalescing matches records during import, impersonation is a security/testing feature, and cascading delete propagates record deletion.
When a user requests a record operation, ServiceNow evaluates Access Control Rules (ACLs). If NO matching ACL grants the user access to that operation, what happens by default?
- A. Access is granted because no rule denied it
- B. Access is denied by default ✓
- C. The record is deleted
- D. The admin role is automatically applied
Why: ServiceNow access control is deny-by-default: if no matching ACL explicitly grants access, the operation is denied. A matching ACL must satisfy both its required role(s) and its condition/script to allow access.