Pass the ServiceNow Certified System Administrator CSA Questions and answers with ValidTests

In ServiceNow, ataskis a record that represents work that needs to be completed. It follows a lifecycle where it is:

Created– A task is generated, either manually or automatically (e.g., an incident, change request, or problem record).

Worked Upon– Users perform necessary actions, update statuses, and progress the task towards resolution.

Closed– Once completed, the task reaches a closed state, indicating that no further action is needed.

Tasks in ServiceNow are derived from theTask [task]table.

Common task-based records includeIncidents, Change Requests, Problems, and Service Requests.

Tasks follow a defined workflow and state transitions (e.g., New → Work in Progress → Resolved → Closed).

Key Features of a Task:

A. Report:

A report is a visualization of data and does not follow a lifecycle involving work or closure.

B. Workflow:

A workflow definesprocess automationand the movement of tasks, but it is not something that gets "worked upon" directly like a task.

C. Event:

Events are system-generated triggers that notify or automate actions, but they do not have a structured lifecycle like a task.

Why Other Options Are Incorrect:

ServiceNow Documentation:Task Management in ServiceNow

CSA Exam Guide:Coverstask recordsas fundamental entities that go through a lifecycle.

Reference from CSA Documentation:Thus, the correct answer isD. Task.

InServiceNow,User Impersonationallows anadmin or a user with the appropriate roleto temporarily act as another userwithout needing their password. This is mainly used fortesting and visibility, helping administrators and developers verify user permissions, role-based access, and UI experiences.

Testing Permissions & Roles

Ensures thatusers have the correct access rights(e.g., verifying ITIL user permissions for incident management).

Helps testUI Policies, Business Rules, and ACLs (Access Control Rules)by viewing the system from the perspective of different roles.

Debugging & Troubleshooting

Identifies why a usercannot access certain records or modules.

Helps inresolving permission-related issueswithout affecting live users.

Experience Validation

Ensures userssee the correct menus, fields, and optionsbased on their assigned roles.

Useful when developingnew applications, workflows, or Service Catalog items.

Admins and authorized userscan impersonate by clicking on their name in the top-right corner and selectingImpersonate User.

Once impersonated, all actions are logged for security and compliance.

Primary Functions of User Impersonation:How to Use Impersonation:

(A) Testing and visibility – Correct

The primary function ofuser impersonationis totest and verify what different users can see and doin the system.

It helps withdebugging UI, role-based access, ACLs, and workflow execution.

(B) Activate verbose logging – Incorrect

Verbose loggingis used fordetailed debugging and performance monitoring, butimpersonation does not enable logging features.

(C) View custom perspectives – Incorrect

ServiceNow doesnotuse the term "custom perspectives" in the context of impersonation.

Impersonationshows what a specific user sees based on their roles, but it doesnot create custom perspectives.

(D) Unlock Application master list – Incorrect

There isno such featureas an "Application Master List" that requires impersonation to unlock.

Application access is controlled byroles and permissions, not impersonation.

Explanation of Each Option:

Never impersonate a user without permission, especially in production environments.

All impersonation actions are loggedin the system for security and auditing purposes.

Use impersonation in a sub-production (development or test) instancebefore making changes to production.

Admins should use impersonation instead of logging in with test user accountsto maintain security and accountability.

Additional Notes & Best Practices:

ServiceNow Docs: Impersonating Users

https://docs.servicenow.com

ServiceNow Community: Best Practices for User Impersonation

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

LDAP (Lightweight Directory Access Protocol) Integrationin ServiceNow enables organizations to connect theircorporate directory services (such as Microsoft Active Directory)with their ServiceNow instance. This integration helps manageuser authentication and data synchronizationefficiently.

There aretwo key aspectsof LDAP Integration in ServiceNow:

Authentication

LDAP is commonly used foruser authentication, allowing users to log in to ServiceNow using theircorporate credentials.

Instead of storing passwords in ServiceNow, authentication requests are sent to theLDAP serverto verify the user's identity.

This helps in maintainingcentralized identity managementacross the organization.

Data Population

LDAP can be used toimport user and group informationinto ServiceNow.

This process is known asdata synchronization, where attributes such asusernames, email addresses, department details, roles, and group membershipsare pulled from LDAP and stored in ServiceNow.

This ensures that user information in ServiceNow isalways up-to-datewith the organization's directory.

B. Data Formatting–

While ServiceNow does process data from LDAP, "Data Formatting" isnotan aspect of LDAP integration.

Formatting refers to structuring or modifying data but is not a core function of LDAP integration.

C. Authorization–

Authorizationdetermines what a user can doafter authentication, such as assigning roles and permissions.

While ServiceNow can use LDAPgroupsto assign roles, the integration itselffocuses on Authentication and Data Populationrather than defining permissions within ServiceNow.

ServiceNow Docs: LDAP Integration Overviewhttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/integrate/authentication/concept/c_LDAPIntegration.html

ServiceNow CSA Official Training Guide (LDAP Integration & User Authentication)

Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms that the two main aspects of LDAP Integration in ServiceNow areAuthentication and Data Population.

InServiceNow,Access Control rules (ACLs)are used torestrict or grant accessto data. Each Access Control rule consists of:

Table-level (Row-Level) ACLs– Control access to the entire record (row).

Field-level ACLs– Control access to specific fields within a record.

Access Control rules are evaluated in a specific orderto determine whether a user has the necessary permissions to perform an action (Read, Write, Create, Delete, etc.).

If both a row-level and a field-level ACL exist for the same table, BOTH must evaluate to "true"before access is granted.

The system checks conditions, scripts, and roles defined in the ACLsto decide whether the user meets the access requirements.

Access Control Rule Evaluation Process:Why is Option C Correct?If both a row-level rule and a field-level rule exist, both must evaluate to "true" for a user to perform an action.

Row-Level ACLscheck if a user can access the record itself.

Field-Level ACLscheck if a user can access specific fields within that record.

If a user failseitherACL check, access is denied.

Why Are the Other Options Incorrect?A. "Rules are evaluated using roles. The role with the most permissions evaluates the rules first."

Access Control rulesare not evaluated based on roles with the most permissions.

Roles are just one factorin ACL evaluation, along with conditions and scripts.

B. "If more than one rule applies to a row, the older rule is evaluated first."

ServiceNow does not prioritize ACL rules based on their creation date.

Instead, ACLs follow a structured evaluation order (general-to-specific).

D. "Rules are evaluated from the general to the specific, so a table rule must be active to continue."

This is partially true but misleading.

ServiceNow evaluates ACLs fromspecific to general(Field → Table).

However,a table-level rule does NOT need to be activefor a field-level ACL to be evaluated.

Reference from Certified System Administrator (CSA) Documentation:????ServiceNow Docs – Access Control Rules (ACLs) Evaluation

????ServiceNow ACL Evaluation Documentation

"If a field-level rule and a row-level rule exist,both must evaluate to truefor the operation to be allowed."

Conclusion:The correct answer isC. If a row-level rule and a field-level rule exist, both rules must be true before an operation is allowed.

????Understanding ACL rule evaluation is critical for managing security in ServiceNow, ensuring that users have the appropriate access while maintaining data integrity.

InServiceNow, knowledge articles within aKnowledge Base (KB)aregrouped by categoriesto help users easily find and navigate relevant information.

Hierarchical Structure:

Categories can haveparent-child relationships, allowing forsubcategories.

Example:

Key Features of Knowledge Article Categorization:nginx

CopyEdit

ITSupport

├── Hardware

│ ├── Laptops

│ ├── Printers

├── Software

│ ├── Windows

│ ├── MacOS

Improved Search & Filtering:

Users can filter knowledge articlesby categoryin the Service Portal, Knowledge Management homepage, or in the Global Search.

Permissions & Visibility Control:

Categories can havespecific user criteriato restrict access to certain articles based on roles or groups.

Article Organization & Management:

Knowledge managers canreassign articlesto different categories if needed.

Knowledge Base (KB) articlesare always assigned to acategoryfor structured organization.

Without categories, articles would be unstructured and difficult to locate.

Knowledge Management Overview

Knowledge Management in ServiceNow

Creating and Managing Knowledge Categories

Knowledge Base Categories

Why the Answer is True?References from ServiceNow CSA Documentation:Final Verification:Answer is 100% correct and aligned with official ServiceNow Certified System Administrator (CSA) documentation.

