CSA Exam Dumps - ServiceNow Certified System Administrator

Access Control Rules (ACLs)in ServiceNow define security rules thatcontrol user permissionsforviewing, creating, updating, and deletingrecords in the system. These rules ensure that users can onlysee and interact with the data they are authorized to access.

D. Access Control Rules

ACLsdefine security restrictionsat thefield, table, and record level.

These rules useconditions, scripts, and role-based permissionsto enforce security.

Example: A user with theitilrole may view incidents, but only users with theadminrole can delete them.

A. Role Assignment Rules

ServiceNowassigns roles to users, butroles alone do not define security rules.

ACLs controlwhat users can do, whilerolesonly grant potential access.

B. CRUD Rules

CRUD (Create, Read, Update, Delete)definespermission types, butnot security rules.

ACLs enforce CRUD operations based on roles and conditions.

C. Scripted User Rules

No such term as " Scripted User Rules " in ServiceNow security.

Possibly confused withScripted ACLs, which are part of Access Control Rules.

E. User Authentication Rules

Authentication rules controluser login mechanisms(LDAP, SSO, OAuth) but donot define access to data.

ACLs managedata security, while authentication ensuresusers are who they claim to be.

When selecting aTarget Tablefor anImport Set, you must choose a table that exists within the ServiceNow system and falls within your scope of permissions. The following types of tables are eligible as target tables:

Tables within the Global Scope(A - Correct Answer)

If the table exists within theglobal application scope, it is accessible from all applications.

Example:Task [task],User [sys_user] ,Configuration Item [cmdb_ci]

Tables within the Existing Application Scope(B - Correct Answer)

Tables belonging to the same application scope as the import set can be selected.

Example: If you are working in a scoped application likeHR Service Delivery, you can import data intoHR-related tables.

Related Tables Using Dot Walk(E - Correct Answer)

You can select related tables usingdot-walkingto reference data from linked tables.

Example: If importing intoIncident [incident], you can reference data fromCaller (sys_user)via dot-walking.

C. Tables outside of ServiceNow

ServiceNowcannotdirectly import data into external databases or non-ServiceNow tables.

Instead, you can export data to an external system after processing.

D. Tables which allow write access to other applications

ServiceNow enforcesscope protection, so you cannot write to tables in a different application scope unless explicitly allowed.

You needcross-scope privilegesto modify tables in another application.

Importing Data into ServiceNow

Understanding Application Scope

Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

In ServiceNow, theApprover [approver-user] roleis specifically designed for users who need toauthorize requestsbut should not have any other permissions or administrative access to the platform.

Canapprove or reject requests(e.g., Change Requests, Service Catalog Requests).

No additional platform permissions(cannot create, modify, or view records beyond approvals).

Assigned automatically tousers designated as approversin approval workflows.

AnIT Managerreceives an approval request for a new laptop.

Themanager logs in and sees only the approval request(no other system access).

Theyapprove/rejectthe request without modifying any records.

Key Features of the Approver Role:Example Use Case:

B. Authorize [authorize-user] →Incorrect

No such role exists in ServiceNow.

C. Reviewer [reviewer_user] →Incorrect

No such role exists in ServiceNow.

D. Approver Group [approval_group] →Incorrect

Approval groupsallow multiple users to approve a request collectively, but it is not a standalone role.

Theapprover-user roleis the correct answer for individual approvals.

E. Verification [verify_user] →Incorrect

No such role exists in ServiceNow.

Why Other Options Are Incorrect?

Approval Configuration

User Roles in ServiceNow

Official ServiceNow Documentation Reference:

In ServiceNow, Application Scope is a fundamental concept used to protect applications by identifying and restricting access to application artifacts (such as tables, scripts, and business rules). 3

1. The Concept of Scope:

Every application in ServiceNow has a scope.4

Global Scope: This is the default scope for the baseline ServiceNow instance. Legacy applications and general configurations usually live here.

Private/Scoped Applications: These are distinct namespaces (e.g., x_acme_book_mgmt ). 5

2. Why Option D is Correct (Availability and Protection):

The primary purpose of a private scope is to define boundaries. It acts as a protective layer that does two main things:

Protection: It prevents code in the Global scope or other Scoped applications from modifying your application ' s data or logic without explicit permission. 6

Availability (The Answer): It allows the developer to explicitly define which parts of the application are public. By default, artifacts in a private scope are hidden from other applications. 7 The developer must configure " Cross-scope privileges " or set specific " Access " settings (e.g., making a Script Include " Accessible from: All application scopes " ) to determine what is available for use by others. 8

3. Why the other options are incorrect:

A: Scope does the opposite; it restricts access by default, rather than granting " all access. "

B: Scope does not determine the functionality of core services; it acts as a container for custom or store-bought applications.

C: Scope prevents other applications from changing your tables, but it allows the application to change its own tables and logic. 9

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.

By default, ServiceNow encrypts data in transit using industry-standard Transport Layer Security (TLS) protocols. This ensures that any data transmitted between the client and the ServiceNow platform, or between ServiceNow and integrated systems, is encrypted and protected from interception or tampering.

While ServiceNow also offers options for data at rest encryption and customer-managed encryption keys, these features often require additional configuration or subscription services. Encryption of data in use (while data is being processed in memory) is a more advanced concept and not provided by default.

Thus, encryption of data in transit is the baseline encryption feature included automatically in all ServiceNow instances.