New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

CompTIA XK0-005 Exam - Topic 1 Question 30 Discussion

Actual exam question for CompTIA's XK0-005 exam
Question #: 30
Topic #: 1
[All XK0-005 Questions]

An administrator is running a web server in a container named web, but none of the error output is not showing. Which of the following should the administrator use to generate the errors on the container?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Tamar
3 months ago
C looks complicated, why not just use B?
upvoted 0 times
...
Myra
3 months ago
A is just for inspecting, not for logs.
upvoted 0 times
...
Aaron
3 months ago
Wait, can you really use docker logs for that? Seems too simple.
upvoted 0 times
...
Lemuel
4 months ago
Yeah, B makes the most sense for viewing logs.
upvoted 0 times
...
Aja
4 months ago
I think it's B, docker logs WEB.
upvoted 0 times
...
Lashawn
4 months ago
I remember that `docker ps` shows running containers, but I don't think it would help with error output. It seems like `docker logs` is the best choice here.
upvoted 0 times
...
Serina
4 months ago
I’m a bit confused about the options. I feel like `docker-compose inspect` just gives details about the configuration, not the logs.
upvoted 0 times
...
Raul
4 months ago
I practiced a similar question where we had to check logs for a container, and I think `docker logs WEB` was the right answer there too.
upvoted 0 times
...
Lai
5 months ago
I think I remember that `docker logs` is used to view the output from a container, but I'm not entirely sure if it shows errors specifically.
upvoted 0 times
...
Stanford
5 months ago
I'm not totally confident, but I'm leaning towards option B. That seems like the most straightforward way to view the container's logs.
upvoted 0 times
...
Sharen
5 months ago
Ah, I've seen this type of issue before. I'm pretty sure the answer is B, using the docker logs command.
upvoted 0 times
...
Carin
5 months ago
Wait, I'm a bit confused. I'm not sure which of these commands would actually show the error output.
upvoted 0 times
...
Gaynell
5 months ago
Okay, I think I know the answer here. Let me double-check the options.
upvoted 0 times
...
Peggie
5 months ago
Hmm, this looks like a tricky one. I'll need to think through the options carefully.
upvoted 0 times
...
Chi
5 months ago
I think forming an alliance with a local supplier is the way to go. It would give Mitch access to more resources and potentially better pricing, which could really help grow the business. The other options seem a bit risky or complex.
upvoted 0 times
...
Mariann
5 months ago
I remember discussing how transparency in blockchain can build trust among users, so I'm leaning towards option A.
upvoted 0 times
...
Jeff
5 months ago
I think we learned that when you stick with the same instance type, some configurations remain static. Maybe it's about the memory size?
upvoted 0 times
...
Stefany
5 months ago
This seems pretty straightforward. I think the answer is D - starting a timer when the request is made and stopping it when the result is received.
upvoted 0 times
...
My
2 years ago
I once tried to use option A to debug a container, and it just made me feel like I was playing a game of 'Where's Waldo?' with the error messages. Stick to the classics, people!
upvoted 0 times
...
Helaine
2 years ago
Ah, the good old docker logs command. It's like a magical window into the container's soul, where all the secrets and mysteries are revealed. Option B is the way to go, folks!
upvoted 0 times
...
Afton
2 years ago
Haha, option D? Really? That's like asking for the weather forecast when you want to see the error messages. Nice try, but I'm not falling for that one!
upvoted 0 times
Joaquin
2 years ago
C) docker run --name WEB --volume /dev/stdout:/var/log/nginx/error.log
upvoted 0 times
...
Fabiola
2 years ago
B) docker logs WEB
upvoted 0 times
...
Tracie
2 years ago
A) docker-compose inspect WEB
upvoted 0 times
...
Lettie
2 years ago
C) docker run ---name WEB ---volume/dev/stdout:/var/log/nginx/error.log
upvoted 0 times
...
Charlette
2 years ago
I'm not so sure about that. Maybe we should try option C instead.
upvoted 0 times
...
Catalina
2 years ago
B) docker logs WEB
upvoted 0 times
...
Evan
2 years ago
Yeah, I agree. Option B, docker logs WEB, should show the error output.
upvoted 0 times
...
Emerson
2 years ago
I think option B is the way to go. That's how you can check the logs.
upvoted 0 times
...
Leontine
2 years ago
A) docker-compose inspect WEB
upvoted 0 times
...
...
Joseph
2 years ago
I tried option C before, but it didn't work for me. The syntax is a bit confusing, and I'm not sure if it's the right way to handle logging in a container.
upvoted 0 times
Lynette
2 years ago
B) docker logs WEB
upvoted 0 times
...
Dorthy
2 years ago
I had the same issue with option C. It was confusing for me too.
upvoted 0 times
...
Frederick
2 years ago
D) docker ps WEB -f
upvoted 0 times
...
Skye
2 years ago
C) docker run --name WEB --volume /dev/stdout:/var/log/nginx/error.log
upvoted 0 times
...
Carman
2 years ago
B) docker logs WEB
upvoted 0 times
...
Denny
2 years ago
A) docker-compose inspect WEB
upvoted 0 times
...
...
Amina
2 years ago
Option B seems like the logical choice to view the container's logs. Why would you need to inspect the container when you can just view the logs directly?
upvoted 0 times
Jennifer
2 years ago
D) docker ps WEB -f
upvoted 0 times
...
Brynn
2 years ago
Option B seems like the logical choice to view the container's logs. Why would you need to inspect the container when you can just view the logs directly?
upvoted 0 times
...
Elke
2 years ago
C) docker run --name WEB --volume /dev/stdout:/var/log/nginx/error.log
upvoted 0 times
...
Krissy
2 years ago
B) docker logs WEB
upvoted 0 times
...
Rodrigo
2 years ago
A) docker-compose inspect WEB
upvoted 0 times
...
...

Save Cancel