Question 590
A research hospital architecture group is working on compliance-controlled network change recommendations. The team found that a test database is deleted when developers run docker compose down --volumes. After remediation, which observation is the strongest evidence that this particular fault is resolved?
Explanation
Correct Answer
This evidence directly verifies the scoped correction, separate data preservation requirements from teardown commands and protect durable volumes, for the underlying issue: the persistent data volume is treated as disposable test runtime state. It should be checked against actual device or pipeline output.
Incorrect Answers
This would confirm recovery from a Compose worker cannot resolve the Redis service when the services are attached to separate isolated networks, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a normal teardown leaves protected persistent data available for restart.
This would confirm recovery from a stopped background worker remains in an otherwise healthy Compose stack, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a normal teardown leaves protected persistent data available for restart.
This would confirm recovery from the automation service starts before the mock network API is ready and exits with connection refused, not necessarily from the reported incident. For the specified issue the relevant confirmation is: a normal teardown leaves protected persistent data available for restart.