Discovery Pattern Design practice questions

Use the 'Related CI' step within the Identification section.

The 'Related CI' step establishes relationships between the discovered CI and existing infrastructure.

Using CI Identification Rules

Identification rules are the primary mechanism for matching CIs.

Matching on Serial Number

Matching on serial number satisfies the requirement to identify a CI using a unique hardware attribute. Serial numbers are typically unique per device, so the pattern can reliably correlate discovered data with an existing CI record, avoiding duplicates. This makes it a valid identification method alongside other unique identifiers such as MAC address or hostname.

Using a temporary variable

Patterns can identify a CI by assigning a discovered value to a temporary variable during horizontal or vertical discovery steps, then using it to populate the CI field. This is a valid identification method alongside direct attribute mapping.

Set Parameter Value

This is used for assigning values to variables or attributes.

To establish relationships between the current CI and other CIs.

The Connection section defines how the current CI relates to other CIs, specifying the relationship type and target CI so discovered components are linked correctly. This satisfies the stem by establishing the dependency and containment links that populate the CMDB relationship map.

The Identification rule does not support the CI class.

If the identification rule isn't configured for the class, identification will fail even if attributes are found.

Identification section

The identification section handles matching the CI to a record and setting its attributes.

It executes commands to gather data from the target.

The discovery section contains steps to run OS commands and collect data.

The pattern fails the step with an 'Undefined Variable' error.

Referencing an undefined variable leaves the pattern step without a resolvable input, so execution halts and reports an 'Undefined Variable' error. This satisfies the scenario's constraint: variables must be defined in an earlier step before a later step can consume them.

They must be the first section in the pattern.

Identification sets the primary CI context for the rest of the pattern.

Pattern parameters

Pattern parameters are declared inputs that carry values across sections, letting one section consume data produced or supplied elsewhere in the pattern. This is a valid data-passing mechanism, satisfying the stem's requirement for ways to move data between sections.

Defined variables

Defined variables are declared within the pattern and persist across its sections, so a value set in one section is readable by later sections. This is a valid data-passing mechanism, satisfying the stem's requirement for ways to move data between sections.

The target attribute must exist on the CI class

The CMDB class must support the attribute.

The pattern must correctly capture the data from the target

Data must be extracted first.

The attribute must be mapped in the pattern

Mapping is required to populate the field.

The pattern moves from 'Draft' to 'Active'

Publishing changes the pattern's state from Draft to Active, making it a usable, live artefact rather than an editable work-in-progress. This state transition is one of the actions the stem asks about when a pattern is published.

The pattern is made available to discovery schedules

Once Active, the pattern becomes selectable by discovery schedules, so Discovery can invoke it during horizontal and vertical scans. This availability to schedules is one of the actions the stem asks about when a pattern is published.

The pattern is saved as a new version

Publishing saves the pattern as a new version, preserving version history so prior iterations remain recoverable and changes are auditable. This versioning action is one of the actions the stem asks about when a pattern is published.

JSON

Supported by the Parse step.

XML

Supported by the Parse step.

Regex

Supported by the Parse step.

Parse

Parse is a selectable step type that extracts fields from raw discovery payloads using defined parsing logic. It satisfies the question's requirement by being one of the concrete step operations available when creating a New Step in a pattern.

Lookup

Lookup is a selectable step type that queries existing CMDB records or reference tables to enrich or correlate discovered data during pattern execution. It qualifies as one of the concrete operations offered when creating a New Step.

Command

Command steps execute a shell command or script on the MID Server host during a discovery schedule, letting you run custom logic outside standard probes. This satisfies the scenario's need for an executable action type when defining a New Step in the discovery workflow.

Runs on

A common relationship type.

Depends on

A common relationship type.

The system creates duplicate CIs for the same asset

This is a classic symptom of poor ID rules.

Discovery fails with 'No identification rule'

The rule is missing or not configured for the class.

Line Delimiter

The line delimiter defines how lines are split, which is critical for parsing configuration files.

Use the Parse Delimited Text step

Parse Delimited Text splits a delimited string into columns using a specified delimiter, producing tabular output directly. This handles the comma-separated key-value pairs in one step, avoiding manual string parsing or scripting to build the table.

Connection Definition

Connection definition is where the access parameters are defined.

Review the IRE payload in the Discovery Log to ensure the data is being sent to the CMDB

Reviewing the IRE payload confirms if data reached the CMDB.

Check the Pattern Debugger to confirm the variable contains the expected value

Verification of data extraction is the first step.

Verify the Identification Rule to ensure the attribute is not ignored or read-only

If the IRE rule prevents the update, the pattern will fail to populate it.