InServiceNow Service Catalog, approvals forcatalog item requestsare handled through workflows. Since the approval policy is based on thetotal cost of a request, it is managed within theService Catalog Request workflow.
C: Service Catalog Request
This workflowhandles approvals for catalog item requests, includingpurchase approvals.
Since the policy change involvesadjusting an approval threshold, this workflow needs to be updated.
The approval logic is likely configured in aconditional activity (if total cost > $3,100, require approval), which must be modified to$3,150.
A: Services Approval Processing
Not a standard ServiceNow workflowfor managing purchase approvals.
Service approvals are typically handled within theService Catalog Requestworkflow.
B: 6 Services Catalog Item Request
Likely acustom workflow, but not adefault ServiceNow workflowfor purchase approvals.
D: Purchasing Process Flow
There isno default "Purchasing Process Flow"in ServiceNow.
Theapproval workflow for purchasesis managed withinService Catalog Request workflows.
References:ServiceNow Documentation:Service Catalog Workflows
ServiceNow Developer Guide:Modifying Approval Conditions in Workflows

InServiceNow, afilter conditionis used toquery data from tables. It consists of three main components:
1. Column (Field)Represents the database column (or field) that is being filtered.
Example:Priority,State,Assigned To
In ServiceNow UI, this appears as thefirst dropdownin a filter condition.
2. OperatorDefines the comparison condition for the filter.
Examples:is,is not,greater than,contains,starts with
In ServiceNow UI, this appears as themiddle dropdownin a filter condition.
3. ValueSpecifies the criteria being matched against the column.
Example:High,Closed,John Doe
In ServiceNow UI, this is thethird input fieldin a filter condition.
Example of a Filter Condition in ServiceNow UI:Column (Field)
Operator
Value
Priority
is
High
State
is not
Resolved
This filter will returnrecords where:
ThePriorityfield is set toHigh
TheStatefield is NOTResolved
B: Match CriteriaIncorrect-No such term exists in ServiceNow filters.
C: FieldIncorrect- "Field" is another word for "Column", but "Column" is the correct term in ServiceNow filter conditions.
Incorrect Answer Choices Analysis:
ServiceNow Docs - Filtering Data#How to Create Filters in ServiceNow
ServiceNow Docs - Query Builder and Operators#Building Filter Queries
Official ServiceNow Documentation References:

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:

InServiceNow Knowledge Management,User Criteriais used to controlwho can view, contribute, or editknowledge articles and knowledge bases.
Scenario Requirements Breakdown:TheHR Knowledge Baseis already restricted to HR department members.
Anew knowledge articleneeds to be published in theQuarterly Reviewcategory.
OnlyHR Managersshould be able to read this specific article.
Best Approach (Correct answer: D)Torestrict access to the article itself(not the entire knowledge base or category), we:
Open the knowledge article
Go to the " Can Read " field
Add a User Criteria that includes the " HR Manager " group
Publish the article
This ensures thatonly HR Managers can read this specific articlewhile the rest of the HR departmentcannotsee it.
A). On the Knowledge Base, add User Criteria with a Manager Can Read script to the Can Read list, publish article to any category This would restrictall articlesin the knowledge base, not just the single article.
B). Add User Criteria for HR Manager Group on the Category's Can Read list User criteria canonly be applied at the Knowledge Base or Article level, not at the category level.
C). On the Knowledge Article, add an Access Control for HR Manager Group on the Can Read list, then publish article to any category ACLs (Access Controls)are not used forKnowledge Article permissions. User Criteria is the correct method.
Managing User Criteria in Knowledge Management
Restricting Article Access
Why Other Options Are Incorrect?Official ServiceNow Documentation Reference: