At a bank, a container that handled one payment was gone before the nightly host scan, and its overlay traffic never appeared on the physical switch. What visibility problem does that show?
Select an answer to reveal the explanation.
Short Explanation
A stall that folds before the night round, on a floor the paper map does not draw, leaves your notebook empty. The bank container that vanished, on an overlay the physical switch never saw, is that visibility gap. A mail filter, a failed login, or a denied inbound scan explains a different miss.
Full Explanation
Containers can exist for one transaction and exit before a nightly host scan ever logs in. Traffic between them can stay on a virtual switch or overlay and never hairpin onto the physical switch a span or a scan is watching. Both facts are one visibility problem. Short-lived container workloads on an overlay that does not show up on the physical switch. Mail controls do not explain a missing workload. A missing email filter on the customer mailbox that sends payment notices for the bank would affect messages, not a container that exited before the scan. An authentication failure is a user event. A user who failed multifactor authentication at the payment console and then lost that session explains a locked console session, not an overlay the physical network never saw. A logged deny is evidence of a different shape. A perimeter firewall deny recorded for an inbound scan of the bank payment subnet would appear as a deny of a scan, whereas this container disappeared and its overlay never reached that firewall's path. Exam caveat: container and virtual visibility fails even when the perimeter firewall is healthy, because the workload is brief and the path is virtual. Operational check: compare the container's start and exit times with the scan window, and confirm the overlay bridge is not mirrored to the physical switch you are watching.