Question 660
At Skyline Digital Commerce, while troubleshooting missing logs, the data center fabric team observes: A traffic capture collects sensitive unrelated tenant packets during troubleshooting. What repeatable acceptance check would reduce recurrence?
Explanation
Correct Answer
At Skyline Digital Commerce, while troubleshooting missing logs, use this repeatable control: Require scope approval and retention review for packet captures. Its scope is the problem (The capture filter is too broad for the authorized incident scope), not an unrelated network maintenance procedure.
Incorrect Answers
At Skyline Digital Commerce, while troubleshooting missing logs, this option proposes: Expose freshness and device state as distinct monitoring signals. The option describes a different failure mode: A dashboard treats a stale telemetry timestamp as proof that a link is down. It would address Missing fresh monitoring data was confused with actual interface operational state, but here the case reports A traffic capture collects sensitive unrelated tenant packets during troubleshooting. The current required evidence is: A safe test shows only scoped packets are collected and sensitive unrelated samples are excluded.
At Skyline Digital Commerce, while troubleshooting missing logs, this option proposes: Check remote log delivery independently from network reachability. That choice would be more relevant when this different symptom occurs: A remote log collector receives no fabric events despite healthy IP reachability. The present scenario instead points to: The capture filter is too broad for the authorized incident scope. The correct resolution has its own verification outcome: A safe test shows only scoped packets are collected and sensitive unrelated samples are excluded.
At Skyline Digital Commerce, while troubleshooting missing logs, this option proposes: Retain state and log context together for interface incidents. This is a valid category of fabric maintenance for another scenario (An engineer cannot correlate a fabric alert to a specific interface), not the targeted action for Skyline Digital Commerce. The distinction is the actual cause: The capture filter is too broad for the authorized incident scope.