ServiceNow CIS-Discovery Practice Test 45
Question 440
A second change advisory delegate at Willowbrook Payment Services revisits an unresolved finding during nonproduction Discovery regression suite: A switch responds to SNMP but is assigned to a generic network class because classification does not inspect the model identifier. A fresh run still shows: The SNMP response includes vendor and model OIDs while the classifier trace selects a generic catch-all first. Production-affecting actions require an independently verified change approval. Which ServiceNow Discovery principle BEST explains the failure? Choose ONE.
- The schedule control status describes job lifecycle and does not by itself prove all target identification succeeded
- Scanning discovers a reachable service; classification must interpret returned protocol attributes before identification
- Credential selection and affinity order should be inspected before creating new privileged accounts
- A partial discovery status must be tied to the exact failed operation, not used to justify entire schedule changes
Explanation
Correct Answer
B:Scanning discovers a reachable service; classification must interpret returned protocol attributes before identification. This is the underlying causal Discovery implementation principle for the documented fictional Willowbrook Payment Services case. The defect is: A switch responds to SNMP but is assigned to a generic network class because classification does not inspect the model identifier. The governing mechanism is: Scanning discovers a reachable service; classification must interpret returned protocol attributes before identification. The supporting measured observation is: The SNMP response includes vendor and model OIDs while the classifier trace selects a generic catch-all first. After treatment, the result must be checked: The device receives the correct network class and subsequent discovery does not duplicate the prior CI.
Incorrect Answers
A:The schedule control status describes job lifecycle and does not by itself prove all target identification succeeded. It concerns avoid assuming completion from a green schedule status, not the failure described here: A switch responds to SNMP but is assigned to a generic network class because classification does not inspect the model identifier. Scanning discovers a reachable service; classification must interpret returned protocol attributes before identification.
C:Distinguish missing credentials from wrong account selection priority is a separate consideration. In the stated situation, A switch responds to SNMP but is assigned to a generic network class because classification does not inspect the model identifier. Scanning discovers a reachable service; classification must interpret returned protocol attributes before identification. Check: The SNMP response includes vendor and model OIDs while the classifier trace selects a generic catch-all first.
D:A partial discovery status must be tied to the exact failed operation, not used to justify entire schedule changes. The question instead centers on A switch responds to SNMP but is assigned to a generic network class because classification does not inspect the model identifier; the governing distinction is scanning discovers a reachable service; classification must interpret returned protocol attributes before identification.
Question 441
During a second independent synthetic CMDB reconciliation rehearsal for Meridian Food Systems, an attempted correction to the documented failure remains unverified: A dashboard marks a rollout healthy because ninety percent of hosts succeeded, hiding failures on all high-priority database servers. The governing rule is: Coverage quality should be assessed by critical asset group and failure reason, not only aggregate discovery percentages. The decision must preserve approved CI source authority and relationship direction. Which concrete observation MOST strongly supports the reported defect?
- A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud
- The MID status has an old heartbeat timestamp despite previous completed discovery results
- A test incident requires tracing a failing database dependency but the resulting CMDB graph lacks that relationship
- The overall run success is high but per-class results show every protected database fails authentication
Explanation
Correct Answer
D:The overall run success is high but per-class results show every protected database fails authentication. This is the reproducible observation that distinguishes this failure for the documented fictional Meridian Food Systems case. The defect is: A dashboard marks a rollout healthy because ninety percent of hosts succeeded, hiding failures on all high-priority database servers. The governing mechanism is: Coverage quality should be assessed by critical asset group and failure reason, not only aggregate discovery percentages. The supporting measured observation is: The overall run success is high but per-class results show every protected database fails authentication. After treatment, the result must be checked: The database group meets its explicit target-level coverage threshold and failures are separately visible.
Incorrect Answers
A:A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud. It concerns place a mid server where it can reach an isolated plant network, not the failure described here: A dashboard marks a rollout healthy because ninety percent of hosts succeeded, hiding failures on all high-priority database servers. Coverage quality should be assessed by critical asset group and failure reason, not only aggregate discovery percentages.
B:Distinguish stale MID heartbeat from an active discovery success is a separate consideration. In the stated situation, A dashboard marks a rollout healthy because ninety percent of hosts succeeded, hiding failures on all high-priority database servers. Coverage quality should be assessed by critical asset group and failure reason, not only aggregate discovery percentages. Check: The overall run success is high but per-class results show every protected database fails authentication.
C:A test incident requires tracing a failing database dependency but the resulting CMDB graph lacks that relationship. The question instead centers on A dashboard marks a rollout healthy because ninety percent of hosts succeeded, hiding failures on all high-priority database servers; the governing distinction is coverage quality should be assessed by critical asset group and failure reason, not only aggregate discovery percentages.
Question 442
In a Discovery implementation risk workshop at Brookhaven Freight, the following behavior is documented: A custom Unix pattern references the application_home variable in a later step even though the earlier command returned an empty value. The relevant mechanism is: A dependent pattern step must consume an actually populated variable from the correct preceding operation rather than assume a value exists. The operator may not broaden credential or subnet permissions to bypass a failed test. What is the MOST immediate reliability or governance consequence?
- Duplicate dependencies can inflate downstream service impact counts
- An unrelated MID route produces false application absence and tempts unnecessary pattern edits
- Corrupt ownership data may create misleading support assignments and inventory exceptions
- An uninitialized variable can make a healthy application appear undiscoverable
Explanation
Correct Answer
D:An uninitialized variable can make a healthy application appear undiscoverable. This is the plausible direct consequence of the observed failure for the documented fictional Brookhaven Freight case. The defect is: A custom Unix pattern references the application_home variable in a later step even though the earlier command returned an empty value. The governing mechanism is: A dependent pattern step must consume an actually populated variable from the correct preceding operation rather than assume a value exists. The supporting measured observation is: The debug trace records an empty application_home variable before a file-read command attempts the nonexistent path. After treatment, the result must be checked: A replay shows application_home populated from the expected field and the next step reads the approved file.
Incorrect Answers
A:Duplicate dependencies can inflate downstream service impact counts. It concerns avoid duplicate relationship edges from repeated pattern sections, not the failure described here: A custom Unix pattern references the application_home variable in a later step even though the earlier command returned an empty value. A dependent pattern step must consume an actually populated variable from the correct preceding operation rather than assume a value exists.
B:Confirm the intended MID Server executed the pattern step is a separate consideration. In the stated situation, A custom Unix pattern references the application_home variable in a later step even though the earlier command returned an empty value. A dependent pattern step must consume an actually populated variable from the correct preceding operation rather than assume a value exists. Check: The debug trace records an empty application_home variable before a file-read command attempts the nonexistent path.
C:Corrupt ownership data may create misleading support assignments and inventory exceptions. The question instead centers on A custom Unix pattern references the application_home variable in a later step even though the earlier command returned an empty value; the governing distinction is a dependent pattern step must consume an actually populated variable from the correct preceding operation rather than assume a value exists.
Question 443
An owner-private simulated closeout at Northlake Cloud Services addresses this failure: A dependency pattern discovers a web process but fails to associate its listener with the upstream database host. Its independent defect indicator is: The process-identification step succeeds, but the connection section lists a blank remote endpoint despite an approved sample socket record. Uncommon but critical failure cases must be tested before closing the defect. Which TWO options form the appropriate remediation-and-verification pair?
- Debug the connection section against the controlled socket sample and correct the endpoint extraction mapping
- Filter nonservice interfaces and validate selected addresses against the documented target interface criteria
- The command yields the documented raw response within the approved timeout and unchanged extraction produces the expected field
- The extracted version matches one intended line and ignores subsequent warnings in regression fixtures
- The re-run emits the documented source and destination endpoints and maps only the expected application dependency
Explanation
Correct Answers
A:Debug the connection section against the controlled socket sample and correct the endpoint extraction mapping. This is the case-specific scoped correction, not a justification to expand the authorized scan or credential scope. In the fictional Northlake Cloud Services scenario, the observed defect is: A dependency pattern discovers a web process but fails to associate its listener with the upstream database host. The causal principle is: Connection discovery must collect and map endpoints before dependent relationship output can be trusted. The proposed change must still pass this independent test: The re-run emits the documented source and destination endpoints and maps only the expected application dependency.
E:The re-run emits the documented source and destination endpoints and maps only the expected application dependency. This is the independently testable outcome that validates the targeted repair. The authorized change for the fictional Northlake Cloud Services scenario is: Debug the connection section against the controlled socket sample and correct the endpoint extraction mapping. The prior failing observation was: The process-identification step succeeds, but the connection section lists a blank remote endpoint despite an approved sample socket record. A deployment record without this tested outcome does not prove effectiveness.
Incorrect Answers
B:Separate IPv4 addresses from a noisy interface enumeration is a separate consideration. In the stated situation, A dependency pattern discovers a web process but fails to associate its listener with the upstream database host. Debug the connection section against the controlled socket sample and correct the endpoint extraction mapping. Check: The process-identification step succeeds, but the connection section lists a blank remote endpoint despite an approved sample socket record.
C:The command yields the documented raw response within the approved timeout and unchanged extraction produces the expected field. The question instead centers on A dependency pattern discovers a web process but fails to associate its listener with the upstream database host; the governing distinction is debug the connection section against the controlled socket sample and correct the endpoint extraction mapping. Check: The process-identification step succeeds, but the connection section lists a blank remote endpoint despite an approved sample socket record.
D:That alternative is relevant to capture multiline service metadata with a bounded match, but the issue here is A dependency pattern discovers a web process but fails to associate its listener with the upstream database host. Debug the connection section against the controlled socket sample and correct the endpoint extraction mapping. Check: The process-identification step succeeds, but the connection section lists a blank remote endpoint despite an approved sample socket record.
Question 444
An owner-private simulated closeout at Silvergate Health addresses this failure: A Windows software pattern stores the display label in install_path when a command returns both Name and InstallLocation fields. Its independent defect indicator is: The raw command has Name=AtlasAgent and InstallLocation=C:\\Program Files\\Atlas while the mapped path equals AtlasAgent. A reviewed fault must be distinguished from a guessed cause. Which TWO options together provide the treatment and a separate success measure?
- Use a key-aware match on InstallLocation with appropriate escaping and map the captured path explicitly
- A fixture with both fields populates the correct path and does not mistake the application name for a location
- Reconcile the classifier criteria and retain the one verified applicable horizontal pattern
- The command yields the documented raw response within the approved timeout and unchanged extraction produces the expected field
- Reordered table fixtures still identify the same target process and port with the approved mapping
Explanation
Correct Answers
A:Use a key-aware match on InstallLocation with appropriate escaping and map the captured path explicitly. This is the case-specific scoped correction, not a justification to expand the authorized scan or credential scope. In the fictional Silvergate Health scenario, the observed defect is: A Windows software pattern stores the display label in install_path when a command returns both Name and InstallLocation fields. The causal principle is: Field extraction should match a stable named key and validate the value type before mapping a CI attribute. The proposed change must still pass this independent test: A fixture with both fields populates the correct path and does not mistake the application name for a location.
B:A fixture with both fields populates the correct path and does not mistake the application name for a location. This is the independently testable outcome that validates the targeted repair. The authorized change for the fictional Silvergate Health scenario is: Use a key-aware match on InstallLocation with appropriate escaping and map the captured path explicitly. The prior failing observation was: The raw command has Name=AtlasAgent and InstallLocation=C:\\Program Files\\Atlas while the mapped path equals AtlasAgent. A deployment record without this tested outcome does not prove effectiveness.
Incorrect Answers
C:Reconcile the classifier criteria and retain the one verified applicable horizontal pattern. The question instead centers on A Windows software pattern stores the display label in install_path when a command returns both Name and InstallLocation fields; the governing distinction is use a key-aware match on InstallLocation with appropriate escaping and map the captured path explicitly. Check: The raw command has Name=AtlasAgent and InstallLocation=C:\\Program Files\\Atlas while the mapped path equals AtlasAgent. For the response decision in this case, the decisive response is to use a key-aware match on InstallLocation with appropriate escaping and map the captured path explicitly; A fixture with both fields populates the correct path and does not mistake the application name for a location.
D:That alternative is relevant to distinguish command timeout from a malformed pattern expression, but the issue here is A Windows software pattern stores the display label in install_path when a command returns both Name and InstallLocation fields. Use a key-aware match on InstallLocation with appropriate escaping and map the captured path explicitly. Check: The raw command has Name=AtlasAgent and InstallLocation=C:\\Program Files\\Atlas while the mapped path equals AtlasAgent. For the response decision in this case, the decisive response is to use a key-aware match on InstallLocation with appropriate escaping and map the captured path explicitly; A fixture with both fields populates the correct path and does not mistake the application name for a location.
E:Reordered table fixtures still identify the same target process and port with the approved mapping. It concerns select a table row by service identifier rather than its position, not the failure described here: A Windows software pattern stores the display label in install_path when a command returns both Name and InstallLocation fields. Use a key-aware match on InstallLocation with appropriate escaping and map the captured path explicitly.
Question 445
A second pattern designer at Cedarline Media revisits an unresolved finding during read-only asset coverage assessment: A cluster discovery configuration uses a fixed single-node IP even though the active nodes change after failover. A fresh run still shows: The current schedule finds a retired node and misses new nodes identified in the platform's approved cluster inventory. The operator may not broaden credential or subnet permissions to bypass a failed test. Which technical explanation is supported by the Discovery log? Choose ONE.
- Staged discovery rollout should gate expansion on validated reachability, identity quality, and target-owner approval
- The schedule control status describes job lifecycle and does not by itself prove all target identification succeeded
- Classification chooses the target class before its identification and exploration pattern can be selected
- Cluster coverage should use supported authorized membership and address scope rather than assuming one endpoint represents the fleet
Explanation
Correct Answer
D:Cluster coverage should use supported authorized membership and address scope rather than assuming one endpoint represents the fleet. This is the underlying causal Discovery implementation principle for the documented fictional Cedarline Media case. The defect is: A cluster discovery configuration uses a fixed single-node IP even though the active nodes change after failover. The governing mechanism is: Cluster coverage should use supported authorized membership and address scope rather than assuming one endpoint represents the fleet. The supporting measured observation is: The current schedule finds a retired node and misses new nodes identified in the platform's approved cluster inventory. After treatment, the result must be checked: The next discovery finds active nodes and excludes the retired address without leaving the approved cluster boundary.
Incorrect Answers
A:Staged discovery rollout should gate expansion on validated reachability, identity quality, and target-owner approval. The question instead centers on A cluster discovery configuration uses a fixed single-node IP even though the active nodes change after failover; the governing distinction is cluster coverage should use supported authorized membership and address scope rather than assuming one endpoint represents the fleet.
B:That alternative is relevant to avoid assuming completion from a green schedule status, but the issue here is A cluster discovery configuration uses a fixed single-node IP even though the active nodes change after failover. Cluster coverage should use supported authorized membership and address scope rather than assuming one endpoint represents the fleet. Check: The current schedule finds a retired node and misses new nodes identified in the platform's approved cluster inventory.
C:Classification chooses the target class before its identification and exploration pattern can be selected. It concerns distinguish classification failure from identification failure, not the failure described here: A cluster discovery configuration uses a fixed single-node IP even though the active nodes change after failover. Cluster coverage should use supported authorized membership and address scope rather than assuming one endpoint represents the fleet.
Question 446
A second change advisory delegate at Westfield University revisits an unresolved finding during nonproduction Discovery regression suite: A discovery pattern intermittently fails its remote service query under high host load and the team rewrites a regular expression without checking command timing. A fresh run still shows: The failed attempt has a command timeout and no raw response, while the same parse expression succeeds with a captured valid response. Production-affecting actions require an independently verified change approval. What Discovery implementation principle MOST directly explains the cause?
- The debugger distinguishes execution failure from parsing failure by recording elapsed time, raw output, and step outcome
- Extraction logic must be grounded in observed current command output and tested against permitted variants
- Relationship discovery should use observed endpoints or approved configuration semantics and validate ambiguous aliases
- Field extraction should match a stable named key and validate the value type before mapping a CI attribute
Explanation
Correct Answer
A:The debugger distinguishes execution failure from parsing failure by recording elapsed time, raw output, and step outcome. This is the underlying causal Discovery implementation principle for the documented fictional Westfield University case. The defect is: A discovery pattern intermittently fails its remote service query under high host load and the team rewrites a regular expression without checking command timing. The governing mechanism is: The debugger distinguishes execution failure from parsing failure by recording elapsed time, raw output, and step outcome. The supporting measured observation is: The failed attempt has a command timeout and no raw response, while the same parse expression succeeds with a captured valid response. After treatment, the result must be checked: The command yields the documented raw response within the approved timeout and unchanged extraction produces the expected field.
Incorrect Answers
B:Extraction logic must be grounded in observed current command output and tested against permitted variants. The question instead centers on A discovery pattern intermittently fails its remote service query under high host load and the team rewrites a regular expression without checking command timing; the governing distinction is the debugger distinguishes execution failure from parsing failure by recording elapsed time, raw output, and step outcome.
C:That alternative is relevant to use supported connection data instead of inferred hostnames, but the issue here is A discovery pattern intermittently fails its remote service query under high host load and the team rewrites a regular expression without checking command timing. The debugger distinguishes execution failure from parsing failure by recording elapsed time, raw output, and step outcome. Check: The failed attempt has a command timeout and no raw response, while the same parse expression succeeds with a captured valid response.
D:Field extraction should match a stable named key and validate the value type before mapping a CI attribute. It concerns extract a named installation directory from a key-value response, not the failure described here: A discovery pattern intermittently fails its remote service query under high host load and the team rewrites a regular expression without checking command timing. The debugger distinguishes execution failure from parsing failure by recording elapsed time, raw output, and step outcome.
Question 447
The owner of Norwood Retail Cooperative asks for a new risk decision after a prior correction failed to resolve this issue: A multi-region schedule sends an isolated plant subnet through a MID Server that lacks a route to its internal network. The replay still demonstrates: The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone. Only approved target ranges and read-only lab credentials are authorized. Which failure impact should the decision owner prioritize?
- A classifier failure can block an otherwise healthy pattern from running at all
- Overbroad discovery can probe systems outside change authorization and distort coverage data
- Duplicate CIs misstate asset counts and relationship impacts
- Wrong worker placement produces false reachability failures and encourages unnecessary firewall changes
Explanation
Correct Answer
D:Wrong worker placement produces false reachability failures and encourages unnecessary firewall changes. This is the plausible direct consequence of the observed failure for the documented fictional Norwood Retail Cooperative case. The defect is: A multi-region schedule sends an isolated plant subnet through a MID Server that lacks a route to its internal network. The governing mechanism is: Discovery behaviors can select an eligible MID Server by reachable scope, including routing restrictions. The supporting measured observation is: The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone. After treatment, the result must be checked: The chosen MID serves all approved plant addresses while unrelated regions remain outside the behavior.
Incorrect Answers
A:A classifier failure can block an otherwise healthy pattern from running at all. The question instead centers on A multi-region schedule sends an isolated plant subnet through a MID Server that lacks a route to its internal network; the governing distinction is discovery behaviors can select an eligible MID Server by reachable scope, including routing restrictions. Check: The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone.
B:That alternative is relevant to restrict discovery ip range to an approved cidr, but the issue here is A multi-region schedule sends an isolated plant subnet through a MID Server that lacks a route to its internal network. Discovery behaviors can select an eligible MID Server by reachable scope, including routing restrictions. Check: The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone.
C:Duplicate CIs misstate asset counts and relationship impacts. It concerns prevent duplicate server cis when primary identifiers change, not the failure described here: A multi-region schedule sends an isolated plant subnet through a MID Server that lacks a route to its internal network. Discovery behaviors can select an eligible MID Server by reachable scope, including routing restrictions. Check: The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone.
Question 448
The owner of Horizon Public Library asks for a new risk decision after a prior correction failed to resolve this issue: A custom pattern guesses the dependent server from an application configuration label rather than a verified connection endpoint. The replay still demonstrates: The config names db-prod but observed connections go to a separate cluster virtual address. A reviewed fault must be distinguished from a guessed cause. What is the MOST immediate reliability or governance consequence?
- An optional topology error should not erase accurate application inventory data
- An inferred edge can mislead incident impact analysis and service topology
- Changing extraction logic cannot fix a target command that never returns data
- A disabled security control can be misreported as enabled in inventory reports
Explanation
Correct Answer
B:An inferred edge can mislead incident impact analysis and service topology. This is the plausible direct consequence of the observed failure for the documented fictional Horizon Public Library case. The defect is: A custom pattern guesses the dependent server from an application configuration label rather than a verified connection endpoint. The governing mechanism is: Relationship discovery should use observed endpoints or approved configuration semantics and validate ambiguous aliases. The supporting measured observation is: The config names db-prod but observed connections go to a separate cluster virtual address. After treatment, the result must be checked: The resulting topology matches verified endpoint records and does not create a link to the unrelated host.
Incorrect Answers
A:An optional topology error should not erase accurate application inventory data. The question instead centers on A custom pattern guesses the dependent server from an application configuration label rather than a verified connection endpoint; the governing distinction is relationship discovery should use observed endpoints or approved configuration semantics and validate ambiguous aliases. Check: The config names db-prod but observed connections go to a separate cluster virtual address.
C:That alternative is relevant to distinguish command timeout from a malformed pattern expression, but the issue here is A custom pattern guesses the dependent server from an application configuration label rather than a verified connection endpoint. Relationship discovery should use observed endpoints or approved configuration semantics and validate ambiguous aliases. Check: The config names db-prod but observed connections go to a separate cluster virtual address.
D:A disabled security control can be misreported as enabled in inventory reports. It concerns transform command booleans consistently for the target attribute, not the failure described here: A custom pattern guesses the dependent server from an application configuration label rather than a verified connection endpoint. Relationship discovery should use observed endpoints or approved configuration semantics and validate ambiguous aliases.
Question 449
A second Discovery implementation specialist at Clearwater Research Institute revisits an unresolved finding during approval-gated incident investigation: An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field. A fresh run still shows: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer. A reviewed fault must be distinguished from a guessed cause. What Discovery implementation principle MOST directly explains the cause?
- Reconciliation should enforce which authorized data source may update each CI attribute
- CMDB governance can require both technical attributes and service ownership for accountable operations
- CMDB relationship health must be considered alongside the presence and completeness of CI attributes
- A reconciliation authorization denial on an existing matching CI is not a reason to bypass identification and insert a duplicate
Explanation
Correct Answer
A:Reconciliation should enforce which authorized data source may update each CI attribute. This is the underlying causal Discovery implementation principle for the documented fictional Clearwater Research Institute case. The defect is: An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field. The governing mechanism is: Reconciliation should enforce which authorized data source may update each CI attribute. The supporting measured observation is: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer. After treatment, the result must be checked: A controlled Discovery update preserves cost center and still refreshes the approved operating-system version.
Incorrect Answers
B:CMDB governance can require both technical attributes and service ownership for accountable operations. The question instead centers on An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field; the governing distinction is reconciliation should enforce which authorized data source may update each CI attribute. Check: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer.
C:That alternative is relevant to detect an absent business service relationship in cmdb health, but the issue here is An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field. Reconciliation should enforce which authorized data source may update each CI attribute. Check: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer.
D:A reconciliation authorization denial on an existing matching CI is not a reason to bypass identification and insert a duplicate. It concerns separate an unauthorized update attempt from a missing matching ci, not the failure described here: An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field. Reconciliation should enforce which authorized data source may update each CI attribute.
Question 450
An owner-private simulated closeout at Willowbrook Payment Services addresses this failure: A database application CI exists and passes field completeness checks but is not related to its owning service. Its independent defect indicator is: The health report shows required fields populated while the known application-to-service dependency edge is absent. The operator may not broaden credential or subnet permissions to bypass a failed test. Select TWO actions: correct the identified issue and independently prove it is resolved.
- Review class hierarchy and migration behavior with the CI owner, restoring only supported relationships
- The tested payload identifies one expected CI and produces valid relationship mappings without unapproved writes
- Compare the discovered dependency against governed relationship policy and add only the supported typed link
- A controlled Discovery update preserves cost center and still refreshes the approved operating-system version
- A post-run relationship health check finds the correct application-service edge and no unrelated links
Explanation
Correct Answers
C:Compare the discovered dependency against governed relationship policy and add only the supported typed link. This is the case-specific scoped correction, not a justification to expand the authorized scan or credential scope. In the fictional Willowbrook Payment Services scenario, the observed defect is: A database application CI exists and passes field completeness checks but is not related to its owning service. The causal principle is: CMDB relationship health must be considered alongside the presence and completeness of CI attributes. The proposed change must still pass this independent test: A post-run relationship health check finds the correct application-service edge and no unrelated links.
E:A post-run relationship health check finds the correct application-service edge and no unrelated links. This is the independently testable outcome that validates the targeted repair. The authorized change for the fictional Willowbrook Payment Services scenario is: Compare the discovered dependency against governed relationship policy and add only the supported typed link. The prior failing observation was: The health report shows required fields populated while the known application-to-service dependency edge is absent. A deployment record without this tested outcome does not prove effectiveness.
Incorrect Answers
A:That alternative is relevant to preserve relationship evidence when an application ci is reclassified, but the issue here is A database application CI exists and passes field completeness checks but is not related to its owning service. Compare the discovered dependency against governed relationship policy and add only the supported typed link. Check: The health report shows required fields populated while the known application-to-service dependency edge is absent.
B:The tested payload identifies one expected CI and produces valid relationship mappings without unapproved writes. It concerns simulate ire payload changes before production ci updates, not the failure described here: A database application CI exists and passes field completeness checks but is not related to its owning service. Compare the discovered dependency against governed relationship policy and add only the supported typed link.
D:Apply reconciliation priority when Discovery and asset management disagree is a separate consideration. In the stated situation, A database application CI exists and passes field completeness checks but is not related to its owning service. Compare the discovered dependency against governed relationship policy and add only the supported typed link. Check: The health report shows required fields populated while the known application-to-service dependency edge is absent.