ServiceNow Certified System Administrator CSA Exam Dumps and Practice Test Questions Set10 Q136-150
Visit here for our full ServiceNow CSA exam dumps and practice test questions.
Question 136:
Which ServiceNow feature allows administrators to control which fields users can see and edit on a form?
A) Data Policies
B) UI Policies
C) Access Control Lists
D) Field Security
Answer: B
Explanation:
UI Policies in ServiceNow provide administrators with powerful capabilities to dynamically control field visibility and editability on forms based on specified conditions. These client-side automation rules execute in the user’s browser and modify the form interface in real-time, creating responsive and context-aware user experiences. UI Policies enable administrators to show or hide fields, make fields mandatory or read-only, and customize form behavior without requiring custom scripting.
UI Policies consist of conditions and actions that determine when and how form elements should be modified. When a user loads or interacts with a form, the platform evaluates UI Policy conditions against current field values and executes corresponding actions. For example, a UI Policy might make a resolution field mandatory only when an incident’s state is set to resolved, ensuring users provide necessary information before closing tickets. This conditional logic helps maintain data quality and guides users through appropriate workflow steps.
The UI Policy framework supports multiple actions that can be applied to form fields simultaneously. Administrators can configure actions to set field visibility, change mandatory status, modify read-only properties, and clear field values. Multiple UI Policies can apply to the same form, with the system executing them in priority order. The reverse-if-false option allows UI Policies to automatically reverse their actions when conditions are no longer met, creating dynamic forms that adapt as users enter information.
UI Policies improve user experience by presenting only relevant fields based on current record state and context. This reduces form complexity and helps users focus on information appropriate for their current task. The client-side execution of UI Policies ensures immediate visual feedback without requiring server round trips, creating responsive interfaces. UI Policies can be scoped to specific roles, ensuring different user groups see customized form layouts appropriate for their responsibilities.
Option A is incorrect because Data Policies enforce data integrity rules server-side and do not control UI field visibility. Option C is incorrect as Access Control Lists manage security permissions for records and operations but do not dynamically control form field behavior. Option D is incorrect because Field Security is not a standard ServiceNow feature for controlling form field visibility and editability.
Question 137:
What is the purpose of the Application Navigator in ServiceNow?
A) To navigate between different ServiceNow instances
B) To provide hierarchical access to modules and applications
C) To manage application security settings
D) To monitor application performance metrics
Answer: B
Explanation:
The Application Navigator serves as the primary navigation interface in ServiceNow, providing users with hierarchical access to modules, applications, and platform functionality. This left-side navigation panel organizes system features into logical groupings, making it easy for users to locate and access the tools they need to perform their work. The Application Navigator displays a tree structure of applications and modules, with expandable sections that reveal nested navigation options.
The hierarchical organization of the Application Navigator reflects ServiceNow’s application-based architecture, where functionality is grouped into applications that contain related modules. Users can expand application folders to view available modules, which are essentially shortcuts to specific tables, lists, forms, or functionality within the platform. This organization helps users understand the logical structure of the system and discover related features within the same functional area. The navigator supports search functionality, allowing users to quickly find modules by typing keywords rather than browsing through the hierarchy.
Customization options for the Application Navigator enable administrators to tailor the navigation experience for different user groups. Module visibility can be controlled through roles, ensuring users only see navigation options relevant to their responsibilities. Administrators can create custom applications and modules, organizing them in the navigator to support specific business processes. The navigator also supports favorites and history, allowing users to quickly access frequently used modules and recently visited pages.
The Application Navigator enhances productivity by providing consistent navigation patterns across the platform. Users can quickly switch between different functional areas without losing context or needing to memorize complex navigation paths. The navigator’s persistent presence on the interface ensures users always have access to navigation controls, reducing the likelihood of users becoming lost within the application. Modern ServiceNow interfaces also support collapsible navigators, maximizing screen space for content while maintaining easy access to navigation.
Option A is incorrect because navigating between ServiceNow instances requires different mechanisms such as instance URLs or identity provider integrations. Option C is incorrect as managing application security settings is performed through dedicated security modules, not the Application Navigator. Option D is incorrect because monitoring application performance metrics requires analytics tools and dashboards rather than the Application Navigator interface.
Question 138:
Which type of ServiceNow notification can be sent to users when specific conditions are met?
A) Email notifications only
B) SMS notifications only
C) Both email and SMS notifications
D) Push notifications only
Answer: C
Explanation:
ServiceNow supports multiple notification channels including both email and SMS notifications, providing flexible communication options to reach users through their preferred methods. This multi-channel notification capability ensures critical information reaches users promptly, regardless of whether they are actively using the ServiceNow platform. Organizations can configure notifications to send through different channels based on urgency, user preferences, and business requirements.
Email notifications are the most commonly used notification type in ServiceNow, providing detailed information about events, updates, and actions requiring user attention. Email notifications can include rich formatting, embedded images, links back to the ServiceNow platform, and comprehensive context about the triggering event. ServiceNow’s email notification framework supports template-based messages with dynamic content insertion, allowing administrators to create professional, branded communications. Email notifications can be triggered by various events including record updates, approval requests, task assignments, and workflow milestones.
SMS notifications provide immediate alert capabilities for time-sensitive situations where users may not be monitoring email. These text message notifications are typically shorter and more concise than email notifications, focusing on essential information and calls to action. SMS notifications are particularly valuable for critical alerts, emergency notifications, and situations requiring immediate response. ServiceNow integrates with SMS gateway providers to deliver text messages to users’ mobile devices, with configuration options for message templates and delivery rules.
The platform’s notification framework allows administrators to configure which notification channel should be used for different scenarios. Organizations can implement escalation strategies where initial notifications are sent via email, with SMS notifications triggered if users don’t respond within specified timeframes. User preferences can also influence notification channel selection, allowing individuals to specify their preferred communication methods. The notification system tracks delivery status and maintains logs of sent notifications for audit purposes.
Option A is incorrect because ServiceNow supports multiple notification channels beyond just email. Option B is incorrect as SMS is available but not the only notification option. Option D is incorrect because while push notifications exist in mobile applications, the platform primarily supports email and SMS as the main notification channels described in standard documentation.
Question 139:
What is the function of a client script in ServiceNow?
A) To run automation on the server after database operations
B) To execute JavaScript in the user’s browser for real-time form interaction
C) To schedule automated tasks to run at specific times
D) To integrate ServiceNow with external systems
Answer: B
Explanation:
Client scripts in ServiceNow execute JavaScript code directly in the user’s browser, enabling real-time form interactions and dynamic user interface behavior. These client-side scripts respond to user actions such as field changes, form loads, and form submissions, providing immediate feedback without requiring server communication. Client scripts are essential for creating responsive, user-friendly interfaces that guide users through data entry and validate information as it is entered.
There are four types of client scripts in ServiceNow, each designed for specific interaction patterns: onLoad, onChange, onSubmit, and onCellEdit. OnLoad scripts execute when a form first loads, allowing initialization logic to run before users interact with the form. OnChange scripts trigger when specific field values change, enabling dependent field updates and dynamic form behavior. OnSubmit scripts run when users submit forms, performing validation checks before allowing the form to save. OnCellEdit scripts apply to list views, executing when users edit fields directly in list layouts.
Client scripts enhance user experience by providing immediate validation feedback, reducing the need for server round trips and form reloads. For example, a client script might validate that an email address is properly formatted as the user types, displaying error messages instantly if the format is incorrect. Client scripts can also implement cascading field behaviors, where selecting a value in one field automatically populates or restricts options in related fields. This guidance helps users complete forms accurately and efficiently.
The client-side execution model of these scripts means they cannot directly access server-side data or perform database operations. However, client scripts can use GlideAjax to make asynchronous server calls when server data is needed. Best practices recommend keeping client scripts lightweight to maintain form performance and using them judiciously to avoid browser performance issues. Client scripts should focus on user interface logic and immediate validation, while leaving complex business logic to server-side business rules.
Option A is incorrect because server-side automation after database operations is handled by business rules, not client scripts. Option C is incorrect as scheduling automated tasks uses scheduled jobs rather than client scripts. Option D is incorrect because system integration is typically performed through integration modules and APIs rather than client scripts.
Question 140:
Which ServiceNow table stores information about user accounts?
A) sys_user_group
B) sys_user
C) sys_user_role
D) sys_user_profile
Answer: B
Explanation:
The sys_user table is the fundamental database table in ServiceNow that stores information about user accounts, containing essential details such as user names, email addresses, phone numbers, departments, locations, and authentication credentials. This core system table serves as the foundation for user management and is referenced throughout the platform wherever user information is needed. Every user who accesses ServiceNow has a corresponding record in the sys_user table, making it central to identity management and security.
The sys_user table includes numerous fields that capture comprehensive user profile information. Standard fields include first name, last name, user ID, email, phone, mobile phone, title, department, company, location, time zone, and date format preferences. The table also stores authentication-related information such as password hashes, multi-factor authentication settings, and locked account status. Extended fields may capture additional organizational details like manager, cost center, and employee number, supporting human resources processes and organizational hierarchies.
User records in the sys_user table integrate with ServiceNow’s security framework, linking to roles, groups, and access permissions. The platform uses sys_user records to determine what data users can access, which actions they can perform, and how the interface should be customized for their needs. User records also connect to activity history, allowing the system to track who created, modified, or accessed records throughout the platform. This audit trail capability is essential for compliance and security monitoring.
The sys_user table supports various user types including regular employees, contractors, service accounts, and integration users. Each user type may have different attribute requirements and security configurations. Administrators can extend the sys_user table by adding custom fields to capture organization-specific information not included in the baseline schema. Data in the sys_user table can be populated through manual entry, import from external systems, or integration with identity providers like LDAP or Single Sign-On systems.
Option A is incorrect because sys_user_group stores information about user groups, which are collections of users, not individual user accounts. Option C is incorrect as sys_user_role is a many-to-many relationship table that links users to their assigned roles but does not store core user information. Option D is incorrect because sys_user_profile is not a standard ServiceNow table for storing user account information.
Question 141:
What is the purpose of the Condition Builder in ServiceNow?
A) To build workflow conditions using drag and drop
B) To create filter conditions for queries without writing code
C) To construct database table relationships
D) To design form layouts and field arrangements
Answer: B
Explanation:
The Condition Builder is a visual query tool in ServiceNow that enables users to create filter conditions for records without requiring knowledge of scripting or query syntax. This intuitive interface allows users to construct complex filter logic by selecting fields, operators, and values through dropdown menus and form elements. The Condition Builder democratizes data filtering capabilities, making it accessible to users with varying technical skill levels while ensuring query syntax accuracy.
The Condition Builder interface presents a structured approach to defining filter conditions, with separate sections for selecting the field to filter, choosing the appropriate operator, and specifying the comparison value. Users can add multiple conditions and organize them using AND/OR logic to create sophisticated filtering rules. The tool supports various data types including strings, numbers, dates, and reference fields, automatically presenting appropriate operators for each field type. For example, date fields offer operators like is, is before, is after, and is between, while string fields provide options like contains, starts with, and ends with.
This visual condition building interface appears throughout ServiceNow in numerous contexts including list filters, report conditions, business rule conditions, assignment rules, and workflow transitions. The consistent interface across these different areas makes it easy for users to apply filtering knowledge learned in one context to other platform areas. The Condition Builder generates encoded query strings behind the scenes, which are stored in the database and executed when needed. These query strings are optimized for database performance and security.
Advanced features of the Condition Builder include dynamic reference qualifiers, which filter related record lists based on current field values, and the ability to filter on related table fields using dot-walking notation. Users can also create filter conditions that reference the currently logged-in user, enabling personalized views and security filtering. The Condition Builder preserves complex query logic in a human-readable format, making it easy to understand and modify conditions without parsing encoded query syntax.
Option A is incorrect because building workflow conditions uses workflow editors and transition conditions, though they may incorporate the Condition Builder. Option C is incorrect as constructing database table relationships is performed through table schema design tools, not the Condition Builder. Option D is incorrect because designing form layouts uses form designer and form layout tools rather than the Condition Builder interface.
Question 142:
Which ServiceNow module allows administrators to view and manage all active sessions?
A) User Administration > Active Users
B) System Diagnostics > Active Transactions
C) System Security > Active Sessions
D) User Administration > Active Sessions
Answer: A
Explanation:
The User Administration module contains the Active Users feature, which provides administrators with visibility into all current user sessions and active connections to the ServiceNow instance. This monitoring capability is essential for system administration, security oversight, and troubleshooting user access issues. The Active Users list displays real-time information about who is currently logged into the system, when their session started, and which applications or modules they are accessing.
Active user monitoring serves multiple important functions in ServiceNow administration. Security teams use this feature to identify unauthorized access attempts, detect unusual login patterns, and investigate potential security incidents. When suspicious activity is detected, administrators can immediately terminate sessions to prevent further unauthorized access. The active sessions view also helps with capacity planning by showing peak usage times and concurrent user counts, informing decisions about instance sizing and performance optimization.
The Active Users interface displays detailed session information including user name, login time, session duration, IP address, and browser information. Administrators can filter and sort this information to find specific users or identify patterns in system usage. The interface provides action capabilities such as impersonating users to troubleshoot reported issues or forcibly logging out users when necessary for maintenance or security reasons. Session timeout policies can be monitored through this interface, ensuring users are automatically logged out after periods of inactivity.
Managing active sessions is particularly important during maintenance windows and system updates. Administrators need to verify that all users have logged out before performing critical system changes or applying updates. The Active Users module provides the visibility needed to communicate with remaining users and ensure clean system states before maintenance. This capability also supports license management by monitoring concurrent user connections against licensed user counts.
Option B is incorrect because System Diagnostics > Active Transactions monitors system performance and transaction processing, not user sessions. Option C is incorrect as System Security does not contain an Active Sessions module with this specific functionality. Option D is incorrect because while conceptually close, the standard navigation path is User Administration > Active Users rather than Active Sessions.
Question 143:
What is the primary purpose of transform maps in ServiceNow?
A) To transform data during import from external sources
B) To map user roles to security permissions
C) To transform workflow diagrams into executable processes
D) To map form fields to different layouts
Answer: A
Explanation:
Transform maps in ServiceNow serve as the primary mechanism for transforming and mapping data during the import process from external sources into ServiceNow tables. These configuration objects define how raw import data should be processed, cleansed, and mapped to appropriate fields in target tables. Transform maps are essential components of the data import infrastructure, enabling organizations to load data from various sources while maintaining data quality and consistency.
A transform map consists of field mappings that specify how each column from the source data corresponds to fields in the target ServiceNow table. These mappings can perform simple one-to-one field assignments or implement complex transformation logic using scripts. Transform map scripts allow administrators to manipulate data during import, performing tasks such as data format conversions, value lookups, default value assignments, and conditional logic based on source data characteristics. This flexibility ensures imported data meets platform standards and business requirements.
The transform map framework supports various data import scenarios including creating new records, updating existing records, or performing coalesce operations that determine whether to create or update based on matching criteria. Coalesce fields define unique identifiers used to match import data with existing records, preventing duplicate record creation. Transform maps can reference other tables to populate reference fields, ensuring relational integrity when importing interconnected data. The platform provides debugging capabilities that help administrators test transform maps and troubleshoot mapping issues.
Transform maps work in conjunction with import sets, which serve as staging tables for imported data. The import process loads raw data into import set tables, then applies transform maps to process and move data into production tables. This two-stage approach allows administrators to review imported data before transformation, making corrections if needed. Transform maps can be reused across multiple import operations, standardizing data integration processes and reducing configuration effort for recurring imports.
Option B is incorrect because mapping user roles to security permissions is handled through role assignments and access control lists, not transform maps. Option C is incorrect as transforming workflow diagrams into executable processes is handled by workflow publishing mechanisms. Option D is incorrect because mapping form fields to layouts uses form design tools rather than transform maps.
Question 144:
Which ServiceNow feature allows users to save personalized list configurations?
A) List Controls
B) List Layouts
C) List Filters
D) List Views
Answer: D
Explanation:
List Views in ServiceNow provide users with the capability to save personalized list configurations, preserving filter conditions, column arrangements, and sort orders for future use. This feature enhances productivity by allowing users to quickly access commonly used data views without repeatedly configuring filters and column layouts. List Views can be created as personal views visible only to the creator or shared views accessible to other users with appropriate permissions.
When users configure a list by adding filters, selecting which columns to display, arranging column order, or setting sort preferences, they can save these configurations as named List Views. These saved views appear in a dropdown menu above the list, allowing quick switching between different data perspectives. For example, an incident manager might create separate list views for high-priority incidents, incidents assigned to specific teams, and recently updated incidents, easily switching between these views throughout the day.
The List View functionality supports both simple and complex configurations. Users can combine multiple filter conditions using the Condition Builder, create filters that reference dynamic values like the current date or logged-in user, and set up multi-level sorting. Column configurations in List Views specify which fields should be visible and in what order, allowing users to focus on information relevant to their specific needs. Some List Views can be designated as default views, automatically loading when users navigate to the list.
Administrators can create and share List Views for their user communities, establishing standardized views that support consistent work practices. Shared List Views can be assigned to specific roles, ensuring users see relevant data perspectives when they first access lists. The platform tracks List View usage, helping administrators identify which views are most valuable and refining shared configurations based on user behavior. List Views contribute significantly to user adoption by reducing the learning curve and making data access more intuitive.
Option A is incorrect because List Controls refer to the control buttons and actions available on lists, not saved view configurations. Option B is incorrect as List Layouts relate to the visual arrangement of list elements but do not encompass the saved filter and configuration aspect of List Views. Option C is incorrect because List Filters are components used within List Views but do not represent the complete saved configuration feature.
Question 145:
What is the purpose of the ServiceNow CMDB?
A) To manage customer relationship data
B) To store configuration item information and relationships
C) To track change management requests
D) To maintain service catalog item definitions
Answer: B
Explanation:
The Configuration Management Database, commonly known as CMDB, serves as the centralized repository for storing information about configuration items and their relationships within an organization’s IT infrastructure. The CMDB provides a comprehensive view of the IT environment, documenting hardware, software, network components, services, and their interdependencies. This visibility is essential for effective IT service management, enabling informed decision-making about changes, incidents, and service delivery.
Configuration items stored in the CMDB represent individual components of the IT infrastructure such as servers, workstations, applications, databases, network devices, and business services. Each configuration item record contains detailed attribute information including specifications, ownership, location, lifecycle status, and relationships to other configuration items. These relationships map the complex dependencies between infrastructure components, showing how business services rely on underlying technical infrastructure. The CMDB enables impact analysis by revealing which business services would be affected if specific configuration items fail or require maintenance.
The CMDB integrates with multiple ServiceNow processes and modules, providing context for incident management, change management, problem management, and service request fulfillment. When incidents occur, technicians can reference the CMDB to understand affected configuration items and their dependencies, accelerating root cause identification. Change management processes use CMDB information to assess change risks by identifying all components and services potentially impacted by proposed changes. This integration ensures consistent configuration information is available across all IT service management processes.
Maintaining CMDB accuracy requires ongoing discovery, reconciliation, and data governance processes. ServiceNow provides discovery tools that automatically scan networks to identify configuration items and populate CMDB data. Reconciliation processes merge information from multiple sources, resolving conflicts and maintaining data quality. Organizations establish CMDB governance practices to define data ownership, update responsibilities, and quality standards. A well-maintained CMDB becomes a strategic asset, supporting automation initiatives, security management, and IT portfolio optimization.
Option A is incorrect because managing customer relationship data is the function of CRM systems, not the CMDB. Option C is incorrect as tracking change management requests uses the change management module, though it references CMDB data for impact analysis. Option D is incorrect because maintaining service catalog item definitions is handled by the service catalog application rather than the CMDB.
Question 146:
Which type of ServiceNow workflow activity requires user input to proceed?
A) Approval activity
B) Notification activity
C) Script activity
D) Timer activity
Answer: A
Explanation:
The Approval activity in ServiceNow workflows represents a specific type of activity that requires explicit user input before the workflow can proceed to subsequent steps. This activity creates approval records and waits for designated approvers to make acceptance or rejection decisions. Approval activities are fundamental to implementing governance processes, ensuring that appropriate stakeholders review and authorize actions before they are executed. The workflow execution pauses at approval activities until all required approvals are granted or the approval is rejected.
When a workflow reaches an Approval activity, the platform generates approval records and sends notifications to assigned approvers. These notifications inform approvers of pending decisions and provide context about what they are approving. Approvers can respond through multiple channels including the ServiceNow interface, email responses, or mobile applications. The Approval activity configuration specifies who should approve, whether approvals are required from all approvers or just a majority, and how the workflow should proceed based on approval outcomes.
Approval activities support complex approval routing scenarios including sequential approvals, parallel approvals, and conditional approvals based on request attributes. Sequential approvals move through approvers one at a time, often representing organizational hierarchies where managers approve before executives. Parallel approvals send approval requests to multiple approvers simultaneously, proceeding when a configured threshold is met. Approval activities can implement escalation rules that notify additional approvers or managers if decisions are not made within specified timeframes.
The Approval activity integrates with ServiceNow’s approval framework, which maintains approval history, tracks approval chain details, and enforces approval policies. Approved records retain complete audit trails showing who approved requests, when approvals occurred, and any comments provided. This documentation supports compliance requirements and provides transparency into decision-making processes. Approval activities can trigger different workflow paths based on approval outcomes, enabling sophisticated process branching for approved versus rejected scenarios.
Option B is incorrect because notification activities send information to users but do not require user input to proceed. Option C is incorrect as script activities execute code automatically without requiring user interaction. Option D is incorrect because timer activities wait for specified time periods to elapse rather than requiring user input for continuation.
Question 147:
What is the function of the global search feature in ServiceNow?
A) To search only within the current module
B) To search across multiple tables and data sources
C) To search for knowledge articles exclusively
D) To search for users and groups only
Answer: B
Explanation:
The global search feature in ServiceNow provides comprehensive search capabilities across multiple tables and data sources within the platform, enabling users to quickly locate information regardless of where it resides. This unified search interface eliminates the need to know which specific table or module contains desired information, significantly improving productivity and information accessibility. Global search returns results from various sources including incidents, changes, problems, knowledge articles, users, configuration items, and custom application data.
Global search employs intelligent indexing and ranking algorithms to present the most relevant results based on user queries. When users enter search terms, the platform searches across configured tables, examining multiple fields within each table to find matches. Results are organized by table type, allowing users to filter and navigate to specific record types quickly. The search interface displays key information about each result, such as record numbers, titles, states, and relevant dates, helping users identify the correct record without opening each result.
The global search functionality is highly configurable, allowing administrators to control which tables are searchable, which fields are indexed for search, and how results should be ranked. Security permissions are respected during searches, ensuring users only see results for records they have access to view. The platform’s search infrastructure supports advanced query syntax including phrase searches, wildcards, and field-specific searches for power users who need precise query control. Recent enhancements have added natural language processing capabilities, improving the platform’s ability to interpret user intent.
Global search performance is optimized through background indexing processes that maintain search indexes for configured tables. These indexes are updated automatically as records are created or modified, ensuring search results reflect current data. Administrators can monitor search usage patterns and performance metrics to optimize search configurations. The global search feature integrates with mobile interfaces and is accessible through the main navigation bar, making it consistently available throughout the user experience.
Option A is incorrect because global search explicitly searches across the entire platform rather than limiting results to the current module. Option C is incorrect as global search covers many content types beyond just knowledge articles. Option D is incorrect because while users and groups are searchable, global search encompasses many additional record types and data sources.
Question 148:
Which ServiceNow feature enables automatic population of fields based on other field values?
A) Field Policies
B) Calculated Fields
C) Data Lookup Rules
D) Field Defaults
Answer: C
Explanation:
Data Lookup Rules in ServiceNow enable automatic population of fields based on values in other fields, typically by looking up information from related tables or reference data. These rules streamline data entry by automatically filling in related information when users select or enter values in trigger fields. Data Lookup Rules reduce manual data entry, improve data consistency, and help maintain data quality by populating information from authoritative sources rather than relying on user memory or manual lookups.
When a Data Lookup Rule is configured, it specifies a source field that triggers the lookup, a target table to query for information, matching criteria to find the correct record, and destination fields where retrieved information should be copied. For example, when a user selects a specific location in a form, a Data Lookup Rule might automatically populate the corresponding city, state, time zone, and building manager fields by looking up these details from the location record. This automation ensures consistency and accuracy while reducing the time required to complete forms.
Data Lookup Rules support both simple direct lookups and complex queries with multiple conditions. The rules can retrieve information from directly related tables through reference fields or perform more sophisticated queries based on matching criteria. Multiple fields can be populated from a single lookup operation, efficiently populating entire sections of forms with a single user action. The platform evaluates Data Lookup Rules when trigger field values change, ensuring populated data remains synchronized with source records.
Configuration of Data Lookup Rules requires understanding the relationship between tables and identifying which fields should trigger lookups versus which should receive populated data. Administrators can control when rules execute, set precedence for multiple rules targeting the same fields, and implement conditional logic to determine whether rules should apply in specific scenarios. Data Lookup Rules complement other automation features like business rules and workflows, working together to create seamless data entry experiences.
Option A is incorrect because field policies enforce data requirements and constraints but do not automatically populate field values based on lookups. Option B is incorrect as calculated fields compute values based on formulas rather than looking up information from other tables. Option D is incorrect because field defaults provide static initial values rather than dynamically looking up information based on other field values.
Question 149:
What is the purpose of scheduled jobs in ServiceNow?
A) To run automated tasks at specified times or intervals
B) To schedule user training sessions
C) To manage project timelines and deadlines
D) To schedule system maintenance windows
Answer: A
Explanation:
Scheduled jobs in ServiceNow enable automated execution of tasks at specifietimes or regular intervals, providing essential automation capabilities for system maintenance, data processing, and recurring business operations. These background jobs run server-side without user intervention, handling tasks such as data cleanup, report generation, integration synchronization, and automated notifications. Scheduled jobs are fundamental to maintaining system health and automating routine administrative functions.
The scheduled job framework supports various scheduling patterns including one-time execution at specific dates and times, recurring execution at fixed intervals, and cron-based scheduling for complex timing requirements. Administrators can configure jobs to run daily, weekly, monthly, or at custom intervals aligned with business needs. Each scheduled job specifies a script or function to execute when the schedule triggers, with the platform managing job queuing, execution, and error handling automatically.
Common use cases for scheduled jobs include purging expired records from audit tables to manage database size, generating and distributing scheduled reports to stakeholders, synchronizing data with external systems at regular intervals, and performing periodic checks for system issues or data anomalies. Scheduled jobs can also automate business processes such as sending reminder notifications for upcoming deadlines, updating record status based on time elapsed, and triggering escalations for overdue tasks. The flexibility of scheduled jobs makes them valuable tools for implementing time-based automation across diverse scenarios.
Monitoring and managing scheduled jobs requires attention to execution history, performance metrics, and error conditions. ServiceNow provides interfaces for viewing scheduled job execution logs, analyzing execution duration trends, and identifying failed jobs requiring attention. Administrators can manually trigger jobs for testing or urgent execution needs, temporarily disable jobs during maintenance, and adjust schedules based on changing requirements. The platform’s job queue management ensures efficient resource utilization and prevents conflicts between simultaneously scheduled jobs.
Option B is incorrect because scheduling user training sessions is managed through training management systems or calendar applications, not scheduled jobs. Option C is incorrect as managing project timelines uses project management tools rather than the scheduled jobs feature. Option D is incorrect because while scheduled jobs might run during maintenance windows, scheduling the actual maintenance windows is handled through change management and maintenance scheduling processes.
Question 150:
Which ServiceNow table stores information about system properties?
A) sys_properties
B) sys_config
C) sys_settings
D) sys_parameters
Answer: A
Explanation:
The sys_properties table in ServiceNow serves as the central repository for storing system property definitions and values that control platform behavior and feature configurations. System properties act as configuration parameters that administrators can adjust to customize how ServiceNow functions without modifying source code. These properties influence diverse aspects of the platform including security settings, performance parameters, feature enablement, integration configurations, and user interface behaviors.
System properties stored in the sys_properties table include property names, current values, data types, descriptions, and metadata about property usage. Each property has a unique name that follows a dotted notation convention, often indicating which functional area or feature the property affects. Property values can be strings, numbers, booleans, or references to other records, depending on the configuration parameter being controlled. The table maintains both out-of-box properties provided by ServiceNow and custom properties created by administrators for application-specific configurations.
Accessing system properties can be done through the System Properties module in the navigation menu or by directly querying the sys_properties table. Many properties can be modified directly through the interface, while others may require administrative privileges or specific knowledge to change safely. ServiceNow documentation provides guidance on which properties are safe to modify and the potential impact of changes. Some properties take effect immediately upon change, while others may require system restarts or cache clearing to apply changes.
System properties enable administrators to fine-tune platform behavior to match organizational requirements without requiring custom code development. Examples of commonly modified properties include session timeout durations, attachment size limits, email notification settings, and feature activation flags. The sys_properties table supports property scoping for multi-application environments, allowing different applications to maintain separate property values. Best practices recommend documenting property changes and testing modifications in non-production environments before applying to production instances.
Option B is incorrect because sys_config is not a standard ServiceNow table for storing system properties. Option C is incorrect as sys_settings does not exist as the standard table for system configurations. Option D is incorrect because sys_parameters is not the correct table name for storing system property information in ServiceNow.