ServiceNow Certified System Administrator CSA (SNOW-CSA) — Questions 1–75

Why this answer

How to eliminate wrong answers

Option A is wrong because the SLA does not pause and resume; it stops when the condition is no longer met, and a new instance starts when the condition is met again. Option C is wrong because the SLA does not resume with the same elapsed time; it stops completely and a new SLA instance begins with a fresh timer. Option D is wrong because the SLA does not continue running; it is condition-based, and once the priority changes away from 1, the condition fails and the SLA stops.

Why this answer

How to eliminate wrong answers

Option B is wrong because the flow logs show the trigger fired, which means the state field was properly referenced and the condition was met; if the state field were not properly referenced, the trigger would not have fired. Option C is wrong because if the flow were deactivated, the trigger would not fire at all, and the flow logs would not show the trigger firing. Option D is wrong because email properties (e.g., glide.email.smtp.enable) block all outbound email globally, not just for a specific flow; if an email property were blocking, the flow logs would typically show an error or the email would fail for all flows, not just this one.

Why this answer

How to eliminate wrong answers

Option A is wrong because the script already has a condition check (the if-else block after the get call), so missing a condition check is not the issue. Option B is wrong because the variable 'inputs.user_sys_id' is correctly referenced and would be passed if the get method syntax were correct; the problem is not with the variable itself but with how it is used in the get method. Option C is wrong because the 'get' method does not accept a table name as the first parameter; the table is already set when the GlideRecord is instantiated with 'sys_user'.

Why this answer

How to eliminate wrong answers

Option A is wrong because a Bar chart report is a visualization type, not a report type that supports automatic updating of aggregated data; it requires a data source that must be manually refreshed or scheduled. Option B is wrong because a Pivot table report is designed for cross-tabulation and grouping, not for automatically updating a single average metric over time; it would need manual re-run to reflect new incidents. Option C is wrong because a Scorecard report is used for performance indicators with targets and thresholds, not for simple average calculations; it relies on pre-defined metrics that do not automatically update with new incident resolutions.

Why this answer

Why this answer

How to eliminate wrong answers

Option B (Catalog Client Script) is wrong because client scripts are used for client-side validation or dynamic behavior, but they require JavaScript and are not the recommended method for simply making a variable mandatory based on another variable's value; UI Policy is the declarative, no-code alternative. Option C (ACL) is wrong because Access Control Lists govern data access permissions (read/write/delete) on records, not form-level variable behavior like mandatory conditions. Option D (Variable Condition) is wrong because variable conditions are used to show or hide variables, not to enforce mandatory status; they control visibility, not requiredness.

Why this answer

How to eliminate wrong answers

Option A is wrong because duplicate rows in the CSV would cause duplicates only if the transform map does not use coalesce to deduplicate; the question states 'several records are duplicated' implying the issue is systematic, not just repeated rows. Option B is wrong because an index on the number field would help enforce uniqueness and prevent duplicates, not cause them—indexes improve lookup performance but do not control import deduplication logic. Option D is wrong because exceeding the import set row limit would cause the import to fail or truncate, not create duplicate records; the limit caps the number of rows processed per import set run.

Why this answer

How to eliminate wrong answers

Option B (Approval Engine) is wrong because it is a process component that manages approval workflows, not a self-service feature for submitting requests; it requires a record to already exist. Option C (SLA Definition) is wrong because it defines service level agreements and time-based targets, not a mechanism for users to submit requests. Option D (Flow Designer) is wrong because it is a tool for designing automated workflows and processes, but it does not provide a direct user-facing self-service submission interface like a Record Producer does.

Why this answer

How to eliminate wrong answers

Option B is wrong because using a business rule to set a field indicating editability and then an ACL on that field adds unnecessary complexity and latency; the ACL script condition can directly evaluate the relationship without needing an extra field or business rule. Option C is wrong because creating a separate role for each manager is not scalable and violates role-based access control best practices; roles should represent job functions, not individual users. Option D is wrong because creating separate write ACLs for each manager's direct reports is administratively unsustainable and does not scale as the number of managers or direct reports changes; a single scripted ACL is far more efficient.

