Bird
Raised Fist0
Dockerdevops~20 mins

Container metrics collection in Docker - Practice Problems & Coding Challenges

Choose your learning style10 modes available
Challenge - 5 Problems
🎖️
Container Metrics Master
Get all challenges correct to earn this badge!
Test your skills under time pressure!
❓ query_result
intermediate
2:00remaining
Retrieve CPU usage percentage for all running containers
You want to see the CPU usage percentage of all running Docker containers using the docker stats command with JSON output. Which command will correctly show this information?
Adocker stats --no-stream --format '{{.CPUPerc}}'
Bdocker stats --format '{{json .}}' | grep CPUPerc
Cdocker stats --no-stream --format '{{.MemUsage}}'
Ddocker stats --no-stream --format '{{json .}}' | jq '.CPUPerc'
Attempts:
2 left
💡 Hint
Use the --format option to select the CPU percentage field directly.
🧠 Conceptual
intermediate
1:30remaining
Understanding memory usage metrics in Docker stats
Which metric from docker stats shows the current memory usage of a container?
AMemUsage
BMemLimit
CCPUPerc
DNetIO
Attempts:
2 left
💡 Hint
Look for the metric that shows how much memory the container is currently using.
📝 Syntax
advanced
2:30remaining
Correct JSON parsing of Docker stats output
You want to parse the JSON output of docker stats --no-stream --format '{{json .}}' to extract container names and CPU usage. Which jq command correctly extracts these fields as a JSON array of objects?
Ajq '. | {Name, CPUPerc}'
Bjq -s '[.[] | {Name: .Name, CPU: .CPUPerc}]'
Cjq '[.Name, .CPUPerc]'
Djq -r '.Name, .CPUPerc'
Attempts:
2 left
💡 Hint
Use the -s option to read multiple JSON objects as an array.
❓ optimization
advanced
2:00remaining
Efficiently monitor memory usage of a specific container
You want to monitor the memory usage of a container named webapp continuously but only want to see the memory usage percentage updated every 2 seconds. Which command achieves this efficiently?
Adocker stats --format '{{.MemPerc}}' --filter name=webapp --no-stream
Bdocker stats --format '{{.MemPerc}}' --filter name=webapp --interval 2
Cdocker stats --format '{{.MemPerc}}' --no-stream --filter name=webapp
Ddocker stats --format '{{.MemPerc}}' --filter name=webapp
Attempts:
2 left
💡 Hint
By default, docker stats updates every second unless --no-stream is used.
🔧 Debug
expert
3:00remaining
Diagnose why Docker stats JSON parsing fails
You run docker stats --no-stream --format '{{json .}}' and pipe it to jq to parse JSON. But jq reports an error: parse error: Invalid numeric literal at line 1, column 10. What is the most likely cause?
AThe <code>jq</code> command is missing the <code>-r</code> flag to read raw input.
BThe <code>docker stats</code> command does not support JSON output, so the output is invalid.
CThe output contains multiple JSON objects without commas or array brackets, so jq expects a single JSON document.
DThe container names contain special characters that break JSON formatting.
Attempts:
2 left
💡 Hint
Consider how multiple JSON objects are output and how jq expects input.

Practice

(1/5)
1. What does the docker stats command primarily show?
easy
A. Logs of a specific container
B. List of all Docker images on the system
C. Live resource usage metrics of running containers
D. Docker daemon configuration settings

Solution

  1. Step 1: Understand the purpose of docker stats

    This command is designed to display live resource usage statistics such as CPU, memory, and network for running containers.
  2. Step 2: Differentiate from other Docker commands

    Other commands like docker images list images, docker logs show logs, and docker info shows daemon info, so they do not match the description.
  3. Final Answer:

    Live resource usage metrics of running containers -> Option C
  4. Quick Check:

    docker stats = live container metrics [OK]
Hint: Remember: stats = live resource usage [OK]
Common Mistakes:
  • Confusing stats with logs
  • Thinking stats shows images
  • Assuming stats shows config
2. Which of the following is the correct syntax to get a single snapshot of container metrics without continuous updates?
easy
A. docker stats --no-stream
B. docker stats --single
C. docker stats --once
D. docker stats --snapshot

Solution

  1. Step 1: Identify the flag for single snapshot

    The --no-stream flag tells docker stats to show metrics once and exit instead of streaming live updates.
  2. Step 2: Verify other options

    Flags like --single, --once, and --snapshot are not valid Docker flags for this command.
  3. Final Answer:

    docker stats --no-stream -> Option A
  4. Quick Check:

    Single snapshot flag = --no-stream [OK]
Hint: Use --no-stream for one-time metrics [OK]
Common Mistakes:
  • Using invalid flags like --single
  • Omitting the flag and expecting single output
  • Confusing with other Docker commands
3. What will be the output of the command docker stats --no-stream my_container if my_container is running?
medium
A. A continuous live stream of resource usage for all containers
B. Logs of my_container
C. An error saying container not found
D. A single snapshot of resource usage metrics for my_container

Solution

  1. Step 1: Understand the command components

    docker stats --no-stream requests a single snapshot, and specifying my_container limits output to that container only.
  2. Step 2: Predict the output

    Since my_container is running, the command outputs one snapshot of its resource usage metrics, not a stream or logs.
  3. Final Answer:

    A single snapshot of resource usage metrics for my_container -> Option D
  4. Quick Check:

    --no-stream + container name = single snapshot for that container [OK]
Hint: Add container name for focused single snapshot [OK]
Common Mistakes:
  • Expecting continuous stream despite --no-stream
  • Confusing stats output with logs
  • Assuming error if container is running
4. You run docker stats --no-stream my_container but get an error: Error: No such container: my_container. What is the most likely cause?
medium
A. You need to add --all flag to see stopped containers
B. The container my_container is not running or does not exist
C. Docker daemon is not running
D. The --no-stream flag is invalid

Solution

  1. Step 1: Analyze the error message

    The error clearly states the container my_container cannot be found, meaning it is either stopped or never created.
  2. Step 2: Check other options

    The --no-stream flag is valid, Docker daemon errors would be different, and docker stats does not support --all to show stopped containers.
  3. Final Answer:

    The container my_container is not running or does not exist -> Option B
  4. Quick Check:

    Error 'No such container' means container missing [OK]
Hint: Check container existence before stats command [OK]
Common Mistakes:
  • Assuming flag is wrong
  • Thinking Docker daemon is down
  • Trying unsupported flags like --all
5. You want to monitor CPU and memory usage of two specific containers named webapp and db with a single snapshot. Which command should you run?
hard
A. docker stats --no-stream webapp db
B. docker stats webapp db --no-stream
C. docker stats --no-stream --filter webapp --filter db
D. docker stats --filter name=webapp,db --no-stream

Solution

  1. Step 1: Understand how to specify multiple containers

    Docker stats accepts container names as arguments separated by spaces to monitor multiple containers.
  2. Step 2: Use the correct flag placement

    The --no-stream flag should come before container names; docker stats --no-stream webapp db places it correctly.
  3. Step 3: Evaluate other options

    docker stats webapp db --no-stream incorrectly places the flag after container names, causing Docker to interpret --no-stream as a container name and resulting in an error. Options C and D use invalid or unsupported --filter syntax for this command.
  4. Final Answer:

    docker stats --no-stream webapp db -> Option A
  5. Quick Check:

    Multiple containers + --no-stream = docker stats --no-stream webapp db [OK]
Hint: List containers after --no-stream for snapshot [OK]
Common Mistakes:
  • Using invalid --filter syntax
  • Placing flags after container names incorrectly
  • Trying to monitor stopped containers
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard