ServiceNow Updated CSA Exam Questions and Answers by malek

InServiceNow, theTask (task) tableis aparent tablethat provides a common structure forwork-related records. Several core tablesinherit from the Task table, meaning theyreuseits fields, business rules, and workflows.

The following tables arechildren of the Task tablein thebase system:

Incident (incident)

Used for managingbreak/fix issuesreported by users.

Inherits fields likeAssigned To, State, Priorityfrom the Task table.

Problem (problem)

Used forroot cause analysisof recurring incidents.

Inherits Task table properties, making it easy to relate problems to incidents.

Change Request (change_request)

Used tomanage changes in IT infrastructure(e.g., software updates, hardware replacements).

Inherits fields likeAssignment Group, Description, Statefrom the Task table.

D. Config

No such table named "Config" exists as a child of the Task table. Configuration-related data is stored inCMDB tables.

E. Dictionary

TheDictionary (sys_dictionary)table storesmetadata about database fields, not task-related records.

F. cmdb

TheCMDB (cmdb) table is not a child of the Task table. It storesConfiguration Items (CIs)like servers, routers, and software, which are separate from task-based workflows.

InServiceNow, aMany-to-Many (M2M) relationshipexists whenrecords in one tablecan be associated withmultiple records in another table, and vice versa.

A classic example of anM2M relationshipis:

✔Vendors can sell multiple products

✔Products can be sold by multiple vendors

Vendors oftensell multiple productsacross different categories.

A single product can beavailable from multiple vendors.

This requires anintermediary (join) tableto track the many-to-many relationship.

A. Requests & Items

Incorrectbecause eachRequest (REQ#)can havemultiple requested items (RITM#), but anitem does not belong to multiple requests. This is aone-to-many (1:M) relationship.

C. Tasks & Workflows

Incorrectbecause workflows are associatedat an individual task level, and while multiple workflows may be involved, they do not create a trueM2M relationship.

D. Configuration Items & Classes

Incorrectbecause a Configuration Item (CI)belongs to only one class, making this aone-to-many relationship, not M2M.

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:

UI Policiesin ServiceNow dynamically control form field behaviorswithout scripting. They help maintaindata consistencyand improve user experience.

B. Setting fields hidden

UI Policies canhideform fields based on conditions.

Example: Hide the"Resolution Notes"field unlessState = Resolved.

D. Setting fields read-only

UI Policies canmake fields read-onlyto prevent users from modifying certain data.

Example: Set"Requested For"fieldread-onlyafter submission.

E. Setting fields mandatory

UI Policies canenforce mandatory fieldsbased on conditions.

Example: Make the"Justification"field mandatory ifPriority = High.

A. Setting fields to accept the data with ‘n’ number of characters

Field length restrictions are set in theDictionary Definition, not UI Policies.

C. Setting fields to accept the data in an expected format

Data formatting (e.g., date, phone number) is controlled byField Types and Data Policies, not UI Policies.