Free ServiceNow CSA Practice Exam: ServiceNow Certified System Administrator

This free full-length ServiceNow CSA practice exam includes 60 original IT Mastery questions across the exam domains.

These are original IT Mastery practice questions. They are not official exam-owner questions, copied live-exam content, or exam dumps. Use them to preview question style and explanation depth before continuing with mixed sets, topic drills, and timed mocks in IT Mastery.

Count note: this page uses the full-length practice count maintained in the Mastery exam catalog. Some certification vendors publish total questions, scored questions, duration, or unscored/pretest-item rules differently; always confirm exam-day rules with the sponsor.

Exam snapshot

• Practice target: ServiceNow CSA
• Practice-set question count: 60
• Time limit: 90 minutes
• Practice style: mixed-domain diagnostic run with answer explanations

Full-length exam mix

Use this as one diagnostic run. IT Mastery gives you timed mocks, topic drills, analytics, code-reading practice where relevant, and interactive practice.

Practice questions

Questions 1-25

Question 1

Topic: Database Management and Platform Security

The following relationships exist:

• Kai is a member of the Service Desk group.
• Service Desk is assigned the x_acme_support.writer role.
• The writer role contains x_acme_support.reader.
• Task TASK001 is assigned to Service Desk.

Which statement correctly traces why Kai has the effective reader role?

Options:

• A. Kai receives the reader role because the reader role contains the group-assigned writer role.

• B. Kai receives the reader role through membership in a group assigned the containing writer role.

• C. Kai receives the reader role through assignment of a task to the group holding the writer role.

• D. Kai receives the reader role only if the group is also assigned the reader role directly.

Best answer: B

Explanation: ServiceNow users inherit roles assigned to groups in which they are members. When an assigned role contains another role, the contained role also becomes effective for those group members. Kai’s access path is therefore group membership, the writer role assigned to that group, and the reader role contained by the writer role.

Assigning a task to the Service Desk group routes work but does not grant roles or establish group membership. Role containment also operates from the containing writer role to the contained reader role, not in reverse.

• Task assignment identifies the group responsible for work but does not grant its roles to users.
• A separate reader-role assignment is unnecessary because the group-assigned writer role already contains it.
• Reversing containment misstates the relationship; the writer role contains the reader role.

Question 2

Topic: Self Service and Automation

An employee and the employee’s manager both satisfy an Available For user criterion and can find a catalog item. After the employee submits it, the manager cannot read the resulting sc_req_item record.

The existing read ACL allows the requested user or fulfillment group members. No Deny-Unless or field ACL applies. Managers must read only their direct reports’ requested items, without changing who can order.

Which administrative change best meets the goal?

Options:

• A. Add managers to the fulfillment group used by the existing ACL.

• B. Add direct managers as approvers in the item’s fulfillment flow.

• C. Add an sc_req_item read Allow-If for requested users’ managers.

• D. Add managers to the item’s Available For user criterion.

Best answer: C

Explanation: Catalog item visibility and submitted-record access are separate controls. Available For user criteria determine who can discover and order the item; they do not grant read access to the resulting requested item. Reading an sc_req_item record is governed by applicable ACLs. An Allow-If rule based on the requested user’s manager relationship grants access only when the current user manages that requested user, satisfying the required scope without changing the ordering audience.

Fulfillment membership would grant broader access, while an approval assignment does not by itself satisfy the stated read ACL.

• Available For criteria affect item discovery and ordering, not access to an existing sc_req_item record.
• Fulfillment group membership would expose requested items beyond each manager’s direct reports.
• Approval assignment does not independently grant read access under the stated ACL configuration.

Question 3

Topic: Self Service and Automation

An administrator is revising a Workflow Studio flow triggered when a requested item is created. The current flow immediately creates a catalog task.

Requirements:

• Items below $5,000 require no approval.
• Items at or above $5,000 require approval from Requested for.Manager.
• A fulfillment task must not exist before any required approval is granted.
• Rejected items must not produce a fulfillment task.

Assume all manager references are populated. Which redesign best meets these requirements?

Options:

• A. Branch by cost; run Ask for Approval and Create Catalog Task in parallel on the high path; create low-cost tasks directly.

• B. Branch by cost; create the high-cost task in a waiting state and then use Ask for Approval; create low-cost tasks directly.

• C. Branch by cost; set Approval to Requested on the high path and wait for Approved before creating its task; create low-cost tasks directly.

• D. Branch by cost; use Ask for Approval on the high path and create its task only when Approved; create low-cost tasks directly.

Best answer: D

Explanation: Approval must operate as a gate before fulfillment begins. On the high-cost branch, the Ask for Approval action routes the approval and waits for an outcome. Create Catalog Task should run only from the Approved outcome, so rejection cannot create a task. The low-cost branch can create its task immediately because no approval applies.

Changing an approval field does not itself establish and route the required approval. Likewise, creating the task before approval or placing approval and task creation in parallel fails the required sequence.

• Changing approval status does not by itself create and route the manager approval required by the process.
• Creating a waiting task still creates the fulfillment record before approval is granted.
• Running parallel actions provides no dependency that prevents task creation before the approval outcome.

Question 4

Topic: Configuring Applications for Collaboration

An administrator must require u_serial_number when an incident’s Category is Hardware, including records submitted through standard forms and the Table API.

• An active UI Policy makes the field mandatory when Category is Hardware.
• The dictionary entry has Mandatory set to false.
• A form blocks a blank value, but an authorized Table API request creates a Hardware incident with the field blank.

Which configuration best enforces the requirement across both entry paths?

Options:

• A. Add a matching Data Policy for web-service submissions and retain the UI Policy.

• B. Set the dictionary field mandatory for all records and retain the UI Policy.

• C. Add a matching onSubmit Client Script to every view and retain the UI Policy.

• D. Make the UI Policy global across views and leave the dictionary unchanged.

Best answer: A

Explanation: A UI Policy changes form behavior, such as whether a field appears mandatory, read-only, or visible. It does not modify the field’s dictionary definition or enforce the behavior on Table API requests. A conditional Data Policy can enforce the same mandatory requirement for applicable noninteractive submissions, while the existing UI Policy preserves immediate browser feedback.

Making the dictionary field mandatory would affect every incident rather than only Hardware incidents. Expanding client-side rules to more forms or views still would not govern API submissions. The entry path determines whether a form rule participates in validation.

• Dictionary requirement applies to every incident and cannot preserve the category-specific requirement.
• Client script coverage remains browser-side, so Table API submissions are unaffected.
• Global UI Policy expands form coverage but still does not enforce server-side API writes.

Question 5

Topic: Database Management and Platform Security

Which statement best explains how inaccurate CMDB data can affect operational records and service visibility?

Options:

• A. Task records copy CI details when created, preventing later CMDB inaccuracies from affecting their context.

• B. CMDB inaccuracies affect operational work only when task records are transformed into configuration items.

• C. Incorrect CI references and relationships can distort task context, impact analysis, and service visibility.

• D. CSDM stores service relationships separately, preventing CMDB inaccuracies from affecting service visibility.

Best answer: C

Explanation: Incidents, changes, and requests can reference configuration items in the CMDB. If a referenced CI has inaccurate attributes, support and change teams may use incorrect ownership, status, or configuration context. Inaccurate CI relationships can also distort dependency views, impact analysis, and service visibility. CSDM provides guidance for modeling service data, but it does not create a separate database that insulates services from poor CMDB data. Accurate CI records and relationships are therefore important for both task processing and understanding service dependencies.

• Copied CI details is incorrect because a reference links to a CI record rather than creating an isolated, permanently accurate copy.
• Separate CSDM database is incorrect because CSDM is a modeling standard used with CMDB data.
• Task transformation is incorrect because incidents, changes, and requests may reference CIs without becoming CIs themselves.

Question 6

Topic: Configuring Applications for Collaboration

In ServiceNow, a tag is shared with a team. A team member can see the tag, but a read ACL prevents that member from opening one record carrying it. Which statement correctly describes the relationship between tag sharing and record access?

Options:

• A. Tag sharing controls tag visibility and also grants read access to tagged records.

• B. Tag sharing delegates the owner’s access, while ACLs evaluate the tag owner.

• C. Tag sharing controls tag visibility, while ACLs independently control record access.

• D. Tag sharing controls record access, while ACLs independently control tag visibility.

Best answer: C

Explanation: Tag sharing and record authorization are separate controls. The sharing audience determines who can see or use the tag as a collaboration aid. It does not add roles, satisfy ACL conditions, or grant read access to records carrying that tag. When a member attempts to open a tagged record, ServiceNow evaluates access in that member’s user context against the applicable ACLs. Here, the team membership permits tag visibility, but the stated read ACL still blocks the underlying record. Record permissions are not inherited from the tag owner, and the tag audience does not replace ACL evaluation.

• Treating tag sharing as a read grant confuses collaboration metadata with authorization to underlying records.
• Delegating the owner’s access is incorrect because ACLs evaluate the team member’s own user context.
• Reversing the controls is incorrect because the audience governs tag sharing, while ACLs govern record access.

Question 7

Topic: Database Management and Platform Security

A platform administrator imports 120 employee rows. Each row has a unique employee number. The transform map targets User [sys_user], coalesces on employee number, and maps email and department. Before the import, 20 employee numbers existed and 100 did not.

Which TWO checks confirm that all rows reached the intended target records?

Options:

• A. Compare the source attachment count with the expected 120 rows.

• B. Query sys_user for all employee numbers and verify the mapped values.

• C. Inspect the run’s sys_user results: 100 inserts, 20 updates, zero errors.

• D. Verify the active transform map targets the sys_user table.

• E. Inspect the import set for 120 staged rows and a Processed state.

Correct answers: B and C

Explanation: Import set staging and target-table persistence are separate stages. Transform run results provide execution evidence: 100 inserts plus 20 updates account for all 120 rows, while zero errors indicates no failed transformations. Querying sys_user by employee number and comparing mapped values verifies that the intended records actually contain the imported data.

