Pass CSA Exam Guide

Detailed Explanation:

In ServiceNow, when reporting data is required from multiple tables and dot-walking isn’t feasible, creating aDatabase Viewis often the best approach. A Database View allows joining multiple tables virtually without creating new records, making it highly efficient for reporting. This view can then be used as a data source for reports, pulling information across tables without physically combining data. According to ServiceNow documentation, this is especially useful for creating complex reports that rely on data relationships across tables without altering the underlying data structure. (Reference: ServiceNow Documentation - Database Views)

==

In ServiceNow’sConfiguration Management Database (CMDB), threekey tablesform the foundation for storing and managingConfiguration Items (CIs)and theirrelationships.

cmdb_ci (E) - CI Base Class Table

This is thebase classfor allConfiguration Items (CIs)in the CMDB.

Every CI (e.g., servers, applications, network devices) extends from this table.

Stores general attributes like name, serial number, and asset tag.

cmdb (G) - CMDB Parent Table

This is theparent tablefor all CMDB-related tables.

Itdoes not store CI records directlybut serves as a reference structure.

All CMDB tables, includingcmdb_ci, inherit from this table.

cmdb_rel_ci (C) - CMDB Relationship Table

This tablestores relationshipsbetween different CIs.

Example: Aserver hosts an application, or adatabase is dependent on a storage unit.

Helps withimpact analysis and dependency mapping.

A. sn_cmdt_bak

No such table in standard ServiceNow CMDB.

B. sh_emdb_ci

Typo or incorrect table name—not part of the ServiceNow CMDB model.

D. cmdb_bak

" bak " suggests abackup table, but there isno standard " cmdb_bak " in ServiceNow.

F. sh_eomdb

Not a recognized CMDB table in ServiceNow.

Detailed Explanation:

In ServiceNow,User Presencefeatures provide real-time visibility into record collaboration. This includes:

Option B:An icon that appears beside fields updated by other users, indicating recent changes.

Option E:A user presence icon showing initials of users currently viewing the record. These real-time indicators improve collaboration and prevent conflicts during data entry. (Reference: ServiceNow Documentation - Real-time Collaboration and User Presence)

==

In ServiceNow, Roles are used to configure access to Applications and Modules. Roles are a core component of ServiceNow ' s role-based access control model and determine which application menus, modules, features, and administrative capabilities a user can access.

For an Application , access can be restricted by assigning one or more roles to the corresponding Application Menu record. Only users possessing the required role can normally see that application in the navigation interface. ServiceNow documentation states that application access can be configured through the application ' s User role or through the Roles field on the Application Menu.

Modules are controlled similarly. The Module record contains a Roles field within its Visibility configuration. ServiceNow specifies that access to modules in the navigation menu is controlled through roles; users must meet the applicable role requirements before the module is displayed.

Users and Groups can receive roles, but they are not the permission mechanism configured directly on Applications and Modules. Departments are organizational records and do not determine Application Navigator access.

Therefore, the permission mechanism used to configure Application and Module access is Roles .

Study Guide Reference/Topics: User Administration → Roles → Role-Based Access → Application Menus → Module Visibility → Assigning Roles to Users and Groups.