InServiceNow, theService Catalogis a centralized portal where users can request IT services, hardware, software, and other business-related items. Within theService Catalog, the fundamental components are known asService Catalog Items.

Definition of Service Catalog Items:

AService Catalog Itemrepresents a specific service, product, or action that a user can request from theService Catalog.

It is thecore componentthat defines what users can request.

Examples include:

Requesting anew laptop

Submitting anaccess request

Ordering asoftware installation

Why They Are the "Building Blocks" of the Service Catalog:

All Service Catalog requests are based on catalog items—without them, the catalog has no offerings.

Each item has associated workflows, approvals, and fulfillment processesthat define how the request is handled.

They form the foundationof the Service Catalog because every service request must be tied to an item.

Understanding Service Catalog Items

Why Answer "B" is Correct:✔️"They are the building blocks."

Service Catalog Itemsserve as the fundamental componentsof the catalog.

They define what services and products are available for request.

Withoutcatalog items, the Service Catalog would not function as intended.

Why the Other Answers Are Incorrect:A. "They run behind the scenes."

Incorrectbecause Service Catalog Items arevisible to usersin the Service Catalog portal.

While workflows and fulfillment processes may operate in the background, the items themselves arenot hidden.

C. "They are optional."

Incorrectbecause Service Catalog Items aremandatoryfor a functioning Service Catalog.

Thecatalog is useless without catalog items, making them essential, not optional.

D. "They provide options."

Incorrectbecause while Service Catalog Items can havevariables(such as dropdown selections or checkboxes), their primary role isnot just to provide options but to define the services available.

ServiceNow CSA Study Guide – Service Catalog & Request Management

ServiceNow Docs: Service Catalog Overview(ServiceNow Documentation)

ServiceNow Tables & Data Model (sc_catalog, sc_cat_item, sc_request, sc_task)

References from the Certified System Administrator (CSA) Documentation:

In ServiceNow,Table Access Control (ACL) rulesdefine the permissions for accessing records within a table. When a user attempts to access a record, ServiceNow processesACL rules in a specific orderto determine if the user has the necessary permissions.

Specific Table Name ACLs

ServiceNowfirst checks ACL rulesthat are defined for the exact table being accessed.

If there are multiple ACL rules for the same table, ServiceNow evaluates themfrom most specific to least specific(i.e., field-level ACLs before table-level ACLs).

Parent Table Name ACLs(If applicable)

If the table inherits from another table (e.g.,Incident inherits from Task), ServiceNownext checks ACL ruleson theparent table.

This ensures that inherited rules are properly applied.

Wildcard ACLs (*)(Any table)

If no explicit ACL rule is found for the table or its parent, ServiceNow checkswildcard ACL rules (*), which apply toall tables.

Wildcard ACLs act as alast resortwhen no table-specific rules exist.

Order of Processing ACL Rules:

(A) any table name (wildcard), parent table name, table name – Incorrect

Wildcard rules (*) areprocessed last, not first.

(B) table name, parent table name, any table name (wildcard) – Correct

This follows the correctprocessing order:

First:ACLs for the specific table

Second:ACLs for the parent table (if applicable)

Third:Wildcard ACLs (*)

(C) parent table name, table name, any table name (wildcard) – Incorrect

Parent table ACLs arechecked aftertable-specific ACLs, not before.

(D) any table name (wildcard), table name, parent table name – Incorrect

Wildcard ACLs (*) arealways processed last, so this order is incorrect.

Explanation of Each Option:

Field-level ACLs(column-specific) take precedence overtable-level ACLs.

If multiple ACL rules apply,all must evaluate totruefor access to be granted.

Explicit Deny:If an ACL rule explicitlydenies access, the user is denied, even if another ACL grants access.

Always Test ACLs:Use the "Security Debugging" feature (/sys_security_acl_list.do) to verify how ACLs are applied.

Additional Notes & Best Practices:

ServiceNow Docs: How Access Control Rules Work

https://docs.servicenow.com

ServiceNow Community: Understanding ACL Processing Order

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

Update Setsin ServiceNow are used tocapture customizations and configurationsmade in an instance, allowing these changes to be moved between instances (e.g., from development to test or production). ServiceNow provides best practices to ensure smooth migration and avoid issues with missing or conflicting updates.