Staging counts, source-file counts, and transform map configuration establish preparation or processing status, but they do not prove that the target records were successfully written.

• A Processed import set may still contain ignored or failed rows, so staging status does not prove target persistence.
• The attachment row count validates the source file, not the transformation results.
• An active map identifies the intended destination but does not prove that a particular run wrote records.

Question 8

Topic: Database Management and Platform Security

An administrator reviews an inherited field:

• Task.assignment_group has Mandatory cleared.
• An Incident dictionary override has Override mandatory and Mandatory selected.
• Problem extends Task but has no override for this field.
• No policies or scripts change the field behavior.

Which two conclusions are valid? Select TWO.

Options:

• A. Problem inherits Assignment group as optional.

• B. Incident treats Assignment group as mandatory.

• C. Incident stores Assignment group in a new column.

• D. Task adopts Incident’s mandatory field setting.

• E. Problem inherits Incident’s mandatory field setting.

Correct answers: A and B

Explanation: A dictionary override changes a supported property of an inherited field for a particular child table while leaving the parent dictionary definition unchanged. Incident therefore treats Assignment group as mandatory because its override explicitly replaces the inherited setting. Problem is a separate child of Task and has no such override, so it continues to inherit Task’s optional setting.

The override changes field behavior for the child table; it does not create a separate physical field or modify sibling tables.

• Task remains optional because a child-table override does not modify the parent dictionary definition.
• Problem does not inherit Incident’s override because sibling tables do not pass overrides to one another.
• Incident continues using the inherited Task field rather than receiving a new child-table column.

Question 9

Topic: Self Service and Automation

An administrator is designing a Virtual Agent topic for payroll support.

• The user reports an unauthorized change to bank details and requests immediate assistance.
• Virtual Agent has authenticated the portal session and collected an issue summary.
• Policy requires an HR agent to perform secondary identity verification before discussing or changing payroll data.
• The HR live-agent queue is staffed.

What should the administrator configure as the next conversational outcome?

Options:

• A. Continue the topic by collecting replacement bank details and submit them for HR approval.

• B. Present the payroll security article and ask whether the guidance resolves the issue.

• C. Transfer the conversation to the HR queue and pass the collected context.

• D. Create a high-priority HR case from the collected context and end the conversation.

Best answer: C

Explanation: Virtual Agent should hand off a conversation when the next required action depends on human-only verification, judgment, or authority. Portal authentication does not satisfy the stated secondary-verification requirement. Because an HR agent is available and the user needs immediate assistance, transferring the conversation allows the agent to verify identity before discussing or changing sensitive payroll data. Passing the collected context also avoids requiring the user to repeat the issue. The deciding factor is authorization to continue, not Virtual Agent’s ability to collect additional information.

• Creating a case supports asynchronous follow-up but does not provide the requested immediate assistance while agents are available.
• Collecting replacement bank details proceeds beyond the point where policy requires secondary verification by an HR agent.
• Presenting an article may help with general guidance but cannot complete the required identity verification or address the suspected unauthorized change.

Question 10

Topic: Database Management and Platform Security

An imported incident must reference employee E1042 as the caller. The form displays Alex Chen, but inspection shows:

Employee record
sys_id: 11111111111111111111111111111111
name: Alex Chen
employee_number: E1042

Contractor record
sys_id: 22222222222222222222222222222222
name: Alex Chen
contractor_id: C778

Incident caller_id: 22222222222222222222222222222222

Which action corrects the Caller reference?

Options:

• A. Set Caller to the record for employee E1042.

• B. Clear Caller and reselect the name Alex Chen.

• C. Keep Caller on the record for contractor C778.

• D. Change the user display field to Employee number.

Best answer: A

Explanation: A reference field stores the target record’s sys_id, while the form normally shows that record’s display value. Both user records display Alex Chen, so the visible name does not establish which record is referenced. The incident’s stored caller_id is 22222222222222222222222222222222, which identifies contractor C778. Employee E1042 has the other sys_id, so Caller must be changed to that specific user record. Changing display configuration might improve future identification, but it does not replace the stored reference on this incident.

• Keeping the contractor retains the stored reference that conflicts with the employee requirement.
• Reselecting by name remains ambiguous because both target records have the same display value.
• Changing the display field affects presentation but does not correct the incident’s stored caller_id.

Question 11

Topic: Configuring Applications for Collaboration

A service desk lead frequently reviews active Priority 2 incidents assigned to the Network group. The matching records change throughout the day, and the lead has already built a list filter that returns the correct results.

The lead wants a personal, one-click shortcut under Unified Navigation Favorites. What should the administrator recommend?

Options:

• A. Tag the matching incidents, then open the tag from the list.

• B. Apply the filter, then add the filtered incident list to Favorites.

• C. Save the filter for Me, then open it from the incident list.

• D. Personalize the incident list, then reopen it from Unified Navigation.

Best answer: B

Explanation: A favorite can provide direct access to a filtered list while preserving the list query. Each time the lead opens the favorite, ServiceNow evaluates that query against current incident records, so newly matching records appear and records that no longer match disappear. This fits the requirement for a personal, one-click navigation shortcut.

A saved filter also preserves reusable filter criteria, but users typically select it from the list’s filtering interface. It does not by itself satisfy the stated requirement for direct access from Favorites. The key distinction is whether the user needs reusable criteria within a list or a direct navigation shortcut to the filtered list.

• Saving the filter for Me preserves the criteria but does not create the requested one-click Favorites shortcut.
• Tagging current incidents creates a labeled collection but does not automatically include future records that match the criteria.
• Personalizing the list changes its presentation, such as columns, rather than preserving the required record query.

Question 12

Topic: Self Service and Automation

A Virtual Agent topic is designed so that when guidance fails, it creates an incident, assigns it to Workplace Applications, and transfers the conversation to a live agent with incident context.

During an audit, the user’s transcript shows that the user remained blocked. Which TWO observations provide direct evidence that this interaction was routed and escalated as designed? Select TWO.

Options:

• A. The linked incident shows Workplace Applications as its assignment group.

• B. The user received the standard notification that an incident was created.

• C. The transcript records a transfer accepted by a live agent with incident context.

• D. The topic’s earlier designer test completed successfully before activation.

• E. The active topic includes incident creation and live-agent transfer actions.

Correct answers: A and C

Explanation: Runtime evidence should confirm what happened during the specific conversation, not merely what the topic was designed or tested to do. An accepted live-agent transfer demonstrates actual escalation, while the linked incident’s assignment group demonstrates routing to the required team. Together, these records validate separate parts of the expected outcome.

Configuration state, earlier testing, and notification delivery can support troubleshooting, but they do not prove that this interaction completed the required transfer and assignment. The key distinction is planned behavior versus observed execution for the audited conversation.

• An active topic containing the required actions proves configuration, not that this conversation executed those actions.
• A successful earlier test applies to a different execution and does not establish the audited interaction’s outcome.
• An incident notification indicates record creation but does not prove correct assignment or an accepted live-agent transfer.

Question 13

Topic: Configuring Applications for Collaboration

An administrator shares the Quarter-end tag with the Finance Operations team. Maya is an active member of that team. The tag is applied to an incident and an HR case.

Applicable read ACL evaluation shows:

• Maya is allowed to read the incident.
• Maya is denied access to the HR case because she lacks its required role.
• Maya has no elevated privileges or admin override.

Which TWO conclusions are valid?

Options:

• A. Maya can read the HR case by opening it outside the tagged list.

• B. Maya can use the tag only after reading every tagged record.

• C. Maya can read the incident but remains denied the HR case.

• D. Maya is within the audience that can see the shared tag.

• E. Maya loses incident access if the tag is later unshared.

Correct answers: C and D

Explanation: Tag sharing and record authorization are separate controls. Sharing Quarter-end with Finance Operations places Maya within the tag’s audience, so she can see the shared tag. It does not grant read access to records associated with that tag. When Maya accesses a tagged record, ServiceNow still evaluates the applicable ACLs for that record and operation. Her ACL evaluation permits the incident but denies the HR case because she lacks the required role.

Changing the tag’s audience affects tag visibility, not the independent permissions governing the underlying records.

• Requiring access to every tagged record incorrectly treats record authorization as a prerequisite for tag visibility.
• Using another navigation path cannot bypass the HR case’s read ACL evaluation.
• Unsharing the tag changes its audience but does not revoke separately granted incident access.

Question 14

Topic: Data Migration and Integration

An administrator is promoting a source-tested update set containing a dictionary change, UI policy, and Business Rule. In the production instance, preview identifies a collision with a local UI policy change. The team has determined which version should take precedence and expects preview to be clean after resolving the collision.

Which TWO practices should remain in the controlled promotion plan?

Options:

• A. Resolve the identified preview collision before committing the update set.

• B. Test the changed behavior while the update set remains previewed.

• C. Perform targeted functional validation after committing in the production instance.

• D. Commit the update set before resolving the target collision.

• E. Use the clean preview result as the functional acceptance test.

Correct answers: A and C

Explanation: Update set preview analyzes incoming configuration and identifies potential collisions or other reported problems. It does not activate the previewed configuration or execute its runtime behavior. Because production has a conflicting local change, the team should resolve that conflict before committing so the intended configuration is applied.

A clean preview means no remaining preview problems were detected. It does not guarantee that a schema change is nondestructive or that the UI policy and Business Rule will behave correctly in the target environment. Targeted functional validation must therefore follow the commit, even when source testing passed and the final preview was clean.

• Testing while previewed fails because preview does not apply the incoming configuration for runtime testing.
• Treating a clean preview as acceptance confuses collision analysis with functional verification.
• Committing before collision resolution reverses the controlled sequence and applies changes before the conflict is addressed.

Question 15

Topic: Database Management and Platform Security

A catalog request for a dedicated virtual server is complete. The resulting VM remains operational after the requested item closes and has a unique name, support group, IP address, and relationship to its virtualization host. Administrators need the VM included in change impact analysis while preserving the request for audit history.

Which action should the administrator take?

Options:

