Question 380
The change record states that the team will: Model the required alternative relationship branches correctly in the query canvas. The original defect was: An analyst needs to compare the CI population connected to either Linux or Windows hosts in one graph. Which validation finding should be accepted?
Explanation
Correct Answer
This observation directly validates the implemented control. Graph query logic must represent OR alternatives rather than forcing both branches simultaneously. The decisive expected result is: Both valid host types appear and unrelated CI pairs do not.
Incorrect Answers
This checks a different technical dependency: Multisource records queries enable source-specific inventory reporting. The case requires proof of “Both valid host types appear and unrelated CI pairs do not”, which establishes the relevant condition: Graph query logic must represent OR alternatives rather than forcing both branches simultaneously.
“The test database change lists its genuinely dependent services for review” could occur while the stated failure remains unresolved. It tests: Linked CI dependencies reveal potential blast radius before infrastructure changes. The required validation instead is “Both valid host types appear and unrelated CI pairs do not”, because graph query logic must represent OR alternatives rather than forcing both branches simultaneously.
This checks a different technical dependency: Missing recent source activity can signal integration failure even when other feeds maintain the CI. The case requires proof of “Both valid host types appear and unrelated CI pairs do not”, which establishes the relevant condition: Graph query logic must represent OR alternatives rather than forcing both branches simultaneously.