Question 290
A CMDB engineer applied the control: Use a supported connector or governed API-based ingestion to populate that CI type. This was meant to resolve: An enterprise application cannot be discovered by conventional infrastructure scanning but has a supported cloud API inventory. Which result most directly confirms the implementation works?
Explanation
Correct Answer
This observation directly validates the implemented control. Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs. The decisive expected result is: The non-scannable application CI is updated from the authoritative API inventory.
Incorrect Answers
That observation would verify a control associated with: Supported connectors reduce custom upgrade debt and integrate source identification. It does not establish the needed acceptance outcome. The direct evidence is “The non-scannable application CI is updated from the authoritative API inventory”, testing: Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs.
“New cloud metadata appears but protected Discovery-owned fields remain stable” could occur while the stated failure remains unresolved. It tests: The decisive expected result is: New cloud metadata appears but protected Discovery-owned fields remain stable. The required validation instead is “The non-scannable application CI is updated from the authoritative API inventory”, because integration choice should reflect whether reliable source data comes from discovery protocols or product APIs.
This checks a different technical dependency: A reviewed service graph shows appropriate typed edges rather than one indiscriminate relationship. The case requires proof of “The non-scannable application CI is updated from the authoritative API inventory”, which establishes the relevant condition: Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs.