125 questions from the Database Management and Platform Security domain of the ServiceNow Certified System Administrator (CSA) exam, each with its answer and an explanation. Read them through as revision, then sit the full practice exam to test yourself on them under multiple-choice conditions.
Answer
Task [task] is one of the core tables provided with the base system. It provides a series of standard fields used on each of the tables that extend it, such as Incident [incident] and Problem [problem].
Answer
Contextual security secures data and records via create, read, write and delete permissions using Access Control Lists, giving control at every level.
Answer
Task is the base/parent table holding common fields such as assignment, state and priority. Incident is a child table that extends Task, inheriting its fields and adding incident-specific ones.
Answer
The CI Relationship table in a ServiceNow instance is cmdb_rel_ci.
Answer
Table rotation protects instance performance when querying growing data sets by using the ECC Queue and the sys_created_on field to split data into multiple tables by date.
Answer
Incident, Problem and Change all extend Task. Task is the parent table, so most fields on those forms are derived from it.
Answer
sys_db_object is the master table holding a record for every table in the database, including custom tables and extensions, along with metadata such as name, label and parent table. sys_master_db and sys_master_object do not exist.
Answer
Users can hold multiple roles and belong to multiple groups, so the relationship is many to many.
Answer
A database view defines table joins for reporting purposes. Several useful views ship with the Database View and Database Views for Service Management plugins; for example, one can join Incident to Metric Definition and Metric Instance.
Answer
cmdb_ci stores the basic attributes of all configuration items. cmdb is the base CMDB table for non-IT CIs, cmdb_rel_ci holds CI relationship data, and cmdb_ci_config_file is one of the CI types.
Answer
A user can hold multiple roles (itil, admin, catalog_admin) and can also belong to multiple assignment groups used to route tasks to the right team, so the single-group claim is false.
Answer
The system dictionary is the Dictionary Entry [sys_dictionary] table, holding details for each table and the definition of every column. Each row represents a table or a column, and admins use it to modify tables and fields, which in turn define lists and forms.
Answer
Impersonation is restricted to users with the admin role or specific elevated privileges. It is a troubleshooting and testing capability, limited for security reasons.
Answer
Instance access can be limited by IP ranges defined in whitelisted IP fields.
Answer
CI Attestation lets owners systematically confirm and validate CIs in bulk so the CMDB reflects reality. Multisource Report Builder is for reporting, Service Graph Connectors and IntegrationHub ETL bring in external data, and IRE reconciles data to avoid duplicates.
Answer
The report_view operation is a record-type ACL restricting report access to users with the required roles. There are two kinds: report_view table ACLs, which block report content based on the specified table, and report_view field ACLs, which block reports using the specified field in a group by, row, column or aggregation.
Answer
Child classes derive fields from parent classes, so a dictionary-level change on Task applies to every table extending it, such as Incident.
Answer
Adding a new field to a parent table means it is automatically inherited by all child tables.
Answers
The four supported schema relationship types are Referenced by, Referencing, Extended by, and Extending.
Answer
report_view controls who can view reports on a table, matching the governance requirement. report_on governs creating reports, add_to_list governs adding records to a list, execute applies to scripts, and read covers records and fields rather than report viewing.
Answer
CI Class Manager lets administrators configure CI classes and manage identification rules, including adding related entries for IRE rules. IntegrationHub ETL and Service Graph connectors bring in external data, and CMDB Data Manager handles CI data lifecycle and governance.
Answer
Contextual security protects records based on their contents and table hierarchy, with access control rules definable at any level (table, field, or record), giving fine-grained, hierarchy-aware security enforcement.
Answer
Go to the syslog.list and set the source to "Impersonate" to find the details.
Answer
A field is the component of a table storing a single piece of data for one record; each record consists of multiple fields corresponding to columns, such as Number, Short Description, or Priority on an Incident table.
Answers
By default, admin, public, nobody, and role_delegator cannot be delegated; a user with the role_delegator role cannot delegate that role to other group members.
Answer
Users can be brought into ServiceNow via SSO, LDAP, user authentication (manual or automatic), and import sets.
Answer
Single sign-on (SSO) is an authentication scheme letting a user log in once with a single ID and password to access several related, independent software systems.
Answer
ESS users (end-user employees) are the largest group, followed by ITIL fulfillers (IT/HR staff), then Delegate Administrators with elevated but limited privileges, and finally System Administrators, which should be the smallest group per least-privilege security practice.
Answer
CMDB Data Manager requires active life-cycle rules defined for the target classes so CIs follow proper governance and lifecycle transitions; without them, the tool cannot enforce or manage CI data properly. CSDM setup, migration activities, and the CSDM Activation plugin are not required prerequisites.
Answers
The ITIL role grants Service Desk/technician access to open, update, and close incidents, problems, changes, and CIs. Without it directly or via group membership, a user only sees the Self Service view.
Answer
The label is the user-friendly reference shown on forms and lists, while the name (system name) is the backend reference used in scripts and queries — e.g. label "Assigned To" with backend name assigned_to.
Answer
Not all tables can be extended; core system tables (like sys_user, sys_audit, sys_db_object) and certain non-extensible base tables are restricted from extension to preserve platform integrity. Only tables designed to be extensible (like Task, CMDB, Incident) can be extended.
Answer
A base table is the original table not extending any other table, though other tables can extend it; it serves as the starting point for extensions.
Answer
ServiceNow restricts impersonation of Extended Security Admin users, since these have elevated privileges tied to system security and impersonating them could compromise sensitive configurations or bypass safeguards. Even with the Impersonate role, this type cannot be impersonated.
Answer
CSDM provides a standardized blueprint defining how services, applications, and infrastructure should be represented in the CMDB, ensuring consistency across ITSM, ITOM and other ServiceNow products. The CMDB is the repository, while CSDM is the model/blueprint for structuring it.
Answer
Since tickets need to be assigned and tracked like tasks, best practice is to extend the Task table, inheriting assignment, SLA, and workflow functionality, and then add custom inventory specification fields.
Answer
The String field type allows free-form entry of letters, numbers and special characters; single-line and multi-line are presentation styles of a String field, not separate field types.
Answer
The security_admin role is an elevated privilege role provided with High Security Settings that lets users create and change access controls and modify High Security Settings.
Answer
Application Scope defines the boundaries of an application, restricting access to files, data and resources within that scope so only authorized components can interact with it, preventing unintended access from other applications.
Answer
Activating the glide.sys.log_impersonation property causes every impersonation event to be logged, capturing the impersonator and impersonated user, viewable in System Logs. Update sets are for moving configuration, not monitoring activity, and there is no role or right-click option for this purpose.
Answers
CMDB Data Manager handles large volumes of data for bulk updates, imports, and reconciliations, and its primary purpose is ensuring data integrity, consistency and accuracy, keeping the CMDB healthy and efficient. It is designed to handle dynamic cloud environments and enterprise-sized CMDBs, not just small/medium ones.
Answer
Database Views join data from multiple tables (like Incident and SLA) into a single reporting structure without altering the underlying schema, enabling reports like incidents resolved by SLA per category.
Answer
Administrators can impersonate other authenticated users for testing purposes and can view impersonation logs afterward.
Answer
The Task table's internal name is simply task, serving as the parent table for Incident, Problem, Change Request, and Service Catalog Task. sys_ prefixes are reserved for platform tables, not core application tables like this.
Answer
sys_user_group stores all group records including name, description, manager, type and roles, serving as the repository for group definitions used in assignment rules, notifications, and access control.
Answer
Access Control Lists (ACLs) are the mechanism for controlling access to data and functionality, including restricting which roles or users can execute scripts, query, or update records on a table.
Answer
A CMDB provides visibility, traceability, and impact analysis, but it does not automatically resolve incidents — that requires separate workflows or human intervention. Change impact analysis, correlating failed changes with incidents, and reducing downtime are all genuine CMDB benefits.
Answer
Fulfiller users are typically assigned both the itil role (for ITSM tasks) and the approver_user role (to approve requests or changes), letting them both fulfill and approve requests when required.
Answer
The table-level ACL is the minimum requirement for record access — if it fails, the user cannot access the record at all regardless of field ACLs. Once the table ACL passes, field ACLs may further restrict access to specific fields.
Answer
sys_user is the table used to store users; there are no tables named system_user, user, or users.
Answer
Each record is identified by a unique 32-character GUID called the sys_id, guaranteeing every record in every table across every instance in the world has a unique identifier.
Answer
ServiceNow leverages a relational database management system (RDBMS), organizing data into tables with rows and columns to enable efficient querying and relationships.
Answer
ServiceNow enforces a layered ACL evaluation: the table ACL grants access to the table itself, and field ACLs then control visibility of individual fields. Failing a field ACL only hides that field, not the whole table.
Answer
Roles can be assigned to groups or individual users, though best practice recommends assigning roles to groups rather than individual users.
Answer
CIs are the building blocks of IT services — hardware, software, infrastructure, documentation, or processes — that need to be tracked and managed to deliver functionality, not just generic settings or every ServiceNow component.
Answer
The CMDB is NOT a static list — it tracks CIs within the platform and also tracks the relationships between them dynamically.
Answer
The CI Relationship Editor provides a graphical way to view existing relationships between CIs and establish new ones, helping teams understand dependencies and interactions between components.
Answer
ServiceNow supports OAuth for API/third-party integrations, SAML for SSO, LDAP for directory authentication, and digest-based authentication for integrations — all listed methods are supported.
Answer
ACLs enforce security and governance at the table, field, and record level, determining who can read, write, or execute specific fields based on roles and conditions — unlike UI Policies, Client Scripts, or Data Policies which are not true security mechanisms.
Answer
ServiceNow tracks actions performed while impersonating another user via audit logs, so the feature is traceable and safe to use for testing and troubleshooting.
Answer
A Dependency View graphically depicts CIs, the services they are part of, and the services they support, helping users understand potential impact via relationships rather than merely listing all CIs or incidents.
Answers
The three key field attributes are Label (user-friendly display name), Name (internal system identifier), and Value (the actual stored data for a record).
Answer
Roles are stored in the sys_role table, controlling access to features and capabilities in applications and modules.
Answer
A reference field stores a reference to a record on another table, e.g. the Caller field on Incident referencing the User table.
Answer
The "u_" prefix is the standard used for custom tables created in the global scope, helping avoid naming conflicts with system tables.
Answer
The Configuration Management Database (CMDB) is the core repository storing all configuration items — hardware, software, and business services — providing a comprehensive, centralized view.
Answer
Tables are the relational database structure storing data in rows and columns; lists and forms are interfaces for viewing/interacting with that data, not the storage mechanism itself.
Answer
Assigning roles to groups rather than directly to individual users is a ServiceNow best practice. It simplifies administration, ensures consistency, and makes role management more scalable.
Answer
Access Control Rules (ACLs) are security rules that determine whether a user can access a particular row (record) or column (field) in a table, evaluated whenever access is attempted.
Answer
Out-of-the-box tables come pre-configured with ServiceNow; 'incident' is a fundamental OOTB table. Tables starting with 'u_' or 'x_' indicate custom tables.
Answer
ACLs can be defined using conditional expressions, scripts, and roles - all three methods combined.
Answer
A Schema Map is used to visualize relationships between different tables in the platform, showing tables, relationships, and relevant fields.
Answer
The security_admin role is not permanently assigned; administrators must elevate roles during a session via the Elevate Roles dialog for temporary elevated privileges.
Answer
Custom tables created by users (prefixed 'u_') can be permanently deleted; system/baseline tables cannot, to protect platform integrity. Deleting a table also deletes associated elements like views.
Answer
A dictionary override allows customizing the behavior and appearance of fields within extended tables, including labels, behavior, choices, and validation rules.
Answer
Both row level rules and field level rules must be satisfied for an operation to succeed - if either restricts access, the operation is not allowed.
Answer
A group can contain a nested group, allowing hierarchical organization into smaller, more specific subgroups.
Answer
problem_task is a child table of the task table. Task is the base table for many process-specific tables such as incident, change_request, problem, and problem_task.
Answer
Only Administrators have access to schema maps, tables, and column modules, as these are part of system configuration and the data model requiring elevated privileges.
Answers
CMDB powers ITSM processes, is built on a hierarchical table structure, is a centralized database storing CIs and relationships, and includes the Dependency View for visual mapping. User Permissions is an access control mechanism, not a core CMDB concept.
Answer
Access Control Rules (ACLs) govern access to tables, records, and fields, determining read/write/create/delete permissions based on roles, conditions, and scripts.
Answer
The schema map visually shows how tables are related through class extensions (inheritance) and references (relationships), e.g., Task extended by Incident, Problem, Change tables.
Answer
ESS (Employee Self-Service) users are limited to the self-service portal and do not have access to administrative modules or advanced functionality.
Answer
Best practice for granting catalog access to a team is to assign the role to the group itself, then add users to that group.
Answer
In a database table, each individual record corresponds to one row.
Answers
The Schema Map shows a table's relationships via Extended Tables, Extending Tables, and Reference Tables.
Answer
By default users have no access; explicit ACLs must grant read/write/create/delete permissions, so the statement is true.
Answer
Roles in ServiceNow can be nested — one role can contain (inherit) another role — so the statement that they cannot is false.
Answer
The security_admin role, created when the High Security Plugin is activated, grants elevated administrative privileges for security-sensitive tasks.
Answer
Configuration Items (CIs) can be tangible (a computer) or intangible (a software contract, a business service).
Answer
An elevated privilege grants a user temporary, extra permissions that apply only for the duration of that login session.
Answer
Application visibility upon login is determined by the roles assigned to the logged-in user.
Answer
Creating or modifying an ACL requires the security_admin role due to the sensitivity of access control configuration.
Answer
CI relationships based on discovery data and CMDB logic are created via Configuration > Relationships > Suggested Relationships.
Answer
The System Dictionary, which stores table/field/data-type definitions, is accessed via System Definition > Dictionary.
Answer
Database Views, which join multiple tables into a virtual table for reporting, are built via System Definition > Database Views.
Answer
A Role in ServiceNow is a collection of permissions that determines what a user can see and do; ACLs can reference roles, but a role is not itself an ACL or a persona.
Answer
A Process User is defined as a persona with clearly defined paths and workflows in the platform, assigned one or more roles such as itil or approver_user.
Answer
ACLs are evaluated first at the table level (most specific rule to most general), then at the field level, again from most specific to most general.
Answer
CSDM stands for Common Service Data Model, ServiceNow's standardized framework for structuring service-related data in the CMDB.
Answer
A Many-to-Many relationship links records bi-directionally through a junction table, making related records visible from both sides in related lists.
Answers
The CMDB can be populated using Discovery (which scans the network for CIs) and IntegrationHub ETL/Import Sets (which bring in data from third-party sources).
Answers
The three key CMDB tables are cmdb (base CI table for non-IT CIs), cmdb_ci (core CI table for IT CIs), and cmdb_rel_ci (defines relationships between CIs).
Answer
A group is a set of users who share a common purpose. Members perform tasks like approving change requests, resolving incidents, or receiving notifications. Every user should be assigned to at least one group, and best practice is to assign roles to groups rather than individual users.
Answer
The System Administrator (admin) role provides broad privileges including configuration, customization, and management of applications and modules across nearly all platform features. The other listed roles are either not standard ServiceNow roles or are more limited in scope (e.g., security_admin is specific to security features).
Answer
A Base Class table (e.g., task, cmdb_ci) is the root of the hierarchy and is not extended from any other table. A Parent Class table is itself extended from another table but also serves as the parent for further extensions (e.g., incident extends task and can itself be extended further).
Answer
The CSDM product view is the resource used to view details of the tables and CIs associated with a particular use case, providing a common framework/language for organizing and visualizing an organization's services and data.
Answer
Table ACL rules are processed by first matching the exact table name (e.g., incident), then the parent table name (e.g., task), then any table name using the wildcard (*).
Answer
The proper way to access the Schema Map is by navigating to System Definition > Tables, selecting the desired table, then using Related Links to click Show Schema Map. This gives a visual representation of relationships, extensions, and references for that table. It is not accessed from System Dictionary directly, from the Dictionary module, or via any direct 'Show Schema Map' option under System Definition.
Answer
The approver_user role is specifically designed for users who need to authorize requests without granting broader platform access, ideal for delegating approval authority without full ITIL functionality. 'authorize_user' is not a standard role; reviewers and verifiers don't have final authorization authority; approval groups route approvals but individual members still need the approver_user role to grant authorization.
Answers
ServiceNow supports authentication against its internal user table (Local Database), integration with LDAP directories like Active Directory, and Single Sign-On (SSO) via protocols such as SAML/OAuth/OpenID Connect. XML feeds are used for data integration, not authentication, and FTP is a file transfer protocol, not an authentication mechanism in ServiceNow.
Answer
Standard Application Access database settings are Can create, Can read, Can update, and Can delete. 'Can write' is not a standard ServiceNow setting — 'Can update' is the specific term used for modifying existing records.
Answer
ServiceNow provides a dedicated 'End Impersonation' option in the user menu/banner that immediately switches back to your own account without extra steps like logging out or restarting your computer.
Answers
Both the 'Tables' module and the 'Tables & Columns' module (an older naming) open the list of database tables (sys_db_object) where clicking New lets you create a new table. Schema Map visualizes existing table relationships rather than creating tables, Database isn't a ServiceNow module for this purpose, and Applications is a broader navigator category rather than the specific table-creation module.
Answer
To exclude a specific field from being audited, you add the attribute no_audit = true to that field's definition — 'no_audit = 0' is not the correct syntax.
Answers
Tables relate through extensions (a child table inherits the fields of its parent), one-to-many relationships (a reference field, such as many incidents pointing to one caller) and many-to-many relationships (a link table, such as the one between users and groups). A table can extend only one parent, so multiple inheritance is not supported.
Answers
CIs can be entered or edited manually, loaded with import sets and transform maps, and kept up to date through external integrations such as Discovery, Service Graph Connectors or SCCM. UI Macros and UI policies change how pages and forms behave; they do not load CMDB data.
Answer
Custom tables are created by administrators or developers after the instance is provisioned, and carry a u_ prefix in the global scope or the application's scope prefix. Base tables such as Task [task], and the tables that extend them such as Incident [incident], ship with the platform.
Answer
System Logs record activity on the instance, such as errors, warnings, script log statements, events and transactions, which makes them the place to troubleshoot what happened. Stats shows build and node statistics, Upgrade History lists upgrades and the changes they made, and System Diagnostics reports on instance health rather than activity.
Answer
The Task table has a Configuration item field for the main CI, and the Affected CIs related list (the task_ci table) links a task to any number of additional CIs. Incidents, problems and changes inherit both, which supports impact analysis and root cause investigation.
Answers
A True/False field is shown as a single checkbox, checked for true and unchecked for false, and a Checkbox field is also shown as a single checkbox. Choice and Multiselect Choice fields are shown as lists of choices, and a checkbox list shows a group of options rather than one checkbox.
Answer
The tables provided with the base system, such as Task [task], User [sys_user] and Incident [incident], are called core tables, while custom tables are the ones you create. A base table is a different idea: a table that does not extend another table, whether it is core or custom.
Answer
User [sys_user], Task [task] and Incident [incident] ship with the base system and are core tables that many applications build on. The other options are not sets of tables provided with the platform.
Answer
When a relationship is added from the base CI, the base CI is recorded as the child and the related CI as the parent, so relationships are always recorded the same way in the CMDB.
Answer
An ACL secures an object such as a table, record or field, and grants access to the users who meet its requirements, most often a role. It is not defined for a CI, and groups get access only through the roles assigned to them.