10 free sample questions from a bank of 104, with the correct answers and explanations. No signup required — start practising right now.
ABD — merge into a CMDB-named table inside an application pattern gated by executablePath. The screenshot shows a table-merge style operation that lands in a CMDB-named target, the surrounding pattern is application-type, and the step can only run when process dot executablePath already has data.
A is correct because the operation pulls attributes from two sources into a table mirroring a CMDB table, which is how merge steps stage CI data. B is correct because an operation keyed on process dot executablePath belongs to an application pattern flow. D is correct because the step consumes executablePath as input, so an empty value leaves it with nothing to match or merge.
Think path means process means application pattern, and application merges need a populated executablePath to fire.
C — SNMP discovery needs read community strings. Discovery only polls devices for inventory, so a read-only community string is sufficient and expected, while write strings, interactive usernames, and Windows port 135 have no role in the SNMP credential.
Discovery SNMP probes issue GET and walk requests against device MIBs to identify class, model, and serial data, and a read community string provides exactly that authority. PDI behavior confirms that the read string lets SNMP identification succeed, while no write operation is ever issued by Discovery. Granting only read access therefore satisfies function and least privilege for enterprise scanning.
Remember read to see, write to change, and Discovery only ever needs to see SNMP data.
A — Shared libraries are contained in an extension section. Extension sections hold reusable customization logic, and shared libraries are the textbook example. If the question asks what lives in an extension, choose shared libraries.
ServiceNow pattern documentation for modifying patterns with extensions describes extension sections as the place for added logic such as shared libraries. Connection sections and identification sections belong to the main pattern flow, not inside an extension. Shared libraries fit the extension purpose exactly because they are reusable and kept separate from base logic so upgrades do not overwrite custom work. That alignment makes A the only choice consistent with the documented pattern model.
Think extension equals customization: shared libraries go in extensions so base patterns stay upgrade-safe.
BC — Retry Discovery and View instructions are the bulk remediation actions. On the Discovery Home Automated Error Messages list, ACTION ON ALL lets an operator re-run discovery for the filtered errors and open the per-error guidance, which matches PDI behavior and crowd confirmation.
B is correct because re-running discovery is the core bulk remediation once errors are triaged, and the Recommended Actions menu exposes Retry Discovery for ACTION ON ALL in a PDI. C is correct because each automated error carries curated help text, and View instructions surfaces that guidance for every selected row at once. Community verification in a PDI plus the vendor explanation listing Mark as assigned, Create a task, Retry Discovery, and View instructions corroborates exactly this pair as the available bulk choices.
For error-list bulk actions think retry the run and read the fix, never rebuild ranges there.
AC — Delimited Text parsing offers Delimiters and Positions. In a Parse Variable step using the Delimited Text strategy, the designer picks the separator characters and the positional extraction settings, confirmed in PDI as Variables, Line Separator, Delimiters, and Positions.
A is correct because positional mapping is how the designer tells Discovery which delimited column feeds each variable, and PDI shows Positions on the step form for this strategy. C is correct because without declaring delimiter characters the engine cannot split the line, so Delimiters is a mandatory control for this parsing mode. Together with Variables and Line Separator they form the complete Delimited Text control set visible in Pattern Designer, which is why crowd discussion and PDI checks converge on A and C.
Delimited means declare the divider plus the positions you want to keep.
C — Create Relation slash Reference builds relationships in horizontal patterns. It links discovered CIs to related items during pattern execution per vendor documentation.
C is correct because ServiceNow documentation for creating a relationship and reference identifies this operation as the way to create relationships between CIs and related items inside a pattern. Pattern authors add this step after identification to persist graph edges.
When the stem asks how patterns create relationships, choose Relation slash Reference every time.
B — CI identifiers are viewed under CI Class Manager. CI identification rules and their identifiers are managed per class in CI Class Manager. When asked where to see identifiers, pick CI Class Manager.
ServiceNow documentation for creating CI identification rules directs administrators to the CI Class Manager to view and manage identifiers. The Dashboard shows Discovery status and errors, not identifier definitions. Process handlers and classification lists deal with execution flow, not identifier viewing. CI records show instance values, not the identifier rule model. Only CI Class Manager presents the identifier entries per class, so B is decisively correct.
Link identifiers to classes: if you need to see or edit identifiers, open CI Class Manager, not Discovery home.
C — raising MID Server thread count also demands more MID memory. Each concurrent probe thread consumes heap and CPU on the MID host, so increasing max threads without raising the memory allocation risks slowdowns, queue backup, and out-of-memory restarts.
C is correct because concurrent probes each hold payloads and connection state in memory at once, so more threads raise peak heap demand. Thread increases without more memory produce sluggish MIDs, stuck ECC outputs, and restarts under load. Raising MID memory is therefore the documented companion change when max threads is raised.
More threads means more simultaneous work in memory, so size heap with threads.
A — the Discovery Schedule Location field populates CI Location. When a schedule carries a location value, discovered CIs from that run inherit it for site attribution, which is the documented and KB-backed behavior for this exact question.
A is correct because the schedule is the only listed object whose location is designed to propagate to result CIs at scale across an entire subnet or site scan. The cited KB and community consensus confirm that setting Location on the schedule causes discovered CIs to show that location after promotion to the CMDB. This centralized approach avoids editing thousands of CI records individually and keeps site reporting consistent across recurring runs.
Need CIs tagged by site, set Location once on the schedule and let Discovery stamp them.
The correct answer is C, Check, because the osquery command itself lives in the ACC check definition. ServiceNow docs describe creating a check definition to execute the osquery command on the agent, with command text, plugin, and query parameter. A policy only schedules that check and targets CIs, so E alone does not create the action.
Agent Client Collector uses checks, check types, and policies as separate layers. A check type handles result processing, a check definition holds command plus plugin plus parameters such as the query string, and a check instance inside a policy supplies values. Policies link agents to check instances and control timing and scope. Execution therefore needs a check first, then a policy.
C is correct because the check definition contains osqueryi with logger flags and a query parameter, for example select statements against processes or logged-in users. Docs show Name util.osquery, Check type osquery, Command osqueryi with json output, Plugin osquery, and a mandatory query parameter. Without this check there is no osquery payload for any policy to schedule.
A is wrong because the ACC websocket endpoint is connectivity plumbing, not the place where an osquery string is authored. B is wrong because credential-less discovery is a Discovery capability, not an ACC osquery construct. D is wrong because infrastructure patterns belong to Pattern Designer, not ACC execution. E is wrong as the sole answer because a policy schedules checks but does not define command text; it depends on C.
For CIS-Discovery, separate definition from scheduling when you see ACC. If the stem asks what must be configured to run an osquery command, pick Check. If it asks what controls when and on which CIs it runs, pick Policy. Remember osqueryi with json and params query, plus the osquery plugin, as the giveaway.
Want the full bank of 104 questions for ServiceNow Certified Implementation Specialist - Discovery (CIS-Discovery)? See all practice exams.