• A. Create a server model for the VM and associate its host relationship with that model.

• B. Use the requested item for the VM and associate future operational tasks with that record.

• C. Create an asset record for the VM and retain the requested item as fulfillment history.

• D. Create a server CI for the VM and retain the requested item as fulfillment history.

Best answer: D

Explanation: A CMDB configuration item represents a distinct operational component that must be managed over time. The provisioned VM remains active after fulfillment, has its own operational attributes, and participates in a relationship needed for change impact analysis. Those facts support creating a server CI.

The requested item records the fulfillment transaction rather than replacing the resulting CI. An asset record can track financial or ownership concerns, and a model record can define shared specifications, but neither alone represents the deployed VM and its operational relationships.

• Asset-only tracking does not provide the deployed CI relationships required for operational impact analysis.
• Requested-item tracking treats a temporary fulfillment transaction as the persistent operational component.
• Model tracking describes shared server characteristics rather than one uniquely deployed VM and its host relationship.

Question 16

Topic: Instance Configuration

A company uses Core UI reports and dashboards. An administrator must add Performance Analytics indicators with scheduled data collection for historical trends.

The administrator has the admin role, but the Performance Analytics plugin is inactive in All Available Applications. The company has the required entitlement and prohibits a custom snapshot solution.

Which action is required first?

Options:

• A. Expose Performance Analytics modules in navigation, then configure the indicators.

• B. Activate the entitled Performance Analytics application/plugin, then configure the indicators.

• C. Assign the Performance Analytics administrator role, then configure the indicators.

• D. Migrate the existing reports to Platform Analytics, then configure the indicators.

Best answer: B

Explanation: An inactive application or plugin must be installed or activated before its platform capabilities become available. Performance Analytics supplies capabilities such as indicators and scheduled data collection; ordinary reports and dashboards do not establish that these components are installed. Entitlement permits activation but does not activate the capability automatically.

Navigation settings control how users find installed modules, while roles control access to installed components. Neither mechanism installs missing application artifacts. Similarly, moving existing reports to Platform Analytics does not enable Performance Analytics features. After approved activation, the administrator can configure the required indicators and collection jobs.

• Navigation visibility can expose installed modules but cannot provide components from an inactive plugin.
• Role assignment grants permissions to available capabilities but does not install the Performance Analytics application.
• Report migration changes analytics presentation and does not provide Performance Analytics indicators or data collection.

Question 17

Topic: Database Management and Platform Security

Which statement best explains how a consistent service representation allows incident and change processes to use the same service context?

Options:

• A. Shared service context confirms that the CMDB contains every supporting CI and relationship.

• B. Both processes reference the same service record through consistent identifiers and modeled relationships.

• C. Each process maintains a separate service record while CSDM synchronizes their service attributes.

• D. Both processes match service context by display name, independent of CMDB references and relationships.

Best answer: B

Explanation: CSDM provides consistent guidance for representing services, while the CMDB stores the corresponding records and relationships. Incident and change processes can reference the same defined service record, allowing each process to interpret affected services and related configuration items in a common context. This reuse depends on consistent record identities and modeled relationships, not on separate process-specific copies or display-name matching.

A shared service representation improves operational consistency but does not prove that every supporting CI or relationship has been discovered and recorded.

• Separate process-specific records fragment service context; CSDM does not synchronize duplicate service representations between operational processes.
• Display names are not reliable record identities and do not replace CMDB references or modeled relationships.
• Reusing service context does not establish that the CMDB is complete or that every dependency is recorded.

Question 18

Topic: Instance Configuration

A plugin is Active, and an administrator can open its application module and read its records. The intended operator cannot see the module and lacks the capability-specific role identified in the plugin documentation.

Which statement correctly distinguishes the relevant mechanisms?

Options:

• A. Role assignment installs the capability; activation only displays its application modules.

• B. Activation authorizes all users; navigation personalization gives the operator access to it.

• C. Activation enables the capability; role assignment authorizes the operator to use it.

• D. Activation authorizes administrators; a second activation authorizes other users to use it.

Best answer: C

Explanation: Plugin activation and user authorization are separate mechanisms. Activation installs or enables a capability for the instance; it does not automatically grant every user permission to use that capability. Roles can control whether a user sees an application module and whether applicable ACLs permit access to its records. Here, the plugin’s Active status and the administrator’s successful use show that another activation is unnecessary. The operator lacks the documented capability-specific role, so that role must be assigned directly or through an appropriate group.

Navigation personalization cannot substitute for authorization, and plugins are not activated separately for individual users.

• Navigation personalization can organize modules already available to a user, but it does not grant a missing role or record access.
• Reversed responsibilities incorrectly treats role assignment as installation and activation as merely a navigation setting.
• Per-user activation is incorrect because plugin activation applies to the instance, while roles govern user access.

Question 19

Topic: Configuring Applications for Collaboration

A service desk shares a filtered list of incidents assigned to the Network group. Team members already have permission to update these records. They need a shared card view where:

• Lanes represent incident State values.
• Dragging a card to another lane updates the incident state.
• Records automatically enter or leave the view as the filter results change.

Which configuration best meets these requirements?

Options:

• A. Create a shared incident list grouped by state with inline editing enabled.

• B. Create a shared dashboard visualization grouped by state with record drilldown enabled.

• C. Create a flexible Visual Task Board and manually label its lanes with state values.

• D. Create a guided Visual Task Board using the filter and State lane field.

Best answer: D

Explanation: A guided Visual Task Board is data-driven: its cards come from records matching a table filter, and its lanes correspond to values of a selected field. Here, the board uses filtered Incident records and the State field. Moving a card between lanes updates that record’s state, subject to the user’s existing permissions. Because board membership follows the filter, qualifying incidents appear and nonqualifying incidents disappear as record values change.

A flexible board can organize record cards collaboratively, but manually named lanes are not governed by the incident state field. Lists and dashboards display current data but do not provide the required card-and-lane workflow.

• Flexible board uses manually managed lanes, so moving a card does not provide the required field-driven state transition.
• Dashboard visualization supports monitoring and drilldown, not drag-based updates to incident state.
• Grouped list supports record viewing and editing but does not provide the requested collaborative card-and-lane experience.

Question 20

Topic: Data Migration and Integration

An administrator configures Incident as follows:

• UI policy: Active on the default desktop form; On load is true; Reverse if false is true; when State is Resolved, Resolution notes becomes mandatory. The field is on the form.
• Business Rule: Active before update; when State is Resolved and Resolution notes is empty, it aborts the database operation.
• Import: Every row matches an existing incident, sets State to Resolved, leaves Resolution notes empty, and runs Business Rules.

Which TWO conclusions are valid?

Options:

• A. The before Business Rule immediately marks the field mandatory on an unsaved form.

• B. Reverse if false clears Resolution notes when State changes from Resolved.

• C. The UI policy makes Resolution notes mandatory on each qualifying loaded form.

• D. The UI policy independently rejects each qualifying row during the server-side transform.

• E. The before Business Rule aborts each qualifying incident update from the import.

Correct answers: C and E

Explanation: A UI policy controls client-side form behavior. On a qualifying Incident form, it marks Resolution notes mandatory when State is Resolved. Reverse if false reverses that form property when the condition becomes false; it does not alter the field’s data.

An import transform operates server-side, so the UI policy does not enforce requirements during the transform. The before Business Rule does apply because the import is configured to run Business Rules. Each proposed update has a Resolved state and empty Resolution notes, so the rule aborts the database operation. Server-side logic, not the UI policy, prevents these imported updates.

• UI policy rejects imports: UI policies control qualifying forms and do not independently enforce requirements during server-side transforms.
• Reverse clears data: Reversing the policy action removes the mandatory state rather than clearing the field value.
• Business Rule changes form: A before-update rule runs during a database update attempt, not immediately after an unsaved client-side field change.

Question 21

Topic: Platform Overview and Navigation

In Next Experience Unified Navigation, which pairing correctly identifies the feature for keeping a user-selected shortcut to a frequently used module and the feature for returning to recently opened records?

Options:

• A. Favorites for the shortcut; History for recent records

• B. Workspace for the shortcut; All menu for recent records

• C. History for the shortcut; Favorites for recent records

• D. All menu for the shortcut; History for recent records

Best answer: A

Explanation: Favorites are persistent, user-selected shortcuts to modules, records, lists, or other platform locations. History is populated from recently accessed content and changes as the user navigates. The All menu supports browsing and filtering available applications and modules, while a workspace provides a task-focused interface for particular types of work.

The key distinction is user-selected persistence in Favorites versus automatically tracked recent activity in History.

• Reversing Favorites and History confuses manually saved shortcuts with automatically tracked activity.
• The All menu helps locate applications and modules, but it does not create a saved user shortcut.
• A workspace is a task-focused interface, while the All menu is not a recent-record list.

Question 22

Topic: Self Service and Automation

A knowledge base has article versioning enabled and requires review before publication.

• Network Setup: Published; needs a minor correction. The current version must remain visible until the revision is approved.
• Legacy VPN: Published; obsolete and must be unavailable immediately while retaining its history. A knowledge manager may retire it directly.

Which TWO actions should the administrator take?

Options:

• A. Retire Legacy VPN now through the authorized lifecycle action, preserving its history.

• B. Schedule Legacy VPN for retirement at its next review date instead of retiring it.

• C. Submit Network Setup for review, then edit the published version after approval.

• D. Check out Network Setup, edit the draft version, then submit it for review.

• E. Create a separate Network Setup article, then retire the original after approval.

Correct answers: A and D

Explanation: Article versioning supports controlled updates to published knowledge. Checking out Network Setup creates a draft version for correction while the approved version remains visible. After editing, the revision enters the required review process before publication.

Retirement fits Legacy VPN because the article is obsolete, must become unavailable immediately, and should retain its history. Retirement changes its lifecycle state rather than deleting its record. The knowledge manager’s stated authority means no additional retirement approval is required.

Creating a separate article is more appropriate for distinct content, not a minor revision of the same article.