Why this answer

How to eliminate wrong answers

Option A is wrong because setting the business rule to 'async' would not change the operation it runs on; asynchronous execution still runs on the same event (before query) and would still affect queries, not solve the issue. Option B is wrong because client-side business rules do not exist in ServiceNow; business rules are always server-side, and the problem is about the event trigger, not the execution location. Option D is wrong because the condition script using 'gs.getUser().hasRole("ITIL")' is correct for checking role membership; the issue is not with the condition but with the business rule running on the wrong event.

Why this answer

How to eliminate wrong answers

Option B is wrong because the My Items module shows the individual catalog items (e.g., software, hardware) that have been provisioned to the user, not the status of the original service catalog request. Option C is wrong because the Service Catalog module is the interface for browsing and submitting new requests, not for tracking existing ones. Option D is wrong because the Requested Items related list is a back-end view typically found on the request record itself and is not exposed via the self-service portal for end users; it is used by fulfillers or administrators.

Why this answer

How to eliminate wrong answers

Option B is wrong because if the user did not fill in the variable, the value would be empty on the RITM as well, but the question states the hardware team cannot see the choice, implying the value exists somewhere but is not visible on their task. Option C is wrong because the variable is already on the 'Request' form (the catalog item's variable form), which is where the user submitted it; the issue is not about the request form but about the task form not displaying it. Option D is wrong because making a variable mandatory only enforces that the user must provide a value before submission; it does not affect whether that value is propagated to downstream tasks.

Why this answer

How to eliminate wrong answers

Option A is wrong because a Data Lookup definition is used to populate a variable from a database table based on a lookup field, not to dynamically compute a value like the current user's manager email. Option B is wrong because a Flow Designer action runs after the form is submitted, not on form load, so it cannot pre-populate the variable before the user sees the form. Option C is wrong because an onChange Catalog Client Script triggers only when a specific variable changes, not on form load, and cannot automatically populate a field without a triggering event.

Why this answer

How to eliminate wrong answers

Option A is wrong because upgrading to a newer release may include general performance improvements, but it does not address the specific issue of excessive UI policies causing slow 'getFormMeta' calls; the problem is configuration-based, not version-based. Option B is wrong because the system property 'glide.ui.form.load.max_sections' limits the number of visible sections on a form, but the Incident form's load time issue is due to UI policies, not the number of sections; this property would not reduce the metadata processing overhead. Option C is wrong because converting client scripts to UI policies would actually increase server-side processing during form load, as UI policies execute on the server when the form is loaded, whereas client scripts run client-side after the form loads; this change would worsen, not improve, load times.

Why this answer

How to eliminate wrong answers

Option B is wrong because business rule order only affects the sequence of execution among multiple rules on the same table and same phase; it does not prevent a single rule from executing or saving field changes. Option C is wrong because the administrator explicitly created the rule as an 'after' business rule, and the issue is not about the phase but about missing persistence of field updates. Option D is wrong because the work_notes field does not need to be on the form for a business rule to set it; business rules operate at the database layer and can modify any field regardless of form configuration.

Why this answer

How to eliminate wrong answers

Option A is wrong because the script runs on every load and sets the category to 'software' regardless of whether the user changes it; the user's change would be overwritten on the next load, not preserved. Option C is wrong because `g_form.setValue` is the correct method for setting a field's value in an `onLoad` client script; `g_form.setDisplay` controls visibility, not value assignment, and no error occurs. Option D is wrong because the script executes on every page load irrespective of the field's visibility; visibility does not affect the execution of `onLoad` scripts.

Why this answer

How to eliminate wrong answers

Option A is wrong because if a custom field is not marked as 'Active' in the dictionary, it would not appear in the form or be available for data entry, but discovery updates are driven by the identification and reconciliation engine, not the field's active state. Option B is wrong because discovery probes operate at the system level and do not have field-level access controls; they use MID servers and credentials to collect data, and any field that exists in the table can be populated if the probe is configured to collect it. Option D is wrong because a 'stale glide record' is not a standard ServiceNow concept; records can be stale due to reconciliation rules or update failures, but this is a symptom, not a root cause, and the issue is specifically about identification rules not including custom fields.

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because 'Send when record is updated' triggers the notification once per update transaction, not multiple times; multiple business rules firing would still result in a single notification per update unless they explicitly call the notification action. Option B is wrong because 'Send to all users in the role' sends one email per user, but the issue is duplicate emails for the same user, not multiple recipients. Option C is wrong because the 'cmdb_ci' field update would not cause the notification to fire unless the condition explicitly checks that field; the condition is set to 'Priority changes to 1 - Critical', so unrelated field updates do not trigger it.

Why this answer

How to eliminate wrong answers

Option B is wrong because scheduling the SLA job only during business hours would delay SLA processing for incidents created outside those hours, potentially causing breaches due to late evaluation and violating business requirements. Option C is wrong because disabling SLA evaluation for low-priority incidents changes the business requirements by removing SLA coverage for those incidents, which is not allowed per the question. Option D is wrong because increasing the SLA job interval from 1 minute to 5 minutes reduces execution frequency but does not address the root cause of excessive processing per execution; it would simply delay breach detection and could worsen the backlog of queued jobs.

Why this answer

How to eliminate wrong answers

Option B is wrong because Client Scripts are used for client-side logic like field validation or value manipulation, not for controlling variable visibility based on variable values. Option C is wrong because Catalog Client Scripts are designed for scripting on catalog forms (e.g., onChange or onSubmit), but they require JavaScript code and are not the declarative, no-code feature intended for simple show/hide conditions. Option D is wrong because Access Control Lists (ACLs) control data access and security permissions, not the visibility of form fields or variables.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because if the user lacked the appropriate role to view the item, the item would not appear in the catalog at all, not just fail when clicked. Option B is wrong because a misconfigured Service Portal catalog page would typically cause display or navigation issues, not a specific 'Item not available' error tied to a single item's availability logic. Option D is wrong because if the catalog item were set to 'Inactive', it would not be visible to any user in the Service Portal, contradicting the scenario where the user can see it.

Why this answer

How to eliminate wrong answers

Option A is wrong because `sys_app` stores the application record itself (e.g., name, vendor, version), not the menu or module definitions. Option C is wrong because `sys_ui_module` is a legacy table for UI modules in the old UI16 navigator, not the current standard for application menu/module definitions. Option D is wrong because `sys_app_module` does not exist as a standard table in ServiceNow; the correct table for modules within an application is `sys_app_application`.

Why this answer

How to eliminate wrong answers

Option A is wrong because it uses a condition script checking 'current.assignment_group == gs.getUser().getMyGroups()', which is irrelevant to the requirement of blocking updates based on record creator; it would incorrectly allow or deny updates based on group membership, not creator identity. Option B is wrong because it leaves the condition script empty and unchecks 'Requires role', which would apply the ACL to all users regardless of role, failing to restrict only users with the 'itil' role and potentially blocking all users from updating the table. Option D is wrong because it uses the condition script 'current.created_by == gs.getUserID()', which returns true for the record creator, thus allowing updates for the creator but also inadvertently allowing updates for any user who matches the creator condition; however, the requirement is to block all updates except for the creator, so the condition should deny when the user is not the creator, not allow when they are.

Why this answer

How to eliminate wrong answers

Option A is wrong because relationship rules are defined between CI classes, and if the discovered CIs belong to classes that do not have relationship rules, the IRE would still create the CIs but simply not populate relationships; the question states that relationships are missing, not that the CIs themselves are missing. Option C is wrong because the IRE's 'reconcile only' mode prevents creation of new CIs but does not affect relationship creation; relationships are created by Discovery probes/sensors, not by the IRE. Option D is wrong because if the relationship type were not defined in the CMDB, Discovery would still create the CIs and the relationship would simply be stored with a generic or default type, not be entirely absent.

Why this order

Why these pairings

Why this answer

How to eliminate wrong answers

Option A is wrong because a scheduled job that deletes old CIs would remove CIs based on age or last updated time, not cause duplicate serial numbers with different names and IP addresses. Option B is wrong because a unique constraint on the name field would prevent duplicate names, but the issue here is duplicate serial numbers with different names, so a name constraint would not cause or prevent this problem. Option D is wrong because setting the reconciliation rule to 'Create' instead of 'Update' would cause new CIs to be created on every import, but it would not specifically result in the same serial number appearing on multiple CIs with different names and IPs; the identification rule is what controls how duplicates are detected.

Why this answer

How to eliminate wrong answers

Option A is wrong because Discovery does not fail; the IRE processes the CI and either creates or updates based on the identification rule, not failing due to a name match with a different attribute. Option B is wrong because the existing CI will not be updated with the new business_service; the IRE only updates CIs when all identification attributes match, and since business_service is not part of the identification rule, a name match alone does not trigger an update. Option D is wrong because the identification rule does not match based on name only; it matches based on the defined identification attributes (name), but the rule's behavior is to create a new CI when the business_service differs, not to ignore it.

Why this answer

How to eliminate wrong answers

Option A is wrong because using an 'On Before' script to check for existing records is unnecessary overhead and not the standard, built-in mechanism for ignoring duplicates during imports; the platform provides the coalesce feature for this exact purpose. Option B is wrong because the 'Reject duplicates' checkbox on a transform map does not exist; this is a fictitious option that might confuse candidates into thinking there is a simple toggle for deduplication. Option D is wrong because configuring a business rule on the target table to reject duplicates would run after the import attempt, potentially causing errors or requiring complex logic, and it is not the recommended or efficient approach for ignoring duplicates during the import process.

Why this answer

How to eliminate wrong answers

Option A is wrong because 'setValue' sets the field's internal value, while 'setDisplayValue' sets the display value for choice fields; using 'setValue' is correct for setting a field value and would not prevent the field from being set. Option C is wrong because the condition 'Current state changes' being unchecked means the rule runs on every update regardless of state change, which would not prevent the field from being set; in fact, it would make the rule run more often. Option D is wrong because a business rule set to run on 'display' would not execute during an update operation at all; it would only run when the record is viewed, so it would never set the field during save, but the question states the rule 'runs on the Incident table during update', implying it is configured to run on update, not display.

Why this answer

How to eliminate wrong answers

Option A is wrong because ACLs do not block business rules from writing to fields; they only restrict direct user operations, and the priority is set by the business rule before any ACL evaluation occurs. Option B is wrong because the business rule does not run 'before' the ACL check in a sequential sense—business rules execute with system privileges, bypassing ACLs entirely, not because of timing. Option C is wrong because the update does not fail; business rules run with full system privileges, so the priority is set to 1 without any ACL failure.

Why this answer

How to eliminate wrong answers

Option A is wrong because a business rule on the CI class can trigger on state change, but it lacks the lifecycle-aware context and built-in relationship handling that the CI Lifecycle Manager provides; it would require custom scripting to manage all related services. Option C is wrong because manually editing each relationship via the Relationship Viewer is not scalable and contradicts the goal of automation. Option D is wrong because a scheduled job introduces latency and complexity, and it does not provide real-time, event-driven updates when a CI is retired, unlike the lifecycle framework.

Why this answer

Why this answer

How to eliminate wrong answers

Option B is wrong because removing the incident from the SLA definition condition would modify the definition itself, potentially affecting future incidents that match the condition, and it does not stop tracking for the specific incident already attached. Option C is wrong because setting the SLA definition to inactive would stop all SLA tracking for any incident using that definition, not just the specific incident. Option D is wrong because deleting the SLA record from the SLA table would remove the historical data and could cause errors or data integrity issues; the correct approach is to cancel the SLA on the indicator, not delete the record.

Why this answer

Why this answer

How to eliminate wrong answers

Option B is wrong because enabling Form Layout Personalization allows users to hide fields client-side, but the fields are still loaded in the DOM and their reference data is still fetched, so it does not improve form load performance. Option C is wrong because removing fields from the default view affects all users and can break workflows or hide required fields, reducing usability without a targeted approach. Option D is wrong because using Form Sections to collapse fields into tabs only hides them visually; all fields and their reference lookups are still loaded when the form opens, so performance remains unchanged.

Why this answer

Why this answer

How to eliminate wrong answers

Option B is wrong because the 'Run once' option would cause the job to execute only a single time, which would not produce duplicates across multiple runs. Option C is wrong because the operator used in the report condition ('=' vs 'starts with') affects string matching logic, not the creation of duplicate tasks from the same source data. Option D is wrong because while running too frequently could create multiple tasks if the report is not filtered, the frequency itself is not the root cause; the core issue is the lack of a filter to prevent re-processing already-handled records.

Why this answer

How to eliminate wrong answers

Option A is wrong because a business rule running on 'after update' does not inherently cause duplicate emails; it is the trigger for the notification, and duplicates would only occur if the notification itself has multiple recipients or multiple triggers. Option C is wrong because having two separate conditions that both evaluate to true would cause the notification to fire twice only if the notification is configured to send for each condition separately, but by default, a single notification with multiple conditions still sends one email per record update. Option D is wrong because 'Send for each record' is used for batch updates or multiple records, not for a single record being updated multiple times; duplicate emails from multiple updates would require the notification to be triggered on each update, not the 'Send for each record' setting.

Why this answer

How to eliminate wrong answers

Option A is wrong because the SLA schedule (24x7) would not prevent the SLA from starting; it only defines when time counts toward the SLA, not whether the SLA starts. Option B is wrong because a pause condition would stop an already-running SLA, not prevent it from starting; the issue is that the SLA never starts. Option D is wrong because the SLA definition is explicitly configured on the 'incident' table (as stated in the question), so being on the 'task' table would not apply here and would not cause this behavior.

Why this answer

How to eliminate wrong answers

Option A is wrong because 'Single Line Text' variables fully support hiding via client scripts; there is no restriction on variable type for hiding. Option B is wrong because while `g_form.setDisplay()` is the correct method to hide a variable, the issue is not its absence but rather the variable's display property overriding the script's attempt. Option C is wrong because an 'onSubmit' script runs at form submission, not on variable change, so it would not dynamically hide the variable when the triggering field changes; 'onChange' is the correct type for this behavior.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because Flow Designer, while capable of automation, is a more complex, low-code tool that is not the simplest out-of-box solution for this specific routing need; it would be overkill and could require additional configuration beyond the basic assignment rule. Option C is wrong because setting a Default Assignment on the Record Producer would assign all requests from that producer to the software group, regardless of the category selected, which does not meet the requirement of routing based on the requested software category. Option D is wrong because an Access Control Rule (ACL) controls data visibility and edit permissions, not routing or assignment logic; it would not automate the assignment of requests.

Why this answer

How to eliminate wrong answers

Option A is wrong because Dictionary Override is used to modify field-level properties (e.g., label, default value, reference qualifier) for a specific table or view, not to add sections to a form. Option B is wrong because Application Navigator is used to configure the left-hand navigation menu (modules and applications) in the platform, not to edit form layouts. Option C is wrong because UI Policy is used to dynamically show/hide fields or make them mandatory based on conditions, not to add structural sections to a form.

Why this answer

How to eliminate wrong answers

Option A is wrong because 'Integer' is used for numeric values that support arithmetic operations, not for descriptive text like 'short_description'. Option C is wrong because 'Reference' is a data type that links to a record in another table via a sys_id, not for storing free-text descriptions. Option D is wrong because 'Date' is used for calendar dates without time components, whereas 'short_description' holds arbitrary text strings.

Why this answer

How to eliminate wrong answers

Option A is wrong because increasing the instance size (vertical scaling) is a costly infrastructure change that does not address the root cause of inefficient widget rendering and may not be feasible or necessary; it also violates the constraint of not changing the user interface only indirectly. Option B is wrong because removing all widgets from the homepage would drastically alter the user interface and degrade the portal's functionality, contradicting the requirement to not change the UI. Option C is wrong because disabling the search feature would remove a core self-service capability, negatively impacting user experience and violating the requirement to maintain the existing interface.

Why this answer

How to eliminate wrong answers

Option A is wrong because sharing a report link via email does not grant dashboard access; it only shares a static snapshot or link that may fail due to ACL restrictions, and it requires individual recipients to have appropriate permissions. Option B is wrong because ServiceNow dashboards do not have a 'Public' setting; visibility is controlled via roles, not a public toggle, and making a dashboard public would violate security best practices. Option C is wrong because publishing a dashboard to a homepage only makes it visible on that specific homepage, not to the entire team, and homepage visibility is still governed by role-based access controls.

Why this answer

How to eliminate wrong answers

Option A is wrong because business rules on the request table would require custom scripting and are not the recommended or best practice method for automatic assignment; they are more suited for data validation or complex logic. Option C is wrong because the 'Assigned to' field in the catalog item definition is not a standard field; catalog items define variables and workflow, not direct assignment fields, and setting it there would not trigger automatic assignment to a group. Option D is wrong because while Flow Designer can be used for assignment, it is an over-engineered solution for this simple requirement; assignment rules are the native, lightweight, and best-practice mechanism for automatic assignment based on catalog item conditions.

Why this answer

How to eliminate wrong answers

Option A is wrong because 'Reference qualifier' is used to filter which records from the referenced table are available for selection, not to control the displayed value. Option B is wrong because 'Choice field' is a separate field type that presents a predefined list of options, not a property of a reference field. Option C is wrong because 'Default value' sets the initial value of the field when the form loads, not the display format of the referenced record.

Why this answer

How to eliminate wrong answers

Option B is wrong because a Form module type is used to display a single record form for creating or editing a record, not a list of multiple users. Option C is wrong because a URL module type is used to link to an external or internal URL, such as a webpage or a report, not to display a native list of records from a table. Option D is wrong because a Report module type is used to display a report (e.g., chart, pivot table) based on a data source, not a standard list view of records.

Why this answer

How to eliminate wrong answers

Option A is wrong because it assumes the entire 2-hour SLA duration was consumed, but the SLA was paused for 30 minutes while on hold, so the actual elapsed time is less. Option B is wrong because it incorrectly calculates from the first state change at 10:30 to resolve at 12:00, which is 1 hour 30 minutes, but this ignores the initial 30 minutes in 'New' state that also counts toward the SLA. Option D is wrong because it only counts the time after the hold period (11:30 to 12:00), omitting the 30 minutes in 'New' and the 30 minutes in 'In Progress' before the hold.

Why this answer

How to eliminate wrong answers

Option A is wrong because the 'Use schedule for progress' checkbox controls whether the schedule affects the SLA's progress indicator, not the breach time calculation; even if unchecked, the schedule still applies to the breach time if attached. Option B is wrong because if the business schedule were not attached, the SLA would use the default 24/7 schedule, which would not exclude weekends, but the question states the schedule excludes weekends, implying it is attached; the issue is the condition not being met. Option D is wrong because an incorrect time zone would shift the breach time by a few hours, not cause the weekend to be included; the breach time would still respect the schedule's exclusion of weekends if the condition were met.

Why this answer

How to eliminate wrong answers

Option A is wrong because a missing email template would cause a rendering error or blank email, not a failure to send the notification; the notification would still be triggered and attempted. Option C is wrong because having no members in the assignment group would prevent assignment to an individual, but the notification condition is based on the `assigned_to` field change, not group membership; the incident can still be assigned to a group without members, and no notification would fire because `assigned_to` did not change.

Why this answer

How to eliminate wrong answers

Option A is wrong because current.state.changesTo(3) is a valid condition that triggers when the state changes to 3 (Closed Complete); checking if the state is already 3 would not capture the transition. Option C is wrong because a reference variable stores the sys_id of the referenced record, not the display value, so the variable itself is not the issue. Option D is wrong because the business rule runs 'After' (as indicated by the 'after' keyword in the exhibit), so the state has already changed; running 'Before' would prevent the state change from being committed.

Why this answer

How to eliminate wrong answers

Option A is wrong because a missing coalesce on the assigned_to field would cause that specific field to map as null or fail, but it would not prevent the entire transform from creating or updating records—other fields would still be processed. Option B is wrong because if the staging table does not match the target table, the transform would typically fail with a schema mismatch error or produce a different symptom, such as a 'table not found' error, not zero records with no error. Option D is wrong because an incorrectly set coalesce field would only affect the coalesce logic for a specific field, not cause the entire transform to produce zero records; it might result in duplicate detection issues or null values, but records would still be created or updated.

Why this answer

How to eliminate wrong answers

Option A is wrong because the reference qualifier restricts which records are available for selection, but it does not affect how the selected record's value is displayed in variable substitution. Option C is wrong because if the variable type were not a reference field, the variable substitution would likely fail or show an empty value, not the sys_id. Option D is wrong because variable substitution uses the variable name (e.g., '${variable_name}'), not the field name; using the field name would cause the substitution to not resolve at all.

Why this answer

How to eliminate wrong answers

Option A is wrong because 'g_user.hasRole' is the correct method to check for role membership; 'g_user.hasRoleExactly' is not a valid method in ServiceNow and would cause a script error. Option C is wrong because table-level ACLs control record-level access (read, write, etc.), not form section visibility; they do not affect whether a section is shown or hidden on a form. Option D is wrong because the 'Roles' field on a section controls visibility based on role membership, but it is empty, meaning no role restriction is applied; setting it to 'security_admin' would actually be an alternative way to restrict visibility, but the issue is that the section is not showing despite the UI Policy, so the empty Roles field is not the cause.

Why this answer

How to eliminate wrong answers

Option A is wrong because 'update_set.list' uses an incorrect table name; the actual table is 'sys_update_set', not 'update_set'. Option C is wrong because 'sys_update.set.list' incorrectly places a dot between 'update' and 'set', which does not match the table name 'sys_update_set'. Option D is wrong because 'update_sets' is not a valid filter path; it lacks the '.list' suffix and does not reference the correct table name.

Why this answer

How to eliminate wrong answers

Option A is wrong because the business rule that triggers SLA recalculation is responsible for updating the SLA after changes, but it does not directly control the pause behavior; a misconfigured pause condition would still cause the timer to run even if the recalculation rule is active. Option B is wrong because checking the SLA metric timeline shows historical data on timer states but does not identify why the pause condition failed to trigger; it is a diagnostic tool, not the first step in troubleshooting a configuration issue. Option D is wrong because the SLA schedule's 'Pause' field is used to define non-working hours or holidays that pause the timer, not to pause the timer based on a specific incident state like 'Awaiting Customer'; that state-based pause is controlled by the pause condition on the SLA definition itself.

Why this answer

Why this answer

How to eliminate wrong answers

Option B is wrong because reordering workflow activities does not address the root cause; the mandatory field validation is a client-side check that occurs before the workflow starts, so moving activities within the workflow will not enforce server-side validation. Option C is wrong because changing the variable type to 'Email' only changes the input format validation (e.g., requiring an '@' symbol), but it does not enforce that the field is non-empty; the mandatory attribute is still client-side and can be bypassed. Option D is wrong because setting the variable to 'Read only' and populating it from a reference field would prevent manual entry but does not solve the intermittent empty value issue; it also changes the data source and may not align with the requirement for free-text entry.

Why this answer

How to eliminate wrong answers

Option A is wrong because an unpublished flow will not trigger at all, but the question states the flow is running (it is not creating the task record), so the flow must be published. Option C is wrong because the 'Create Record' action does not require a 'number' field; the 'number' field is auto-generated by the system when the record is saved. Option D is wrong because if the trigger conditions were incorrectly referencing the catalog item, the flow would not trigger at all, but the flow is triggering (it is just not populating the variables).

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because the script explicitly compares `current.caller_id` to `gs.getUserID()`, which returns the current user's sys_id; if the user is editing their own incident, this condition returns true, not false. Option B is wrong because the ACL is explicitly applied to the Incident table for 'write' operation, as stated in the question, and the exhibit shows the ACL type is 'record' with operation 'write', so it is not set to 'read'. Option C is wrong because the ACL does not require a role; it uses a script condition, and the question does not indicate that a role is missing or that the user lacks any required role.

Why this answer

How to eliminate wrong answers

Option B is wrong because there is no 'Reset' attribute on a form; the form's 'Reset' attribute is not a valid mechanism in ServiceNow for clearing user personalizations. Option C is wrong because running a scheduled job to clear all user preferences would remove all preferences for all users, which is overly broad and not targeted to resetting a single user's form layout. Option D is wrong because the 'Restore Default' button on the form resets the current session's view for the administrator, not the user's personalization; it does not clear the user's saved preference.

Why this answer

How to eliminate wrong answers

Option A is wrong because an Approval - Group activity sends the request to an entire group (e.g., 'Manager's Group'), not to the specific manager of the user, and it lacks a condition to trigger only when cost exceeds $500. Option B is wrong because setting a variable as 'Required If' only controls whether the variable must be filled in, not whether an approval step runs; it does not add any approval logic. Option D is wrong because an Approval Group activity (like Option A) requires a group, not a single user, and adding the manager as a member does not create a conditional approval based on cost.

Why this answer

How to eliminate wrong answers

Option A is wrong because the script does not only run on load; it runs on the blur event (when the user tabs out), so it actively validates the input. Option B is wrong because the field type being 'email' does not guarantee successful submission; the custom script overrides default behavior and performs its own validation, which fails here. Option D is wrong because the script explicitly clears the entered value upon validation failure, not just showing an error message while retaining the value.

Why this answer

How to eliminate wrong answers

Option A is wrong because there is no coalesce conflict; the coalesce field 'number' matches exactly one existing record, so the transform proceeds with an update. Option B is wrong because a new record is created only when no matching record is found via the coalesce field; here a match exists. Option C is wrong because the coalesce field 'number' is valid and correctly configured to identify duplicates; it is not invalid.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because if the flow were deactivated, it would not run at all, but the question states the flow is 'scheduled' and not triggering, implying it is active but not executing as expected. Option C is wrong because scoping issues typically cause flows to fail on execution or not be visible, but they do not prevent a scheduled flow from triggering based on its schedule; the trigger type is the primary factor. Option D is wrong because the condition 'state = requested' is correct for filtering approval records that need reminders; an incorrect condition would cause the flow to run but not process records, not fail to trigger entirely.

Why this answer

How to eliminate wrong answers

Option B (read) is wrong because the read ACL controls the ability to view records, and the user can already view them, so the read ACL is not preventing the edit. Option C (create) is wrong because the create ACL controls the ability to insert new records, not edit existing ones. Option D (delete) is wrong because the delete ACL controls the ability to remove records, not modify them.

Why this answer

How to eliminate wrong answers

Option A is wrong because combining variables into a single 'Additional Details' text area variable removes variables, which contradicts the goal of not eliminating any variables. Option B is wrong because converting Catalog Client Scripts to Catalog UI Policies does not reduce client-side processing; UI Policies also execute on the client and can still cause performance issues, and they are not designed to replace all client script logic. Option D is wrong because enabling 'Cache Catalog Item' caches the form data after the first load, but it does not improve the initial render time; the slow load issue is about the first load, not subsequent loads.