A financial system is receiving complaints about slow responses. The teams want to link each user action from the gateway through the login service and into the core engine. Which solution would help them find how much time each step adds to the overall delay?
Focus on container resource metrics in a monitoring dashboard
Set monthly log rotation on each service to free up storage space
Gather logs once per day from every component for offline review
Tag each user action with an ID and capture its progress across services
Assigning a unique identifier for every incoming request lets you follow the full chain of events across multiple services. This practice, commonly called distributed tracing, shows how long each part of a request takes. Gathering logs only once a day, relying on container resource usage alone, or rotating logs monthly does not surface the full timing breakdown for each user action.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is distributed tracing in system monitoring?
Open an interactive chat with Bash
How are unique identifiers used in distributed tracing?
Open an interactive chat with Bash
Why aren't container metrics alone sufficient for diagnosing delays?
Open an interactive chat with Bash
CompTIA Cloud+ CV0-004
Operations
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
IT & Cybersecurity Package Join Premium for Full Access