Which end-to-end visibility challenge is identified in the material?

Which end-to-end visibility challenge is identified in the material?

• A. Lack of End to End Visibility
• B. Excess end-to-end visibility
• C. Too much automation
• D. Redundant dashboards

Answer: (A)

End-to-end visibility is about seeing a transaction or issue across the entire stack—from data source to end user—across systems, apps, and infrastructure. The material presents the challenge as a lack of that unified view. When data lives in silos or isn’t connected, you miss critical links, making it hard to trace a request end-to-end, correlate signals from logs, metrics, and traces, and quickly pinpoint root causes. That lack directly leads to blind spots and slower incident response, which is why this option is the best fit. The other ideas describe different problems: having too much visibility can create noise rather than help you see the whole picture; excessive automation is a separate concern about automation levels; redundant dashboards indicate duplication and inefficiency, not the absence of a comprehensive, connected view.

End-to-end visibility is about seeing a transaction or issue across the entire stack—from data source to end user—across systems, apps, and infrastructure. The material presents the challenge as a lack of that unified view. When data lives in silos or isn’t connected, you miss critical links, making it hard to trace a request end-to-end, correlate signals from logs, metrics, and traces, and quickly pinpoint root causes. That lack directly leads to blind spots and slower incident response, which is why this option is the best fit.

The other ideas describe different problems: having too much visibility can create noise rather than help you see the whole picture; excessive automation is a separate concern about automation levels; redundant dashboards indicate duplication and inefficiency, not the absence of a comprehensive, connected view.