• Creating a separate article unnecessarily fragments the version history for a minor correction to existing content.
• Submitting for review before editing reverses the update sequence and does not produce the required corrected draft.
• Scheduling future retirement leaves the obsolete VPN article available longer than the immediate-withdrawal requirement permits.

Question 23

Topic: Configuring Applications for Collaboration

An administrator investigates an Incident notification after INC0010427 was reassigned at 10:03. At that time, the notification was active and subscribed to the incident.assigned event. Its expected recipient was the new assignee, and its subject was Assignment notice INC0010427.

Which TWO observations provide runtime evidence that the notification was evaluated or its message was sent? Select TWO.

Options:

• A. A Business Rule execution entry linked to the incident update

• B. A sys_email row with matching details and type sent

• C. A recipient record with email populated and notifications enabled

• D. A processed incident.assigned event linked to the changed incident

• E. An active notification whose condition matches the incident’s current values

Correct answers: B and D

Explanation: Event-based notification troubleshooting separates event generation, notification evaluation, recipient resolution, and email sending. A processed event with the correct name and incident shows that the event processor handled the trigger; because the notification was active and subscribed at that time, it was evaluated. A matching sys_email record with type sent confirms that ServiceNow dispatched the outbound message, although it does not prove delivery to the recipient’s inbox.

Configuration settings and eligible recipient data show how processing should work, but they are not evidence that a particular runtime execution occurred.

• A Business Rule execution entry proves the rule ran, but not that the resulting event was processed.
• A currently matching condition describes configuration eligibility, not historical notification evaluation.
• A valid recipient record supports recipient resolution, but does not prove evaluation or sending.

Question 24

Topic: Instance Configuration

Which mechanism allows an administrator to observe the effective end-user context of an authorized test account without changing that account’s role assignments?

Options:

• A. Use user impersonation, test the account context, then end impersonation.

• B. Elevate administrator privileges, test the account context, then end elevation.

• C. Add the account to a role-bearing group, test, then remove membership.

• D. Assign a role directly, test the account context, then remove the role.

Best answer: A

Explanation: User impersonation lets an authorized administrator interact with the platform in another user’s effective context. It is useful for checking navigation visibility, record access, and other user-specific behavior without altering the impersonated account’s role assignments. Ending impersonation returns the administrator to the original session context.

Direct role assignment and membership in a role-bearing group both change the test account’s privileges, even if those changes are later reversed. Role elevation changes the administrator’s own privileges rather than reproducing the test account’s experience. The key distinction is temporary observation of an existing user context versus modification of access assignments.

• Direct role assignment changes the account’s privileges during testing and therefore does not preserve its existing access context.
• Group membership can grant inherited roles, so adding the account changes the experience being investigated.
• Role elevation expands the administrator’s own access rather than adopting the test account’s effective context.

Question 25

Topic: Database Management and Platform Security

An administrator loads worker data into an import set. Staged fields u_worker_name and u_contact contain values, while target fields name and email remain empty. An existing coalesce mapping correctly matches target records by employee number. The source headings and target schema cannot change. What should the administrator configure to populate the target fields?

Options:

• A. Add data policies requiring name and email on the target table.

• B. Reconfigure the data source to load name and email into the target table.

• C. Run automatic field mapping after changing only the staging field labels.

• D. Add explicit name and email field maps to the existing transform map.

Best answer: D

Explanation: An import set stages source data, while a transform map connects that staged data to a target table. Individual field maps specify which source field supplies each target field. Because the internal source and target field names differ, explicit mappings are needed for u_worker_name to name and u_contact to email. The existing coalesce mapping determines which target record matches the imported row; it does not automatically map the other fields.

Changing labels affects presentation, data sources load staging records, and data policies enforce field behavior rather than transfer values. The transform map is the configuration that controls source-to-target field assignment.

• Automatic mapping compares compatible internal field names; changing only displayed labels does not resolve the stated name differences.
• Data source routing loads source rows into an import set rather than defining target-field assignments.
• Data policies enforce mandatory or read-only behavior but do not copy staged values into target fields.

Questions 26-50

Question 26

Topic: Platform Overview and Navigation

An organization has two ServiceNow instances:

• Production: Supports live incident work and current SLA reporting.
• Development: Was cloned from production seven days ago and has masked data, representative test users, and disabled outbound integrations.

An administrator must create a UI policy and validate its behavior for several user roles before release. Meanwhile, agents continue updating live incidents.

Which TWO actions align with the intended use of these instances?

Options:

• A. Configure and test the policy in production because it is client-side.

• B. Configure and role-test the UI policy in development.

• C. Activate the policy in development to update production automatically.

• D. Use production records to manage the current incident queue.

• E. Use the development records to report the current incident queue.

Correct answers: B and D

Explanation: Production instances support live business operations and contain the authoritative, current records. Non-production instances provide controlled environments for configuration and testing, especially when changes must be validated with representative users before release. Therefore, the UI policy should be developed and tested in the development instance while agents continue managing active incidents in production.

A clone represents production data as of the cloning time; it does not remain synchronized with later production activity. Configuration tested or activated in development also does not transfer automatically to production. It must be promoted through the organization’s normal change process and validated after deployment.

• Report from the clone fails because its records are seven days old and do not reflect the current production queue.
• Expect automatic transfer fails because activating configuration in development does not synchronize it to production.
• Test directly in production fails because client-side behavior can still disrupt live users and should be validated in non-production first.

Question 27

Topic: Database Management and Platform Security

A company uses a standard hosted ServiceNow SaaS instance. A Security Center review identifies several control activities. The contract does not transfer customer administration or data-governance duties to ServiceNow.

Under the shared responsibility model, which TWO activities are assigned to the appropriate owner?

Options:

• A. Assign customer ACL and role governance to the customer.

• B. Assign protection of physical hosting facilities to ServiceNow.

• C. Assign classification of uploaded business records to ServiceNow.

• D. Assign approval of employee access requests to ServiceNow.

• E. Assign patching of underlying SaaS host systems to the customer.

Correct answers: A and B

Explanation: Shared responsibility divides security activities according to who controls each layer. ServiceNow protects and maintains the infrastructure used to provide its hosted SaaS platform, including physical hosting safeguards. The customer remains responsible for its instance configuration, identities, roles, ACLs, business data, and internal access approvals.

Security Center can identify posture concerns and recommend improvements, but a recommendation does not transfer ownership or prove that the customer implemented a control. The key distinction is whether the activity concerns ServiceNow’s service infrastructure or the customer’s use and configuration of the instance.

• Business-record classification remains a customer data-governance responsibility because the customer owns and understands the uploaded information.
• Underlying SaaS host patching belongs to ServiceNow because customers do not administer the hosted infrastructure.
• Employee access approval remains with the customer because it controls workforce authorization and role eligibility.

Question 28

Topic: Configuring Applications for Collaboration

Which ServiceNow form action saves changes to an existing record while keeping that record’s form open for continued editing?

Options:

• A. Update

• B. Save

• C. Insert and Stay

• D. Submit

Best answer: B

Explanation: ServiceNow form actions differ in both record operation and navigation behavior. Save writes changes to the current record and keeps its form open, allowing continued editing. Update also writes changes to an existing record but returns the user to the previous page. Actions involving Submit or Insert are associated with creating records rather than continuing to edit the same existing record.

The deciding distinction is whether the user remains on the current record after saving.

• Update saves the existing record but returns to the previous page.
• Submit creates a new record and then leaves its form.
• Insert and Stay creates another record rather than updating the existing one.

Question 29

Topic: Database Management and Platform Security

A CMDB administrator investigates why an impact report lists only one of the two servers supporting the Payroll Production Service Instance.

Report logic: Start with the Service Instance and follow Depends on::Used by relationships where it is the parent.

Current relationships:

Both servers are active. The second server has a blank serial number, the first server has an unverified operating system value, and the business application has no direct server relationships.

Which issue directly causes the undercount?

Options:

• A. The reversed parent-child direction of the pay-srv-02 relationship

• B. The missing direct relationship from the business application to pay-srv-02

• C. The unverified operating system value on the pay-srv-01 server CI

• D. The blank serial number on the pay-srv-02 server CI

Best answer: A

Explanation: CMDB relationships are directional. For Depends on::Used by, the parent depends on the child. The report starts with Payroll Production and follows child CIs only when that Service Instance is the parent. It therefore reaches pay-srv-01 but not pay-srv-02, whose relationship is stored in the opposite direction.

Correcting the relationship direction makes the second server available to the defined traversal. Other incomplete CI attributes can reduce CMDB quality for different purposes, but they do not affect this report’s relationship-based count.

• A blank serial number may hinder identification or reconciliation, but the report does not use serial numbers.
• An unverified operating system value affects attribute reliability, not relationship traversal.
• A direct business-application relationship is outside the report path, which begins with the Service Instance.

Question 30

Topic: Self Service and Automation

Which Service Catalog mechanism supports a repeatable onboarding request that uses stated rules to select several related catalog items while retaining separate requested-item fulfillment records? Select one.

Options:

• A. A record producer with mapped target fields

• B. A standard catalog item with shared variables

• C. An order guide with rule-based item inclusion

• D. A catalog category with curated item membership

Best answer: C

Explanation: An order guide coordinates the request experience for several related catalog items. It can collect initial information and apply rules that determine which items to include. When submitted, the guide acts as the intake mechanism, while the included catalog items generate separate requested item records for their respective fulfillment processes.

A standard catalog item normally represents one requested item. A record producer instead creates a target record, such as an incident, and a catalog category organizes items for browsing rather than submitting them together.

• A standard catalog item can reuse variables, but it does not rule-select several separate catalog items for one coordinated request.
• A record producer creates a task-based target record rather than separate requested items.
• A catalog category organizes discoverability but does not coordinate submission or fulfillment records.

Question 31

Topic: Self Service and Automation

A platform administrator is designing an authenticated Virtual Agent topic. Users satisfy the user criteria for a published knowledge article and a catalog item.

The topic must present the article, ask whether it resolved the issue, and:

