Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

CompTIA Exam XK0-005 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:

My
1 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
1 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
1 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
11 months ago
C) docker run --name WEB --volume /dev/stdout:/var/log/nginx/error.log
upvoted 0 times
...
Fabiola
11 months ago
B) docker logs WEB
upvoted 0 times
...
Tracie
11 months ago
A) docker-compose inspect WEB
upvoted 0 times
...
Lettie
12 months ago
C) docker run ---name WEB ---volume/dev/stdout:/var/log/nginx/error.log
upvoted 0 times
...
Charlette
12 months ago
I'm not so sure about that. Maybe we should try option C instead.
upvoted 0 times
...
Catalina
1 years ago
B) docker logs WEB
upvoted 0 times
...
Evan
1 years ago
Yeah, I agree. Option B, docker logs WEB, should show the error output.
upvoted 0 times
...
Emerson
1 years ago
I think option B is the way to go. That's how you can check the logs.
upvoted 0 times
...
Leontine
1 years ago
A) docker-compose inspect WEB
upvoted 0 times
...
...
Joseph
1 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
12 months ago
B) docker logs WEB
upvoted 0 times
...
Dorthy
12 months ago
I had the same issue with option C. It was confusing for me too.
upvoted 0 times
...
Frederick
12 months ago
D) docker ps WEB -f
upvoted 0 times
...
Skye
12 months ago
C) docker run --name WEB --volume /dev/stdout:/var/log/nginx/error.log
upvoted 0 times
...
Carman
12 months ago
B) docker logs WEB
upvoted 0 times
...
Denny
1 years ago
A) docker-compose inspect WEB
upvoted 0 times
...
...
Amina
1 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
1 years ago
D) docker ps WEB -f
upvoted 0 times
...
Brynn
1 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
1 years ago
C) docker run --name WEB --volume /dev/stdout:/var/log/nginx/error.log
upvoted 0 times
...
Krissy
1 years ago
B) docker logs WEB
upvoted 0 times
...
Rodrigo
1 years ago
A) docker-compose inspect WEB
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77