CompTIA Cloud+ (CV0-004)OperationsHard
A cloud operations team is investigating intermittent performance issues with a serverless function that processes customer orders. They suspect that the function is occasionally taking too long to execute due to external API calls. To diagnose this, they need to trace the execution path and timing of individual requests through the serverless function and any dependent services. Which logging and monitoring feature would be most beneficial for this task?
- AAlerting rules
- BDistributed tracing
- CMetric dashboards
- DCentralized log aggregation
Show answer & explanationAnswer & explanation
Correct answer: B. Distributed tracing
Distributed tracing allows the team to visualize the end-to-end flow of a single request across multiple services, including serverless functions and external API calls. This provides detailed timing information for each segment, making it ideal for pinpointing performance bottlenecks in complex, distributed architectures.
Why the other options are wrong
- A. Alerting rules notify about issues but don't provide the diagnostic details needed to understand the 'why' of performance bottlenecks.
- C. Metric dashboards show overall trends but don't provide granular, per-request execution details across distributed components.
- D. Centralized log aggregation helps collect all logs but doesn't automatically correlate events across services for a single request's path.
Distributed Tracing
A technique used to monitor and observe requests as they flow through a distributed system, providing end-to-end visibility.
- Assigns a unique trace ID to each request.
- Captures timing and contextual data for each service interaction.
- Essential for debugging microservices and serverless architectures.
Memory trick: Tracing follows the 'Thread' of a request through the 'Web'.