• End without creating records after a Yes response.
• Offer a request form after a No response.
• Create records only when the user submits the form.
• Produce a request with a requested item for fulfillment.

Which two design elements satisfy these requirements? Select TWO.

Options:

• A. Branch on the response, ending for Yes and offering the standard catalog item for No.

• B. Use a negative article rating to create the requested item before the user submits a request.

• C. Use the conversation to create a catalog task directly and treat it as the requested item.

• D. Use the standard catalog item submission to create a request and requested item for fulfillment.

• E. Branch on the response, ending for Yes and offering an incident record producer for No.

Correct answers: A and D

Explanation: Virtual Agent can combine knowledge and catalog capabilities in one self-service journey. After presenting an accessible article, the topic needs an explicit resolution check. A Yes response ends the journey without creating records, while a No response offers the appropriate standard catalog item. The user must still submit that item before catalog records are created.

A standard catalog item follows the requested-item process, creating a request (REQ) and requested item (RITM). Fulfillment automation may then create catalog tasks (SCTASK) associated with the requested item. A record producer instead creates a record on its configured target table, such as an incident, so it does not provide the required catalog request structure.

• An incident record producer creates its configured target record rather than the required request and requested item.
• A negative article rating is feedback, not the required form submission that authorizes record creation.
• A catalog task supports fulfillment beneath a requested item; it does not replace the requested item.

Question 32

Topic: Self Service and Automation

A knowledge administrator reviews published articles. Access criteria are correct, and search is operating normally.

Which TWO article improvement actions are supported by the evidence?

Options:

• A. Add “lost phone” wording to the MFA article title and metadata.

• B. Update the VPN article to match the deployed client’s steps and screens.

• C. Rewrite the password-reset article to reduce its unusually high view count.

• D. Shorten the benefits article to reduce traffic during enrollment season.

• E. Retire the travel-exception article because its usage volume is limited.

Correct answers: A and B

Explanation: Knowledge article improvements should follow evidence of inaccurate content, poor user feedback, or findability problems rather than raw usage volume alone. The VPN ratings and comments identify specific outdated instructions following a client change. The MFA search data show that users employ different terminology from the existing article, supporting changes to its title or metadata while preserving the correct procedure.

High or low traffic can reflect audience size, timing, or demand. Strong helpfulness scores and expected usage patterns do not independently demonstrate a content problem.

• High password-reset traffic is expected for a broad audience, while strong helpfulness and no recurring complaints do not support a rewrite.
• Low travel-exception traffic matches its small intended audience, and its helpfulness rating does not support retirement.
• The benefits traffic spike aligns with enrollment season and does not demonstrate excessive article length.

Question 33

Topic: Database Management and Platform Security

Security Center identifies an active, customer-created read ACL on the custom u_payroll table. It grants access to the itil role, but company policy permits only the payroll_user role. The authorization service is functioning as designed, and payroll data cannot be imported until access is corrected.

Under the shared responsibility model, which response correctly assigns ownership?

Options:

• A. ServiceNow should apply the Security Center recommendation, while the customer confirms the resulting payroll-user access.

• B. ServiceNow should revise the ACL and role assignments, then have the customer validate access with authorized test users.

• C. The customer should revise role assignments, while ServiceNow revises the ACL and validates authorization-engine behavior.

• D. The customer should revise the ACL and role assignments, then validate access with authorized test users.

Best answer: D

Explanation: The shared responsibility model separates ServiceNow’s operation and protection of the underlying cloud platform from the customer’s responsibility for instance configuration, identities, access rules, and data governance. Here, the authorization service works correctly; the excessive access results from a customer-created ACL and customer-managed role assignments. Therefore, the customer must change the ACL, review role membership, and test access before importing sensitive records. A Security Center finding identifies a posture issue, but it does not transfer responsibility for implementing customer-controlled configuration changes to ServiceNow.

• Provider operation of the authorization service does not make ServiceNow responsible for customer-created ACLs or role assignments.
• Splitting ownership between roles and ACLs is incorrect because both are customer-controlled instance configurations.
• A Security Center recommendation is not evidence that ServiceNow will implement the recommended customer configuration change.

Question 34

Topic: Data Migration and Integration

An administrator retrieves a completed update set from development into a test instance. The retrieved update set is in the Loaded state. Before any configuration is applied, the administrator must identify collisions with existing test-instance configuration and resolve resulting preview problems.

Which action should the administrator take next?

Options:

• A. Back out the retrieved update set

• B. Run Update Set Scan on the retrieved set

• C. Preview the retrieved update set

• D. Commit the retrieved update set

Best answer: C

Explanation: Previewing a retrieved update set evaluates its configuration changes against the target instance before commit. It can expose collisions and other preview problems that an administrator should review and resolve before applying the update set. Commit is a separate action that writes the configuration changes to the target instance. Update Set Scan examines configuration for potential quality or best-practice issues, but it does not replace the target-instance collision preview. Back out is relevant after a committed update set must be reversed.

The Loaded state and requirement to avoid applying changes make preview the appropriate next step.

• Commit immediately applies the changes before the required collision review and problem resolution occur.
• Back out changes reverses a prior commit, but the loaded update set has not yet been committed.
• Run Update Set Scan checks configuration quality concerns rather than previewing collisions against the target instance.

Question 35

Topic: Configuring Applications for Collaboration

An active Incident notification has this configuration:

• When to send: Updated; State changes to Resolved
• Who will receive: Caller
• What it will contain: Subject and Message HTML

An administrator appends ${resolution_notes} to Message HTML and adds Assigned to under Users/groups in fields. No other settings change. For matching incidents, both user fields reference active users with valid email addresses.

Which TWO conclusions are correct?

Options:

• A. Resolution notes can appear in messages generated by the existing trigger.

• B. Assigned to must be populated before the state-change condition can match.

• C. Changing Resolution notes now independently satisfies the notification’s send condition.

• D. Adding Assigned to replaces Caller in the notification’s resolved recipient list.

• E. Assigned to is resolved as an additional recipient alongside Caller.

Correct answers: A and E

Explanation: A notification separates when it runs, who receives it, and what its message contains. The state-change condition still controls triggering because the administrator did not change When to send. Adding ${resolution_notes} affects only the rendered message after that trigger occurs. Adding Assigned to under Users/groups in fields expands recipient resolution; it does not add a send condition or remove Caller.

Content fields do not monitor record changes, and recipient configuration does not determine whether a notification condition matches. The key distinction is configuration purpose: trigger, recipient, and content settings perform separate functions.

• A message variable displays data but does not create a trigger for changes to that field.
• Recipient population is not an implicit prerequisite for the state-change condition.
• Adding another recipient field does not remove an existing recipient field.

Question 36

Topic: Data Migration and Integration

An administrator completed a configuration update set in a development instance and retrieved it into a test instance. Before applying any changes, the administrator must identify collisions and missing dependencies. After resolving all preview issues, the administrator must apply the tracked configuration to test.

Which TWO update-set actions should the administrator perform?

Options:

• A. Back out the retrieved update set.

• B. Preview the retrieved update set.

• C. Mark the retrieved update set Complete.

• D. Merge the retrieved update set locally.

• E. Commit the retrieved update set.

Correct answers: B and E

Explanation: Update-set migration separates pre-application review from application. After an update set is retrieved into the target instance, preview checks the incoming configuration against that instance and reports issues such as collisions or missing dependencies. The administrator resolves relevant preview problems before proceeding. Commit then applies the tracked configuration changes to the target instance.

Backout is used to reverse an update set that has already been committed. Completing an update set ends configuration capture in the source instance, while merging consolidates local update sets before migration; neither substitutes for previewing and committing a retrieved set.

• Back out applies after a commit when previously applied configuration must be reversed, not during pre-commit review.
• Mark Complete ends capture for a source update set and does not apply a retrieved set to the target.
• Merge locally combines compatible local update sets before retrieval and does not resolve the stated target-instance tasks.

Question 37

Topic: Data Migration and Integration

An import transform updates a hardware asset and queues two active asynchronous Business Rules whose conditions are true.

Initial state: The related import batch is Pending, and no verification record exists.

Rule A | Order 100 | Insert verification record
Rule B | Order 200 | If verification exists, set batch to Ready;
                   | otherwise, set batch to Review

The queue shows Rule A submitted before Rule B. Both operations will succeed, and no other automation changes these records.

What can the administrator conclude about the batch status after both rules complete?

Options:

• A. It must be Ready because both queued rules eventually complete.

• B. It can be Ready or Review, depending on execution timing.

• C. It must be Review because the higher-order rule executes first.

• D. It must be Ready because order 100 precedes order 200.

Best answer: B

Explanation: Business Rule order and queue submission order do not guarantee the execution sequence of asynchronous rules. If Rule A inserts the verification record before Rule B queries for it, Rule B sets the batch to Ready. If Rule B queries first, it finds no record and sets the batch to Review; Rule A’s later insert does not cause Rule B to reevaluate.

A dependency requiring ordered execution should be implemented in one coordinated process or triggered explicitly after the prerequisite completes. Merely queuing both asynchronous rules cannot ensure the required sequence.

• Numeric order can influence rule evaluation and queueing, but it does not serialize asynchronous worker execution.
• Eventual completion does not ensure that the verification record existed when Rule B performed its query.
• Higher order first is incorrect because a larger order value neither runs first nor controls asynchronous completion order.

Question 38

Topic: Configuring Applications for Collaboration

The active resolution_summary field appears on the Incident Default view but is omitted from the Service Desk view for all users. Administrators must add it to the Service Desk view while preserving its shared label, type, length, and mandatory setting.

Which action should an administrator take?

Options:

• A. Create a dictionary override that enables the field for Service Desk.

• B. Create a Service Desk UI Policy action that makes the field visible.

• C. Add the existing field to the Service Desk view in Form Designer.

• D. Add the existing field to the Default view in Form Designer.

Best answer: C