What is an Update Set?

AnUpdate Setis a collection of customizations (e.g., changes to forms, scripts, workflows, business rules) that can be moved from one instance to another.

Ittracks changesin a controlled way, preventing accidental loss of configurations.

Why Avoid Using the Default Update Set?

TheDefault Update Setis automatically used when no other update set is selected.

It captures changesbut should never be used for instance-to-instance migrationsbecause:

Itcannot be exported.

It contains system changes that arenot logically grouped.

It can causeinconsistencies and missing dependencieswhen moving updates.

Instead, administrators shouldcreate a named Update Setfor specific development work.

Understanding Update Sets in ServiceNow:

Why Answer "A" is Correct:✔️"Avoid using the Default Update Set as an Update Set for moving customizations from instance to instance."

This follows ServiceNow’sbest practicesfor managing Update Sets.

Using theDefault Update Setcan lead tomissing updates, conflicts, and untracked changes, making migrations unreliable.

Why the Other Answers Are Incorrect:B. "Before moving customizations from instance to instance with Update Sets, ensure that both instances are different versions."

Incorrectbecause ServiceNowrecommends that instances be on the same versionbefore applying Update Sets.

If instances are ondifferent versions, the Update Set may includeincompatible changes, causing failures.

C. "Use the Baseline Update Set to store the contents of items after they are changed the first time."

Incorrectbecause there is no such thing as a "Baseline Update Set" in ServiceNow.

ServiceNowdoes not automatically create a backup of original configurations—administrators should manually create an Update Set before making changes.

D. "Once an Update Set is closed as 'Complete,' change it back to 'In Progress' until it is applied to another instance."

Incorrectbecausea completed Update Set should not be reopened.

Once markedComplete, an Update Set isready for export and migration. Reopening it can causedata integrity issuesand confusion in version control.

ServiceNow CSA Study Guide – Update Sets & Configuration Management

ServiceNow Docs: Best Practices for Update Sets(ServiceNow Documentation)

ServiceNow Docs: Moving Customizations with Update Sets

References from the Certified System Administrator (CSA) Documentation:

In ServiceNow’sService Catalog, variables are used to capture user input when they request catalog items. These variables allow for dynamic and customized data collection for different service requests.

Among the options provided, the three validvariable typesthat can be added to aService Catalog Itemare:

Multiple Choice:

This variable type presents users with multiple predefined options, but only allows them to selectoneanswer.

Example: "What type of laptop do you need?" with options:MacBook, Windows Laptop, Chromebook.

Select Box:

Similar to Multiple Choice but presented in a drop-down format, making it useful when space needs to be conserved in a form.

Example: "Select your department" with a drop-down list ofIT, HR, Finance, etc.

Checkbox:

A simpleTrue/Falsevariable that allows users to check a box to indicate a selection.

Example: "Do you need an external monitor?" (Checkbox can be checked for 'Yes' or left unchecked for 'No').

Option A (True/False, Multiple Choice, and Ordered)

True/Falseis not a variable type in the Service Catalog. ServiceNow usesCheckboxfor Boolean (Yes/No) values instead.

Orderedisnot a valid Service Catalog variable type.

Option B (True/False, Checkbox, and Number List)

True/False is incorrect(ServiceNow uses "Checkbox" instead).

Number List is not a valid Service Catalog variable type.

Option C (Number List, Single Line Text, and Reference)

Number List is not a valid variable type.

Single Line Text and Reference are valid variables but were not all correct in this case.

ServiceNow Docs: Service Catalog Variableshttps://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/service-catalog-management/concept/c_ServiceCatalogVariables.html

ServiceNow CSA Official Training Guide (Service Catalog & Request Management)

Why the other options are incorrect?References from Certified System Administrator (CSA) Documentation:

In ServiceNow, administrators can check whichrelease versionis running on an instance by navigating to theStats module. This module provides various system statistics, including the current release name, build number, and other important system details.

Navigate toSystem Diagnostics→Stats(or simply type “Stats” in the navigation filter).

Scroll down to find theBuild nameandVersionfields.

The displayed version follows the standard ServiceNow naming convention (e.g., "Washington DC Patch 2 Hotfix 1").

How to Check the Release Version via Stats Module:

