Question 330
While investigating a source-of-truth integration for fictional Willowfield Hospitality, the team reports: A temporary network automation API container is unintentionally published to every host interface with privileged management endpoints exposed. What acceptance check would prove the intended behavior was restored?
Explanation
Correct Answer
Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API. This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. It checks the technical distinction: Compose networks govern container service reachability, while host port publishing determines external exposure. Applied here, the relevant facts are: A temporary network automation API container is unintentionally published to every host interface with privileged management endpoints exposed. The question asks what acceptance check would prove the intended behavior was restored.
Incorrect Answers
That test belongs to another control with this basis: This directly verifies the related correction: Build a representative topology in Cisco Modeling Labs and execute the automation against simulated devices before live release. In the current case, the governing reason is: This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. The direct verification is “Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API”.
This observation would test a different technical dependency: This directly verifies the related correction: Inspect the failed job logs and classify whether build, dependency, test or environment validation failed before making a targeted fix. The current issue is governed by: This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. Its decisive check is “Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API”.
That test belongs to another control with this basis: This directly verifies the related correction: Provision the CML topology reproducibly and wait for all required node readiness conditions before tests begin. In the current case, the governing reason is: This directly verifies the related correction: Use purpose-specific networks and expose only the required listener ports while keeping backend services unexposed. The direct verification is “Network inspection shows the internal service reachable only to authorized app containers and public bindings limited to the approved API”.