Important ServiceNow CSA Exam Questions

Answer: C

Explanation:

In ServiceNow, Roles are used to control access to Applications and Modules within the platform. A Role is a set of permissions that define what actions a user can perform and which records they can access.

Key Functions of Roles in Access Control:

Grant Access to Applications and Modules:

If a user does not have the required role, they cannot see or access an application/module.

Control Record-Level and Field-Level Access:

Some Access Control Rules (ACLs) depend on roles to permit or restrict data visibility.

Assign Multiple Roles to a User:

A user can have multiple roles based on job responsibilities.

Example Roles in ServiceNow:

admin -- Full access to all system features.

itil -- Can manage incidents, problems, and changes.

catalog_admin -- Manages the Service Catalog.

asset -- Manages assets and CI records.

How to Assign Roles to Users:

Navigate to: All Users and Groups Users

Open a user record

Scroll to the Roles related list

Click Edit and add roles

Explanation of Incorrect Answers:

A . Access Control Rules -- Incorrect.

Access Control Rules (ACLs) define record-level and field-level security, but they do not control access to applications and modules directly.

B . UI Policies -- Incorrect.

UI Policies control the visibility and behavior of form fields, not module or application access.

D . Assignment Rules -- Incorrect.

Assignment Rules automatically assign tasks (e.g., Incidents, Requests) to groups or users, but they do not control access.

Reference from Certified System Administrator (CSA) Documentation:

ServiceNow Product Documentation Roles and Permissions

ServiceNow CSA Study Guide User and Role Management

ServiceNow Knowledge Base Controlling Access to Applications and Modules

Answer: C

Answer: A

Explanation:

In the ServiceNow Configuration Management Database (CMDB), the mechanism that enables the tracing of connections between different Configuration Items (CIs) is Relationships.

1. The Role of Relationships in CMDB:

The CMDB is not just a flat list of assets; its true power lies in its ability to map how different components interact. A Relationship defines the dependency or connection between two CIs. For example, a 'Web Server' CI might run on a 'Linux Server' CI, and an 'Email Service' might depend on that 'Web Server.'

2. The cmdb_rel_ci Table:

Technically, these connections are stored in a specific table called the CI Relationship table (cmdb_rel_ci). This table acts as a bridge, storing three key pieces of information for every connection:

Parent: The upstream item (e.g., the Service or Application).

Child: The downstream item (e.g., the Server or Database).

Type: The nature of the connection (e.g., 'Runs on,' 'Depends on,' 'Hosted on,' 'Members of').

3. Dependency Views:

While the Relationship is the underlying data enabler, ServiceNow visualizes these relationships using Dependency Views (formerly known as Business Service Management or BSM maps). Dependency Views use the relationship data to graphically display the infrastructure. By looking at a Dependency View for a Server, you can trace the lines (relationships) upward to see exactly which Business Services will be impacted if that Server goes down.

4. Why the other options are incorrect:

Transform Map: This is a component of the Import Set process. It is used to map source data (from a spreadsheet or XML) to target fields in a ServiceNow table during data import. It does not define infrastructure dependencies.

Automapping Utility: This is not a standard ServiceNow architectural term. While ServiceNow has a 'Service Mapping' product that automates the discovery of relationships, 'Automapping Utility' is not the specific feature name, nor is it the fundamental element that enables tracing.

Service Tracer: This is a fictitious term and does not exist in the ServiceNow platform.

Answer: B

Explanation:

The History section in the Application Navigator tracks recently visited records, lists, and forms within ServiceNow. This feature allows users to quickly navigate back to previously accessed content without searching manually.

What Appears in the History Section?

The History section logs user activity related to:

Records ( Option A) -- Recently viewed records from any table, such as incidents, requests, or tasks.

Lists ( Option C) -- Any list views a user has accessed, such as Incident List or Change Request List.

Forms ( Option D) -- Any individual record viewed in form view, such as an incident form or user form.

Why is Option B (UI Pages) Correct?

UI Pages do NOT appear in the History section.

UI Pages are special custom pages built with Jelly scripting and used for custom interfaces, portals, and dashboards (e.g., Service Portal pages).

Since they do not represent individual records, lists, or forms, they are not included in the user's History tracking.

Why Are the Other Options Incorrect?

A. Records

Records are individual database entries (e.g., specific incidents, change requests, or users).

Since records are frequently accessed, they are logged in History.

C. Lists

Lists display multiple records from a table (e.g., all open incidents).

Since users navigate through lists frequently, they are logged in History.

D. Forms

Forms are used to view or edit individual records (e.g., an incident form).

Since forms are commonly accessed, they are logged in History.

Reference from Certified System Administrator (CSA) Documentation:

ServiceNow Docs -- Application Navigator & History ServiceNow Application Navigator Documentation

'The History section of the Application Navigator displays a list of the records, lists, and forms that you have recently accessed.'

'Custom UI Pages are not included in History tracking.'

Answer: C

Explanation:

In ServiceNow, the Dependency View is a graphical representation that allows Service Desk agents and IT teams to trace relationships between Configuration Items (CIs) and identify which CIs are experiencing issues that may be affecting a business service.

Why is 'Dependency View' the Correct Answer?

Visualizes Relationships Between CIs and Services

Dependency View displays CIs and their dependencies in an interactive map.

Service Desk agents can quickly see which CIs are impacted and how they affect the business service.

Identifies Impacted Configuration Items (CIs)

If a server, database, or network component is down, Dependency View helps trace which business service is affected.

This is useful for incident management, root cause analysis, and change impact assessment.

Integrated with CMDB (Configuration Management Database)

Dependency Views pull data from the CMDB to map CI relationships.

This helps Service Desk agents identify problems quickly without needing deep technical knowledge.

Incorrect Answer Choices Analysis:

A . AI Service Dashboard Incorrect -- There is no standard 'AI Service Dashboard' in ServiceNow.

B . CI Health Dashboard Incorrect -- The CI Health Dashboard focuses on the overall health of CIs (e.g., compliance, correctness, completeness) but does not provide a dependency map for tracing service issues.

D . Event Management Homepage Incorrect -- Event Management (ITOM) is used for monitoring events and alerts, but it does not provide an interactive dependency view for tracing service issues.

Official ServiceNow Documentation Reference:

ServiceNow Docs -- Dependency Views Understanding Dependency Views

ServiceNow Docs -- CMDB Relationship Visualization Using CMDB Relationships

Conclusion:

The correct answer is: C. Dependency View

Dependency View allows Service Desk agents to trace service issues back to the affected CIs, making it an essential tool for incident management and root cause analysis.