A. Memory Stats module:

This module provides memory consumption details and performance-related information, but it does not show the instance version.

C. System.upgraded table:

While this table records upgrade history and past version changes, it does not display the current version running on the instance.

D. Transactions log:

This log captures user activities and system transactions but does not provide release version details.

Why Other Options Are Incorrect:

ServiceNow Documentation:View system version details

Certified System Administrator (CSA) Study Guide: CoversSystem Diagnostics → Stats Moduleas a key method to verify the running release version.

Reference from CSA Documentation:

In ServiceNow,metricsare essential tools used to track and measure key performance indicators (KPIs) related to IT Service Management (ITSM) processes. They help organizations assess how effectively they are meeting their objectives by collecting data over time.

Definition of a Metric:

Ametricin ServiceNow refers to a method of measuring and evaluating the performance and effectiveness ofIT service management processesover time.

It allows organizations to track changes in records and measure how long specific conditions exist within a workflow.

Key Characteristics of a Metric:

It is used toassess process performanceandevaluate efficiencywithin IT services.

It providesquantifiable datato analyze trends and improvements in Service Management.

Common use cases include trackingincident resolution times,change request approvals, andSLA compliance.

Understanding ServiceNow Metrics:Why Answer "C" is Correct:✔️"A metric is used to measure and evaluate the effectiveness of IT service management processes."

This definition aligns precisely with how ServiceNow definesmetrics—theytrack, measure, and analyzethe efficiency of various ITSM processes over time.

Metrics help organizations understand service performance trends and make data-driven decisions.

Why the Other Answers Are Incorrect:A. "A metric is a report gauge used on homepages to display real-time data."

Incorrectbecausegaugesare UI elements thatvisualizedata from reports or metrics but are not themselves metrics. Metricscollect and measuredata, whereasgaugesdisplay the information.

B. "A metric is a time measurement used to report the effectiveness of workflows and SLAs."

Incorrectbecause whiletime-based metricsexist (e.g., tracking how long an incident stays in a particular state), metrics in ServiceNow arebroaderand not limited to time measurement alone.

D. "A metric is a comparative measurement used to report the effectiveness of workflows and SLAs."

Incorrectbecause metrics are not necessarilycomparative; they areabsolute measuresof process effectiveness. Metrics provideraw performance data, which can later be compared or analyzed over time.

ServiceNow CSA Study Guide – Reporting & Performance Analytics

ServiceNow Docs: Metrics Definition & Configuration(ServiceNow Docs - Metrics)

ServiceNow Performance Analytics & Reporting Overview

References from the Certified System Administrator (CSA) Documentation:

In ServiceNow, every table has a uniqueplatform name(also known as thedatabase nameorsys_id). The table that stores user records in ServiceNow is called"sys_user".

Table Name:sys_user

Purpose:Stores user records, including their roles, group memberships, and personal details.

Location in ServiceNow:You can access this table by navigating to:All → Users and Groups → Users

Key Fields in sys_user Table:

User ID (user_name)– Unique identifier for the user.

Name (name)– Full name of the user.

Email (email)– Email address of the user.

Roles (roles)– Defines user permissions in the system.

Active (active)– Indicates if the user is active in the system.

A. u_users– Incorrect. The prefixu_is typically used forcustom tablescreated by administrators. This is not a default system table.

B. sys_users– Incorrect. The correct name issys_user(singular), notsys_users. ServiceNow follows a singular naming convention for system tables.

C. x_users– Incorrect. The prefixx_is reserved forScoped Applicationscreated within an instance. The User table is a core system table, not a scoped one.

ServiceNow Product Documentation → User Administration → sys_user Table

ServiceNow Tables Reference → sys_user

ServiceNow CSA Study Guide → User and Data Administration

Understanding the sys_user Table:Explanation of Incorrect Answers:References from Certified System Administrator (CSA) Documentation:

TheKnowledge Base (KB) Searchfunctionality in ServiceNow is designed to help users find the most relevant articles efficiently. ServiceNow provides various sorting options for search results to ensure that users can access the most useful information.

Sorting Options in Knowledge Base Search:When users search for articles within a Knowledge Base, the results can be sorted using three primary criteria:

Most Recent Update (Option A)

This sorting method ranks articles based on theirlast modified date.

Newer or recently updated articles appear higher in the search results.

This ensures users see the most current information first.

Popularity (Option B)

Popularity is determined byuser interactionssuch as article views, feedback ratings, and usage.

More frequently accessed or positively rated articles are ranked higher.

This helps prioritize articles that have been helpful to other users.

Relevancy (Option C)

The ServiceNow platform uses aninternal search algorithmto determine relevance based on keywords, titles, and content within the article.

More relevant articles appear at the top, ensuring users get the most appropriate answers to their queries.

D. Manager Assignment (Incorrect)

Knowledge articles are not sorted by manager assignment.

Manager assignment applies to workflows and approvals, not to search ranking.

E. Number of Views (Incorrect)

While article popularity is a ranking factor,ServiceNow does not provide a direct "Sort by Number of Views" option.

The "popularity" metric includes views but also considersother engagement factorslike helpfulness ratings.

Why Are the Other Options Incorrect?

Reference from Certified System Administrator (CSA) Documentation:????ServiceNow Docs – Knowledge Management: Search and Filtering

????ServiceNow Knowledge Management Docs

"Knowledge articles can be sorted byrelevance, popularity, or most recent updateto ensure users find the most useful and up-to-date information."

Conclusion:The correct answers are:

A. Most recent update(Sorts by last modified date)

B. Popularity(Sorts based on article usage and engagement)

C. Relevancy(Sorts based on keyword matching and importance)

????Understanding Knowledge Base search sorting is essential for ServiceNow administratorsto help users find the right information efficiently.

When creating filters inServiceNow, the elements should be specified in the following order:

Field– The database field (column) that is being filtered.

Operator– The comparison method, such as "is", "contains", "greater than", etc.

Value– The specific data that the filter should match.

Example of a Properly Structured Filter:Imagine filtering a list ofIncidentswhere the priority is high. The filter would be structured as:

Field:Priority

Operator:is

Value:High

is– Matches an exact value

is not– Excludes a specific value

contains– Looks for a partial match

greater than– Finds records with a value greater than the specified one

less than– Finds records with a value less than the specified one

B. Field, Operator, then Condition– Incorrect.

"Condition" is not an individual filter element in ServiceNow; theoperatoralready defines the condition (e.g., "is", "contains").

C. Operator, Condition, then Value– Incorrect.

The field must comefirstto define what data is being filtered. The operator follows next.

D. Value, Operator, then Field– Incorrect.

This is completely reversed; you must specifywhat fieldyou are filtering first before applying conditions.

ServiceNow Product Documentation → Filters and Condition Builder

ServiceNow CSA Study Guide → Data Management and List Filters

ServiceNow List Views → Using Filters and Operators

Common Operators in ServiceNow Filters:Explanation of Incorrect Answers:References from Certified System Administrator (CSA) Documentation:

In ServiceNow,rolesdefine the level of access a user has within an instance.Roles are stored in thesys_user_roletable.

Definition of a Role:

Aroleis a collection ofpermissionsthat grant access to different parts of the system.

Example:Theadminrole grants full access, while theitilrole allows incident management access.

sys_user_role Table:

This tablestores role recordsand their associated metadata.

Every role has aunique sys_id, aname, and may be associated withparent roles(role inheritance).

Users are linked to roles through thesys_user_has_roletable.

How Roles Work in ServiceNow:

A user assigned a role gainsall the permissionsassociated with that role.

Roles can behierarchical(one role can inherit permissions from another).

Example:Theitil_adminrole includes all the permissions of theitilrole, plus additional privileges.

Key Details About Roles and sys_user_role Table:Why Option D (sys_user_role) Is Correct?sys_user_role→ The correct table where roles are recorded in ServiceNow.

Why Other Options Are Incorrect?A. sys_user→ Incorrect; this table stores user records, not roles.

B. sys_user_profile→ Incorrect; this table does not exist in ServiceNow.

C. sys_user_record→ Incorrect; this is not a valid table in ServiceNow.

ServiceNow Docs – Roles and Role Managementhttps://docs.servicenow.com

ServiceNow Table Schema – sys_user_role

ServiceNow Developer Portal – Role Hierarchy & Best Practices

References from Certified System Administrator (CSA) Documentation: