SNOW-CAD Working with Data Practice Test 4 — 15 Questions

Question 1

Refer to the exhibit. What does this data policy do?

Accepted Answer

Makes 'short_description' mandatory when state is '1' (New).. The data policy sets the 'short_description' field as mandatory when the 'state' field equals '1' (New). Option A is wrong because it says mandatory when state is New, but the condition is on state, not on short description. Option C is wrong because it reverses the condition. Option D is wrong because it ignores the condition.

Answer

Makes 'short_description' mandatory for all incidents regardless of state.

Answer

Makes 'state' mandatory when 'short_description' is empty.

Answer

Makes 'short_description' read-only when state is '1'.

Question 2

Refer to the exhibit. What is the purpose of this transform script?

Accepted Answer

To map the department field only if source department is not empty.. The transform script maps the 'department' field only if the source field 'u_department' is not empty, as indicated by the conditional logic. Option A is incorrect because the script does not ignore records; it only skips mapping for empty departments. Option C is incorrect because no default value is set; the field is simply not mapped if empty. Option D is incorrect because only the department field is mapped conditionally, not all fields.

Answer

To ignore records with empty department.

Answer

To set a default value for the department field.

Answer

To map all fields from source to target.

Question 3

Refer to the exhibit. What does this ACL condition allow?

Accepted Answer

Users with 'itil' role can update incidents in state 'On Hold'.. The ACL condition grants update access when the user has the 'itil' role and the incident state is '3', which is 'On Hold'. Option A is incorrect because it ignores the role requirement. Option B is wrong because it says users without 'itil' role can update, but the ACL requires the 'itil' role. Option C is wrong because state '3' is 'On Hold', not 'Resolved'.

Answer

Any user can update incidents when state is '3'.

Answer

Only users without 'itil' role can update incidents in state '3'.

Answer

Users with 'itil' role can update incidents in state 'Resolved'.

Question 4

A developer needs to update a large number of records in the 'incident' table based on a specific condition. Which approach should be used to minimize performance impact?

Accepted Answer

Use GlideRecord with setWorkflow(false) and setEngine(false) to update records in a loop.. A is correct because using GlideRecord with setWorkflow(false) and setEngine(false) prevents unnecessary business rules and workflow execution, reducing performance impact. B is incorrect because GlideAggregate is used for aggregation and statistics, not for updating records. C is incorrect because an export set is designed for data export/import, not for bulk updates within the platform. D is incorrect because updateMultiple does perform bulk updates but still triggers business rules if not disabled, and it does not provide the same level of control as GlideRecord with disabled workflows.

Answer

Use GlideAggregate to perform the update.

Answer

Use an export set to update records in bulk.

Answer

Use the updateMultiple method on a GlideRecord object.

Question 5

An admin created a new table 'u_custom_asset' with a reference field to 'cmdb_ci'. After creating a form, users report that when they select a CI, additional fields do not auto-populate as expected. What is the most likely cause?

Accepted Answer

The reference field lacks a reference qualifier or default value configuration for auto-population.. Reference fields on custom tables do not auto-populate other fields unless configured with a reference qualifier or default value. ACLs (B) would block read access, not auto-population. A business rule (C) is not necessary for basic auto-population. The cmdb_ci table (D) can be referenced from custom tables.

Answer

ACLs are blocking the read operation on the cmdb_ci table.

Answer

A business rule is missing on the reference field to trigger auto-population.

Answer

The cmdb_ci table is a system table and cannot be referenced from custom tables.

Question 6

During a data migration, a developer runs a GlideRecord query to load 100,000 records from an external source into the 'incident' table. The script times out after 60 seconds. Which optimization technique would be most effective to avoid the timeout?

Accepted Answer

Use GlideRecordBatch or a scheduled job to process records in smaller batches.. Using GlideRecordBatch or a scheduled job with incremental processing breaks the workload into manageable chunks, preventing the script from timing out. Option A is incorrect because setLimit(1000) only limits the number of records returned per query, but the migration requires all 100,000 records to be processed; it does not solve the timeout issue when processing large batches. Option B is incorrect because GlideAggregate is used for aggregation queries (e.g., counting records) and does not assist in batch insertion of records. Option C is incorrect because increasing the transaction timeout is a temporary workaround; it does not address the underlying efficiency problem and may lead to other performance issues.

Answer

Use setLimit(1000) to reduce the number of records per execution.

Answer

Use GlideAggregate to count records before insertion.

Answer

Increase the transaction timeout setting in the system properties.

Question 7

A user needs to generate a report that shows the count of incidents by category for the current month. Which table and field combination should be used in a report?

Accepted Answer

Use the 'incident' table with 'category' and 'sys_created_on'.. The incident table contains incident records, and the category field allows grouping incidents by category, while sys_created_on can be used to filter incidents created in the current month. Option A is incorrect because the cmdb_ci table is for configuration items, not incidents. Option B is incorrect because the task table includes multiple task types (incidents, problems, changes), so it's not specific to incidents. Option C is incorrect because the sys_user table stores user information, not incidents.

Answer

Use the 'cmdb_ci' table with 'install_status' and 'sys_created_on'.

Answer

Use the 'task' table with 'priority' and 'sys_updated_on'.

Answer

Use the 'sys_user' table with 'department' and 'sys_created_on'.

Question 8

An admin notices that a business rule on the 'incident' table that sets the 'assigned_to' field based on the caller's manager is not always firing. The rule is set to run 'Before' and 'Update'. What is the most likely reason?

Accepted Answer

The condition of the business rule is not met because it requires a specific field to change.. Business rules with conditions only fire when the condition is met. If the condition requires a specific field to change (e.g., 'assigned_to' or a related field), but the update does not include that field, the rule will not trigger. Option B is incorrect: asynchronous execution would still cause the rule to run, just not immediately. Option C is incorrect: ACLs control access to records, not business rule execution. Option D is incorrect: order 100 is the default and does not prevent firing; it only affects execution order among multiple rules.

Answer

The business rule is set to run asynchronously.

Answer

The user lacks the 'incident_edit' ACL.

Answer

The business rule order is set to 100, making it run too late.

Question 9

A developer writes a script include that uses GlideRecord to query a large table. The script is called multiple times in a single transaction. What is the best practice to optimize performance?

Accepted Answer

Use a single GlideRecord query with multiple conditions and call .getRowCount() at the end.. When a script include queries a large table multiple times in a single transaction, the best practice is to minimize database round-trips. Using a single GlideRecord query with multiple conditions (combined via OR/AND) reduces the number of queries executed. Calling .getRowCount() at the end forces the query to execute once and caches the result, avoiding redundant queries for counts. This is more efficient than separate queries (A), which each require a round-trip. createOrGetRecord (B) is designed for single-record operations and doesn't optimize multiple queries. setEncodeQuery(false) (D) disables encoding but does not improve performance for repeated calls.

Answer

Use separate GlideRecord queries for each call.

Answer

Use createOrGetRecord for each call to cache the result.

Answer

Use setEncodeQuery(false) to speed up the query.

Question 10

Which method should be used to delete all records in the 'incident' table where the state is 'Closed' and the sys_updated_on is older than 90 days?

Accepted Answer

GlideRecord.deleteMultiple(). GlideRecord.deleteMultiple() is the appropriate method to delete multiple records that match a specified query, such as all incidents in 'Closed' state updated over 90 days ago. Option B is incorrect because GlideAggregate is used for aggregation (e.g., counting, summing) and does not have a deleteMultiple() method. Option C is incorrect because GlideRecord.deleteRecord() only deletes the current single record (the one loaded into the GlideRecord object). Option D is incorrect because GlideRecord.setDelete(true) is not a valid method; deletion is performed via deleteRecord() or deleteMultiple().

Answer

GlideAggregate.deleteMultiple()

Answer

GlideRecord.deleteRecord()

Answer

GlideRecord.setDelete(true)

Question 11

A report on the 'incident' table shows duplicate counts due to the 'active' field being true for some records that shouldn't be counted. The report is using a simple count. How can the admin ensure only active incidents are counted?

Accepted Answer

Add a filter condition: 'active = true'.. Adding a filter condition 'active = true' in the report configuration ensures that only incidents where the active field is true are counted, eliminating duplicate counts from inactive records. Option B is incorrect because a business rule would modify data rather than filter the report. Option C is incorrect because removing the active field from the report does not filter records; it only hides the field display. Option D is incorrect because grouping by active field would separate counts by active status but still count all records including inactive ones.

Answer

Create a business rule to set active=false for certain records.

Answer

Remove the 'active' field from the report.

Answer

Group the report by the 'active' field.

Question 12

A developer is tasked with creating a reference field on a custom table that shows only 'Windows' servers from the 'cmdb_ci_server' table. What is the proper way to implement this?

Accepted Answer

Define a reference qualifier on the field with the condition 'os_type=Windows'.. In ServiceNow, a reference qualifier is used to filter the records that appear in a reference field's lookup. By defining a reference qualifier with the condition 'os_type=Windows', only Windows servers from the cmdb_ci_server table will be available for selection. Option A is incorrect because a choice list is not a reference field and cannot dynamically filter a reference based on a table. Option B is incorrect because a business rule can modify data but is not the standard mechanism to filter a reference field's picker. Option C is incorrect because a dynamic filter on a form typically applies to related lists or reports, not to the lookup of a reference field.

Answer

Use a choice list instead of a reference field.

Answer

Create a business rule that filters the reference field.

Answer

Create a dynamic filter on the form.

Question 13

Which TWO statements are true about GlideAggregate?

Accepted Answer

It provides methods like addAggregate and getAggregate.. Options C and D are correct. GlideAggregate extends the GlideRecord class (D) and provides methods like addAggregate and getAggregate (C) for performing aggregate queries on database tables. Option A is incorrect because getRowCount() is a method of GlideRecord, not the primary method for retrieving counts; GlideAggregate uses addAggregate('COUNT', 'field') and getAggregate() instead. Option B is incorrect because GlideAggregate can be used with any field, not just sys_id. Option E is incorrect because GlideAggregate works on a single table per query; to aggregate across multiple tables, you would need separate queries or database views.

Answer

It uses getRowCount() to retrieve the count.

Answer

It can only be used with sys_id fields.

Answer

It can aggregate data across multiple tables in a single query.

Question 14

Which TWO of the following are valid ways to reduce the number of database queries when processing multiple records in a script?

Accepted Answer

Use dot-walking to access related table fields.. The valid ways to reduce database queries when processing multiple records are A and C. Dot-walking (A) follows relationships without separate queries. GlideAggregate (C) performs aggregation server-side, reducing round trips. Option E is incorrect because using GlideRecord's get() method with a sys_id still executes a separate database query for each call, so it does not reduce queries. Options B and D increase queries: B uses multiple queries, and D uses getValue() which does not reduce queries since it accesses a field from an already retrieved record.

Answer

Use multiple GlideRecord queries for each record.

Answer

Use getValue() to retrieve field values individually.

Answer

Use GlideRecord's get() method with a sys_id set.

Question 15

Which TWO methods are commonly used to prevent performance issues when using GlideRecord in a client script?

Accepted Answer

Use GlideAjax to call a script include for server-side processing.. Options D and E are correct. Using GlideAjax to call a script include moves processing to the server, avoiding synchronous blocking and performance hits in the client. Using setLimit() reduces the number of records retrieved, minimizing data transfer and processing. Option A is incorrect because GlideRecord is not directly available in client scripts and attempting to use it can cause performance issues. Option B is incorrect because synchronous GlideRecord queries block the UI, degrading user experience. Option C is incorrect because business rules run server-side and do not address client-side performance; GlideAjax is the appropriate client-server communication method.

Answer

Use GlideRecord directly in client scripts.

Answer

Use synchronous GlideRecord queries for immediate results.

Answer

Use a business rule instead to perform the query.