Question 490
A follow-up assurance review considers this problem: An application changes from fixed IP infrastructure to autoscaling containers, but monitoring rules are pinned to the former host list. Which outcome best shows the intended improvement?
Explanation
Correct Answer
This is direct test evidence of the control objective in the case: An application changes from fixed IP infrastructure to autoscaling containers, but monitoring rules are pinned to the former host list. It demonstrates that the proposed response, adopt workload identity and dynamic inventory enrichment for telemetry and alert coverage., produces the measurable result newly created test containers appear in monitoring and security events within the ingestion SLA. The observation tests a relevant security outcome rather than an unrelated control or reporting activity.
Incorrect Answers
In the problem “An application changes from fixed IP infrastructure to autoscaling containers, but monitoring rules are pinned to the former host list”, evidence “A crafted malformed login produces an ingestion error and cannot be mistaken for an authenticated success.” is not decisive because it tests “A developer uses a wildcard parser that converts missing security log fields to zero values, making failed imports look like successful logins”; the requested validation is newly created test containers appear in monitoring and security events within the ingestion SLA.
For the issue “An application changes from fixed IP infrastructure to autoscaling containers, but monitoring rules are pinned to the former host list”, measuring “New builds reject the unsupported package and the supported replacement passes functional and security tests.” would validate “An enterprise continues deploying a database library after its vendor ends security support and no maintenance fork exists” instead of the required control effect: newly created test containers appear in monitoring and security events within the ingestion SLA.
In “A branch monitoring appliance records traffic in local time while cloud events are stored in UTC and timeline ordering is inconsistent”, “An incident timeline orders branch and cloud events consistently while preserving original event clocks” is the acceptance signal for “Normalize timestamps with trusted time synchronization and retained original timezone metadata”. The required proof for the selected response “Adopt workload identity and dynamic inventory enrichment for telemetry and alert coverage” is “Newly created test containers appear in monitoring and security events within the ingestion SLA”.