Explanation: A form layout controls which existing fields appear in a particular view, while the dictionary entry defines the field and its shared properties for the table. Because resolution_summary is active and already appears in the Default view, no schema change is needed. Selecting the Service Desk view in Form Designer and adding the existing field changes that view’s layout without altering its label, type, length, or mandatory setting.

A UI Policy can control a field loaded on a form, but it does not add a field omitted from the layout. Dictionary overrides apply to inherited fields on extended tables, not to individual form views.

• Editing the Default view does not change the separate Service Desk layout.
• A UI Policy visibility action cannot place an omitted field onto a form layout.
• A dictionary override changes inherited field behavior for an extended table, not view membership.

Question 39

Topic: Data Migration and Integration

An administrator must migrate a shared Incident form layout change from a development instance. The administrator created and opened Incident Release before saving the change.

Source evidence at save time:

The generated Customer Update record is in Global scope and references Default. Which issue caused the change to be missing from Incident Release?

Options:

• A. The shared layout was stored as a user personalization when saved.

• B. The Incident Release set was not Complete when the layout was saved.

• C. The Global application scope prevented the layout from being captured.

• D. The Default update set was current when the layout was saved.

Best answer: D

Explanation: Tracked configuration changes are captured in the update set that is current for the relevant application scope when the change is saved. Creating or opening an update set does not make it current. Here, Default was current, and the generated Customer Update record directly confirms that the layout change was captured there.

An update set should remain In Progress while collecting changes; marking it Complete is a later transfer step. The evidence also shows a shared, tracked configuration change rather than a personal preference. The key check is the Customer Update record’s update set reference.

• Completion state: An update set remains In Progress while collecting changes; completion is not required for captured records to appear.
• Personalization: A shared layout and generated Customer Update record indicate tracked configuration rather than a user-specific preference.
• Application scope: Global scope supports update-set capture, and the existing Customer Update record proves that capture occurred.

Question 40

Topic: Database Management and Platform Security

An administrator imports user updates.

• Existing user: user_name E104, name Alicia G., department Finance
• Staged row: E104, Alicia Gomez, Field Operations
• No cmn_department record has the name Field Operations

Transform field maps:

Which TWO conclusions are valid after transformation?

Options:

• A. Department text is resolved by matching cmn_department.sys_id.

• B. The E104 user is updated, and its Finance department remains.

• C. Department text is resolved by matching cmn_department.name.

• D. The user_name coalesce match also determines the referenced department.

• E. A Field Operations department is created and assigned to E104.

Correct answers: B and C

Explanation: A reference field stores a relationship to another record, but an import can resolve human-readable source text through a configured reference value field. Here, Field Operations is compared with cmn_department.name, not with a department sys_id.

Because no matching department exists and Choice action is Ignore, the transform omits that field assignment instead of creating a department. Separately, coalesce compares E104 with sys_user.user_name. The matching user is updated with Alicia Gomez, while the ignored department mapping leaves Finance unchanged. Coalesce identifies the target user record; it does not resolve the user’s department reference.

• System identifier lookup does not apply because the reference value field explicitly specifies name.
• Coalesce as reference lookup confuses target-record matching with resolution of a separate reference field.
• Automatic department creation would require Create handling rather than the configured Ignore action.

Question 41

Topic: Data Migration and Integration

An administrator configures the following on the Incident table:

• An active UI Policy makes Assignment group mandatory when Category is Network. It applies to the desktop view being tested.
• An active before-insert Business Rule contains:

if (current.category == 'network' && gs.nil(current.assignment_group)) {
    current.setAbortAction(true);
}

A transform map targets Incident, has Run business rules selected, and processes a Network row with no Assignment group. A user also selects Network on a new Incident form.

Which TWO conclusions are valid?

Options:

• A. The transform map bypasses the before Business Rule because staging occurred first.

• B. The UI Policy rejects the matching import-set row during source staging.

• C. The before Business Rule marks Assignment group mandatory before browser submission.

• D. The before Business Rule aborts the matching target insert during transformation.

• E. The UI Policy marks Assignment group mandatory on the matching browser form.

Correct answers: D and E

Explanation: UI Policies control form behavior in the user interface. When the user selects Network in the applicable desktop view, the UI Policy makes Assignment group mandatory. UI Policies do not execute against rows loaded into an import set or enforce target-table data operations during transformation.

Business Rules execute server-side during applicable database operations. Because the transform map is set to run Business Rules, its attempted Incident insert invokes the active before-insert rule. The Network category and empty Assignment group satisfy the script condition, so setAbortAction(true) prevents the target record from being inserted. Import-set staging occurs before transformation, but it does not exempt the later target operation from enabled Business Rules.

• Source staging is not rejected by an Incident UI Policy because form behavior does not execute on imported rows.
• Browser presentation is not changed by the before Business Rule, which runs server-side during the record operation.
• Staging bypass is incorrect because the transform map explicitly enables Business Rules for target operations.

Question 42

Topic: Platform Overview and Navigation

Which shared ServiceNow platform capability supplies the common record model for assignable work, including fields such as number, state, priority, assignment group, and assigned to, for tables that extend Task?

Options:

• A. User and group administration

• B. Task management framework

• C. Configuration Management Database

• D. Workflow Studio automation

Best answer: B

Explanation: The task management framework provides the common structure for work records on tables that extend the Task table. Incident, problem, change, and other task-based tables inherit standard fields and behaviors for numbering, assignment, state, priority, and activity tracking. This inheritance lets applications manage different kinds of work through a consistent platform model.

Other shared capabilities can support task processing, but they do not supply this common record model. User administration provides identities and groups, the CMDB stores configuration data and relationships, and Workflow Studio automates processes involving records.

• User administration supplies users, groups, and roles but does not define the inherited work-record structure.
• CMDB represents configuration items and relationships rather than the common model for assignable tasks.
• Workflow automation executes triggers and actions but does not provide the underlying Task table inheritance.

Question 43

Topic: Database Management and Platform Security

An organization has a Business Application record for its Claims Portal, used for portfolio ownership and lifecycle management. The production deployment is separately monitored, receives incidents and changes, and depends on web and database CIs. Administrators must use current CSDM terminology while preserving the existing portfolio record.

Which record should represent the production deployment?

Options:

• A. Create a Service Instance and relate it to the supporting CIs.

• B. Create another Business Application and relate it to the supporting CIs.

• C. Create a Technical Service and relate it to the supporting CIs.

• D. Create a Service Offering and relate it to the supporting CIs.

Best answer: A

Explanation: CSDM separates conceptual portfolio records from operational deployments. The Business Application represents the Claims Portal from ownership, investment, and lifecycle perspectives. Its monitored production deployment is represented as a Service Instance, the current term for the concept formerly called an application service. Relationships from that Service Instance to web, database, and other supporting CIs provide operational context for incidents, changes, and impact analysis.

A Technical Service describes a broader technology capability, while a Service Offering describes a defined way that a service is provided or consumed. Neither replaces the record for a specific runtime deployment.

• Creating another Business Application would duplicate the portfolio entity rather than represent its production deployment.
• A Technical Service represents a broader provider capability, not this specific runtime deployment.
• A Service Offering represents a defined service package or commitment, not the deployed runtime topology.

Question 44

Topic: Database Management and Platform Security

A record’s Business owner reference shows the same unintended user on both the form and a report. Inspection confirms that the stored reference value resolves to that user’s record. Which element should be investigated first?

Options:

• A. The user table’s display-field configuration

• B. The form view’s Business owner field placement

• C. The report’s Business owner grouping configuration

• D. The record’s stored Business owner reference value

Best answer: D

Explanation: A reference field stores a link to another record, typically using its sys_id, while the interface displays a readable value from that referenced record. When both a form and a report show the same unintended owner, and the stored reference resolves to that user’s record, the shared source data is incorrect. Form layout controls where a field appears, and report configuration controls how results are presented; neither changes the underlying reference. A display-field issue could alter the label shown for referenced records, but it would not make the stored value resolve to the wrong user record. The key distinction is whether the underlying relationship is wrong or only its presentation is wrong.

• Form placement affects field presentation, not the user record identified by the stored reference.
• Report grouping organizes report output but does not change the source record’s owner reference.
• Display-field configuration controls readable labels, while the evidence confirms resolution to the wrong referenced record.

Question 45

Topic: Data Migration and Integration

An administrator imports Incident records through an import set and transform map.

Current configuration:

• A UI policy makes Caller mandatory when Category is Inquiry.
• The browser form displays the mandatory indicator correctly.
• Imported Inquiry incidents with an empty Caller are still inserted.

The administrator must enforce the requirement during imports and retain the immediate browser-form indicator, using one declarative policy and no script. Which change meets the requirement?

Options:

• A. Replace it with a matching data policy; enable client use but disable import-set use.

• B. Replace it with a matching data policy; enable import-set use but disable client use.

• C. Retain it and set the transform map to enforce all mandatory fields.

• D. Replace it with a matching data policy; enable import-set and client use.

Best answer: D

Explanation: A UI policy controls client-side form behavior, so its mandatory indicator does not enforce the requirement during an import-set transformation. A matching data policy provides server-side mandatory enforcement. Enabling its import-set setting applies that enforcement to transformed rows, while enabling client use presents the same immediate mandatory behavior on browser forms.

The transform map’s mandatory-field setting does not convert a conditionally mandatory UI policy field into a server-enforced field. Both data-policy settings are therefore needed to satisfy the two channels with one declarative rule.

• Disabling client use omits the immediate form indicator, although the import-set requirement is enforced.
• Disabling import-set use preserves browser behavior but allows the import channel to bypass this requirement.
• Transform-map mandatory enforcement does not apply the conditional mandatory state created by a UI policy.

Question 46

Topic: Self Service and Automation

A knowledge manager revised and reviewed an article at the start of the second 30-day period. It remained Published with unchanged user criteria. Searches for the same issue remained stable, and no service or support-process changes occurred.

Authenticated views were correlated with incidents for the same user and issue.

Which interpretation is best supported?

Options:

• A. Evidence supports effective self-service: article use rose while viewer-created incidents and repeat contacts fell.

• B. Evidence shows improved agent resolution: fewer repeat contacts primarily reflect better incident handling.

• C. Evidence remains inconclusive: changing viewer counts prevent a valid comparison of the two periods.

• D. Evidence shows discoverability only: helpful ratings are required before reduced assistance can be inferred.

Best answer: A

Explanation: Knowledge effectiveness is evaluated by pairing article consumption with downstream support outcomes for the same issue. Unique readership more than doubled, while the post-view incident rate fell from 72 of 180 viewers (40%) to 38 of 420 viewers (about 9%). Repeat contacts also fell from 26 to 7. Stable search demand, publication status, audience criteria, and support processes strengthen the interpretation that the maintained article helped users resolve the issue themselves. This evidence supports reduced assistance, although it does not prove absolute causation. Helpful ratings can add context, but they are not required when direct support outcomes are available.

• Ratings required fails because post-view incidents and repeat contacts provide more direct evidence of reduced assistance.
• Agent resolution is insufficient because incidents after article views also fell and the support process did not change.
• Changing viewer counts does not invalidate comparison because the incident rate fell substantially despite the larger audience.

Question 47

Topic: Platform Overview and Navigation

An administrator is coaching a technician who uses Next Experience Unified Navigation. The technician is authorized to read incidents. Incident > All is not a favorite, but the technician opened incident INC0010472 earlier today.

Which TWO statements correctly identify navigation elements that can help the technician locate these items?

Options:

• A. The All menu filter can locate the Incident application and All module.

• B. History can display the recently accessed incident for reopening.

• C. The All menu filter can locate the incident by its record number.

• D. History contains only items that the technician explicitly saved as favorites.

• E. Favorites will include Incident > All because the module was previously opened.

Correct answers: A and B

Explanation: Next Experience Unified Navigation separates application navigation, favorites, and recent activity. The All menu filter helps users find applications and modules available in their navigation menu. History provides access to recently viewed items, so the previously opened incident can appear there. Favorites contains only items the user has intentionally added; opening a module does not automatically make it a favorite. The All menu filter searches navigation entries rather than record field values such as an incident number.

Finding an application or module in navigation also does not grant record access, which is why the technician’s read authorization is stated separately.

• Automatic favorite fails because previously opening a module does not add it to Favorites.
• Record-number menu search fails because the All menu filter searches applications and modules, not incident records.
• Favorites-only history fails because History tracks recently accessed items independently of Favorites.

Question 48

Topic: Instance Configuration

An administrator must enable automatic approval in the scoped Asset Checkout application.

Current state:

• All Available Applications lists the application as Installed.
• Its modules and tables open, and manual approvals work.
• Application setup shows Automatic approval = Off and Approval group = blank.
• The bundled approval flow is active, but a test request creates no flow execution.

Constraint: The change window permits configuration changes but no installations or upgrades.

Which conclusion best describes the instance?

Options:

• A. The application is installed, but automatic approval still requires configuration.

• B. The application is available, but installation must finish before feature setup.

• C. The application is installed, but automatic approval is delayed in execution.

• D. The application is installed, but module visibility is blocking automatic approval.

Best answer: A

Explanation: Application installation and feature configuration are separate states. The Installed status and accessible modules, tables, and records confirm that the application files are deployed. However, automatic approval is disabled and its required approval group is blank, so that feature is not configured for use.

An active flow means its definition can execute when triggered; it does not enable an application-level feature or supply missing settings. The absence of a flow execution also indicates that processing did not start, rather than merely being delayed. The administrator should configure the approval group, enable automatic approval, and then retest.

• Delayed execution does not fit because no flow execution was created and the controlling feature remains disabled.
• Incomplete installation conflicts with the Installed status and the accessible application modules and tables.
• Module visibility is not the blocker because the modules already open and the missing feature settings are visible.

Question 49

Topic: Configuring Applications for Collaboration

An administrator is validating a Platform Analytics bar visualization. The source table contains exactly these records:

Visualization settings:

• Filter: Active is false AND (Priority is 1 OR Priority is 2)
• Group by: Assignment group
• Aggregation: Average of Resolution hours

Which values should the bars display?

Options:

• A. Network: 2 incidents; Service Desk: 2 incidents

• B. Network: 8 hours; Service Desk: 6 hours

• C. Network: 16 hours; Service Desk: 12 hours

• D. Network: 7 hours; Service Desk: 7 hours

Best answer: B

Explanation: The filter is applied before grouping and aggregation, leaving INC001, INC002, INC004, and INC006. The Network group averages 6 and 10 hours, producing 8 hours. The Service Desk group averages 4 and 8 hours, producing 6 hours. The aggregation setting determines that each bar represents an average, not a sum or record count. An overall average of all four included records would be 7 hours, but grouping requires a separate calculation for each assignment group.

• Summing values produces 16 and 12 hours, but the configured aggregation is Average rather than Sum.
• Counting records produces two incidents per group, but the visualization aggregates the Resolution hours field.
• Using one overall average produces 7 hours, but it ignores the configured assignment-group separation.

Question 50

Topic: Database Management and Platform Security

An organization already stores configuration items in the CMDB. However, incident, change, and portfolio teams represent business applications, Service Instances, and service offerings with inconsistent relationships.

The administrator must establish a shared structure for service-related data while retaining the existing CMDB and without requiring automated discovery. Which concept should the administrator apply?

Options:

• A. Apply Service Mapping patterns as the shared modeling standard

• B. Apply CSDM as the shared modeling standard

• C. Apply IRE rules as the shared modeling standard

• D. Apply CMDB class hierarchy as the shared modeling standard

Best answer: B

Explanation: The Common Service Data Model (CSDM) provides ServiceNow’s standard guidance for organizing service-related records and relationships consistently across platform products. It works with the CMDB rather than replacing it. In this situation, CSDM can align how teams represent business applications, Service Instances, service offerings, and their relationships.

The CMDB stores configuration data, but its class hierarchy alone does not define the broader service-data model. IRE controls how incoming CI data is identified and reconciled, while Service Mapping discovers and maps service dependencies. Neither provides the cross-platform organizational structure required here.

• CMDB hierarchy organizes CI classes but does not provide the complete service-data modeling guidance needed across teams.
• IRE rules manage CI identification and source reconciliation rather than defining service domains and relationships.
• Service Mapping patterns discover application dependencies rather than establish an organization-wide service-data standard.

Questions 51-60

Question 51

Topic: Database Management and Platform Security

Dana is using a standard session with no elevated privileges. No ACLs other than those listed apply.

• Dana belongs to the Hardware Support group, which has the x_asset.editor role.
• Dana directly has the x_asset.viewer role.
• The active asset record passes a table write ACL whose required roles are x_asset.editor and x_asset.manager.
• The Status field has a write ACL requiring x_asset.manager.
• The Description field has no field-level write ACL.
• Dana can see the application’s module.

Which TWO conclusions are valid? Select TWO.

Options:

• A. Dana can update Status once the table write ACL has allowed access.

• B. Dana can update Description because the applicable table write gate is satisfied.

• C. Dana’s direct x_asset.viewer role satisfies the table write role requirement.

• D. Dana inherits x_asset.editor through membership in Hardware Support.

• E. Dana’s module visibility establishes write permission for records in the table.

Correct answers: B and D

Explanation: Group membership can provide inherited roles, so Dana has x_asset.editor. Roles listed within an ordinary ACL’s required-role section are alternatives; Dana does not also need x_asset.manager to pass the table write ACL. Because Description has no additional field-level write restriction, the table authorization permits that update.

Status is different. Record access must satisfy both the applicable table and field gates, and Dana lacks the role required by the Status ACL. Module visibility controls navigation availability and does not prove record authorization.

• The direct viewer role permits viewing but does not match either role listed by the table write ACL.
• Passing the table ACL does not bypass the more specific Status field write ACL.
• Seeing a module in navigation is separate from authorization to write its table records.

Question 52

Topic: Instance Configuration

An itil user opens an incident in the standard platform form through Unified Navigation. The Customer reference field is missing.

• The same user sees the populated field in the incident list and Default form view.
• The field is absent only in the Service Desk form view.
• No UI policy or client script targets the field.
• The Service Desk view and existing access controls must remain.

Which action should the administrator take?

Options:

• A. Add the field to the Service Desk form layout.

• B. Create a field ACL that grants read access to itil.

• C. Add the field to the Service Desk list layout.

• D. Create a UI policy that shows the field on load.

Best answer: A

Explanation: Form layouts determine which fields appear in each form view. Because the same user can read the populated field in both a list and the Default form view, neither the data nor field read access is the problem. Its absence only from the Service Desk view indicates that the field is omitted from that view’s form layout. A UI policy can change the behavior of a field already present on the form, but it does not add a field to a view. The administrator should therefore modify the Service Desk form layout while preserving the current view assignment and access controls.

• List layout controls columns displayed in a list, not fields displayed on a record form.
• UI policy cannot display a field that is absent from the selected form view’s layout.
• Field ACL is not the cause because the same user can already read the field in other interfaces.

Question 53

Topic: Self Service and Automation

A solution to a common user issue consists of reusable troubleshooting instructions. It should be searchable in self-service and maintained through a publication lifecycle; it does not need to create a request or task. Which ServiceNow mechanism should store the solution?

Options:

• A. A knowledge article

• B. A standard catalog item

• C. A record producer

• D. A Virtual Agent topic

Best answer: A

Explanation: A knowledge article is a reusable content record designed for searchable self-service information. Its lifecycle can manage drafting, review, publication, and retirement. This fits troubleshooting instructions for a repeated issue when users do not need to initiate a transaction. Catalog items support requested-item fulfillment, while record producers create records such as incidents. Virtual Agent topics manage conversational interactions and may present knowledge or initiate fulfillment, but they are not the primary record for maintaining reusable guidance. Searchable instructions governed through publication therefore belong in Knowledge Management.

• A standard catalog item initiates a request and fulfillment process rather than storing reusable troubleshooting guidance.
• A record producer creates a target record, such as an incident, instead of publishing self-service content.
• A Virtual Agent topic defines a conversation and can reference knowledge, but it is not the primary managed content record.

Question 54

Topic: Self Service and Automation

A Virtual Agent topic invokes the catalog fulfillment action Submit Workplace Accessory Request after collecting these values:

• employee: Jordan Lee, sys_id 7b9130f2db204110a83f7d5f9619ab42
• accessory: USB-C dock
• notes: empty

Which TWO conclusions accurately describe this execution and its configured missing-value behavior?

Options:

• A. requested_for receives 7b9130f2db204110a83f7d5f9619ab42.

• B. delivery_notes receives an empty value.

• C. delivery_notes receives No special instructions.

• D. requested_for receives Jordan Lee.

• E. A missing accessory invokes the action with an empty value.

Correct answers: A and C

Explanation: Virtual Agent topic variables and catalog variables are separate, so the configured mappings determine what fulfillment receives. Because requested_for maps from employee.sys_id, the action receives the user record identifier rather than its display value. The optional notes variable is empty, so its configured default supplies No special instructions to delivery_notes.

Required information is handled differently: if employee or accessory is missing, the conversation returns to the relevant collection step and does not invoke the catalog action. Thus, defaults can resolve designated optional values, while required-value checks prevent incomplete fulfillment submissions.

• Mapping the display name ignores the configured employee.sys_id source.
• Leaving delivery notes empty ignores the stated default for missing notes.
• Invoking with a missing accessory conflicts with the required-value behavior that returns to collection.

Question 55

Topic: Database Management and Platform Security

An administrator reviews Dana’s access and incident assignment. Dana has no directly assigned roles or other group memberships, and no automation populates assigned_to.

Which TWO conclusions are valid?

Options:

• A. Dana effectively gains itil because the incident is assigned to her group.

• B. Dana effectively has x_app.case_reader through membership and role containment.

• C. INC0010462 is individually assigned to Dana through her group membership.

• D. Dana has a direct x_app.case_reader user-role assignment from containment.

• E. INC0010462 remains group-assigned because assigned_to is still empty.

Correct answers: B and E

Explanation: Effective roles can come from both group membership and role containment. Dana inherits x_app.change_coordinator from the Change Coordination group, and that role contains x_app.case_reader, so the contained role is also effective. This inheritance does not make the role a direct assignment to Dana.

Task assignment is separate from role inheritance. assignment_group identifies the responsible group, while assigned_to identifies an individual. Because assigned_to is empty and no automation fills it, the incident is not individually assigned to Dana. Assigning work to a group also does not grant the group’s members unrelated roles such as itil.

• Direct role assignment is incorrect because containment produces inherited entitlement, not a direct assignment to Dana.
• Role from task assignment is incorrect because assigning an incident to a group does not grant itil.
• Automatic individual assignment is incorrect because group membership alone does not populate assigned_to.

Question 56

Topic: Configuring Applications for Collaboration

An incident manager needs today’s active backlog and a daily backlog trend for the previous 12 months.

Available data:

• Incident records contain their current values, but not enough state history to reconstruct prior daily backlog snapshots.
• A Performance Analytics indicator has collected daily backlog scores for the last 90 days with no missed collections.
• No earlier scores or snapshots exist.

Which TWO conclusions are valid?

Options:

• A. A current-record report can show today’s active incident backlog.

• B. The collected indicator can show the last 90 days of backlog history.

• C. A dashboard refresh can create the missing historical indicator scores.

• D. The indicator can derive the earlier nine months from current records.

• E. A current-record report can reproduce 12 months of daily backlog snapshots.

Correct answers: A and B

Explanation: A current-record report queries records as they exist when the report runs, so it can provide today’s active backlog. A Performance Analytics indicator supports historical trending by storing scores during scheduled collections. Because daily scores have been collected for only 90 days, the available trend is limited to that period.

Missing historical scores are not automatically created from current records, especially when the records lack enough state history to reconstruct past daily conditions. Displaying content on a dashboard or refreshing it also does not convert current data into collected historical observations.

• Reproducing 12 months of snapshots is unsupported because current values do not preserve the required daily historical states.
• Deriving the earlier nine months is impossible because neither collected scores nor sufficient record history exists.
• Refreshing a dashboard displays available data but does not retroactively collect indicator scores.

Question 57

Topic: Database Management and Platform Security

An administrator opens a Company record. The instance permits duplicate company names, and the exhibit abbreviates sys_id values.

• Current company: Alpine Data, sys_id = c10
• Related-list relationship: alm_asset.company = core_company.sys_id
• Additional filters: None

Which TWO asset records should appear in the Assets related list?

Options:

• A. Asset AST-1001

• B. Asset AST-1005

• C. Asset AST-1003

• D. Asset AST-1004

• E. Asset AST-1002

Correct answers: A and C

Explanation: A reference field stores a link to another record, represented here by the referenced record’s sys_id. This related list includes asset rows whose company reference equals the current Company’s sys_id, c10. Therefore, the qualifying rows are those with c10 in the Company reference column. Displayed company names do not establish the relationship because multiple Company records can have identical or similar display values.

The stored reference value, not matching display text, determines related-list membership.

• AST-1002 references c20; its identical displayed company name does not link it to c10.
• AST-1004 references c30; a similar company name does not satisfy the relationship.
• AST-1005 references c40; duplicate display text does not override the stored reference.

Question 58

Topic: Configuring Applications for Collaboration

A notification must email the Requested for user, Assigned to user, and the record’s Release coordinator when a release task changes to Ready for Implementation. The coordinator varies by record, and only these record-specific users may receive it. Assigned to must remain the implementation owner.

Evidence:

• Condition evaluation: State changes to Ready for Implementation = true
• u_release_coordinator: active user with valid email and notifications enabled
• Configured recipients: Requested for, Assigned to
• Resolved recipients: Requested for, Assigned to
• sys_email state: Sent to the two resolved recipients

Which administrative action should resolve the missing notification?

Options:

• A. Add the Release Coordination group directly to Groups on the notification.

• B. Add the current coordinator directly to Users on the notification.

• C. Set Assigned to to the coordinator during the state transition.

• D. Add u_release_coordinator to Users/Groups in fields on the notification.

Best answer: D

Explanation: Notification processing includes trigger and condition evaluation, recipient resolution, and outbound email generation. Here, the transition condition evaluated true and a sent sys_email record exists, so the notification reached the outbound stage. The coordinator is absent from the resolved recipient list because the notification does not use the populated coordinator field. Adding that user-reference field to Users/Groups in fields resolves the correct user dynamically for each record while preserving ownership and recipient limits.

Changing the transition or ownership would address the wrong stage of notification processing.

• A static user entry fails when another record identifies a different coordinator.
• A coordination group would notify users beyond the permitted record-specific recipients.
• Reassigning the task would replace the required implementation owner and alter process logic.

Question 59

Topic: Instance Configuration

A ServiceNow administrator reviews a change to activate the Performance Analytics Premium plugin in production.

Current state:

• Performance Analytics Core is active in production and a recent subproduction clone.
• Premium is active only on the clone.
• Data collection and dashboard rendering passed validation on the clone.
• The proposed backout is to deactivate Premium and back out the change’s update set.

Product notes: Premium requires Core and cannot be deactivated after activation. Backing out an update set does not uninstall a plugin. Production policy requires a supported recovery plan.

What should the administrator do before approving the activation?

Options:

• A. Return the change to reactivate Core on the clone before using update-set backout for Premium.

• B. Approve the change and use update-set backout to remove Premium if production validation fails.

• C. Return the change to document a supported recovery plan that acknowledges Premium’s non-reversibility.

• D. Return the change to test Premium deactivation on the clone before activating it in production.

Best answer: C

Explanation: Plugin activation is an instance capability change, not ordinary configuration transported or removed through an update set. Core is already active in both environments, and Premium passed the required subproduction validation, so the dependency and testing conditions are satisfied. The remaining defect is the recovery plan: the product notes explicitly state that Premium cannot be deactivated and that update-set backout will not uninstall it. The change must therefore document a supported recovery approach that recognizes the activation’s non-reversible nature before approval. Additional clone testing cannot make an unsupported deactivation method valid.

• Update-set backout reverses tracked configuration changes, not the activation or installation of the Premium plugin.
• Deactivation testing conflicts with the product note stating that Premium cannot be deactivated after activation.
• Reactivating Core is unnecessary because Core is already active, and it does not correct the unsupported backout plan.

Question 60

Topic: Self Service and Automation

An active contractor with no elevated roles cannot open a knowledge article.

• The article is Published and within its valid dates.
• Its Can Read criterion includes active users; its Cannot Read criterion includes contractors. The user matches both.
• The knowledge base has no user criteria.
• glide.knowman.block_access_with_no_user_criteria is enabled and blocks knowledge bases that have no user criteria.
• The user is not in the article’s ownership group.

Which TWO facts independently explain the lack of access?

Options:

• A. The user’s absence from the article ownership group

• B. The matching article-level Cannot Read user criterion

• C. The article’s current Published lifecycle state

• D. The matching article-level Can Read user criterion

• E. The enabled block for knowledge bases with no user criteria

Correct answers: B and E

Explanation: Knowledge visibility requires both lifecycle eligibility and successful access evaluation. The article is published and within its valid dates, so its lifecycle does not prevent reading. At the article level, the user matches both criteria, but the applicable Cannot Read criterion excludes the contractor despite the Can Read match. Separately, the instance property changes the normal handling of a knowledge base with no user criteria: access is blocked rather than presumed open. Either access barrier is sufficient to hide the article.

Ownership-group membership governs article stewardship and does not itself determine ordinary read access.

• A matching Can Read criterion does not overcome the applicable Cannot Read criterion.
• The current Published state and valid dates make the article lifecycle-eligible.
• Ownership-group membership concerns article management, not ordinary reader access.

Continue in the web app

Use IT Mastery for interactive ServiceNow CSA practice with mixed sets, timed mocks, topic drills, explanations, and progress tracking.

Try ServiceNow CSA on Web