Question 630
At Cresthaven Digital Commerce, while troubleshooting missing logs, the data center fabric team observes: A remote log collector receives no fabric events despite healthy IP reachability. Which result would establish that the original defect has been corrected?
Explanation
Correct Answer
At Cresthaven Digital Commerce, while troubleshooting missing logs, this result is the relevant closure evidence: A safe test event arrives at the remote collector with expected device identity. It checks the effect of: Validate the approved log forwarding configuration and collector reachability. The underlying issue was: The remote logging destination or source path was not configured correctly.
Incorrect Answers
At Cresthaven Digital Commerce, while troubleshooting missing logs, this option proposes: Unauthorized management probes are limited while permitted transit traffic remains. Using that approach would investigate An engineer puts a management-plane filter on a tenant data port expecting to protect the CPU instead. No evidence for that separate failure is supplied here; the reported case is consistent with: The remote logging destination or source path was not configured correctly.
At Cresthaven Digital Commerce, while troubleshooting missing logs, this option proposes: The incident record distinguishes interface status from last-report time. The alternative focuses on Missing fresh monitoring data was confused with actual interface operational state, not on the stated defect. For this scenario the expected acceptance result would be: A safe test event arrives at the remote collector with expected device identity.
At Cresthaven Digital Commerce, while troubleshooting missing logs, this option proposes: Management restrictions remain in effect while the tenant forwarding defect is resolved. This option assumes the other problem (An operator enables a broad system ACL as a quick workaround to an unrelated data-plane incident) is present. The case instead describes A remote log collector receives no fabric events despite healthy IP reachability, for which the causal issue is The remote logging destination or source path was not configured correctly.