Cyber Monday 2024! 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 4 Question 35 Discussion

Actual exam question for CompTIA's XK0-005 exam
Question #: 35
Topic #: 4
[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:

Royal
4 months ago
Wait, there's a container named 'WEB'? Shouldn't it be all lowercase like 'web'? This exam is already tripping me up.
upvoted 0 times
...
Gladys
4 months ago
Ah, the old 'docker ps WEB -f' trick. Classic move, but not quite what we're looking for here.
upvoted 0 times
Yan
3 months ago
Let me know if that works for you.
upvoted 0 times
...
Crista
3 months ago
D) docker ps WEB -f
upvoted 0 times
...
Arminda
3 months ago
No, I haven't. I'll give that a shot.
upvoted 0 times
...
Allene
3 months ago
Have you tried using 'docker logs WEB'?
upvoted 0 times
...
Olive
3 months ago
C) docker run ---name WEB ---volume/dev/stdout:/var/log/nginx/error.log
upvoted 0 times
...
Laura
3 months ago
B) docker logs WEB
upvoted 0 times
...
Cherry
3 months ago
A) docker-compose inspect WEB
upvoted 0 times
...
...
Yoko
4 months ago
Option A? Really? Inspect the container? That's not going to show the errors, my dude.
upvoted 0 times
Meghan
3 months ago
Yes, that's the correct option to generate the errors.
upvoted 0 times
...
Merilyn
3 months ago
B) docker logs WEB
upvoted 0 times
...
Casandra
3 months ago
No, that won't show the errors.
upvoted 0 times
...
Jovita
3 months ago
A) docker-compose inspect WEB
upvoted 0 times
...
...
Bobbie
4 months ago
I think option B) docker logs WEB is the best choice because it specifically mentions generating errors.
upvoted 0 times
...
Sheridan
4 months ago
I believe option C) docker run ---name WEB ---volume/dev/stdout:/var/log/nginx/error.log could also work.
upvoted 0 times
...
Naomi
4 months ago
I agree with Marilynn, option B) docker logs WEB seems like the right choice.
upvoted 0 times
...
Arlie
4 months ago
I tried option C, but it didn't work. I think the volume path might be wrong.
upvoted 0 times
Vincenza
3 months ago
Make sure to check the logs after running option B.
upvoted 0 times
...
Candida
3 months ago
I agree, option B is the correct one to use.
upvoted 0 times
...
Colby
4 months ago
Try option B, it should show the error logs.
upvoted 0 times
...
Luisa
4 months ago
If option B doesn't work, you can also try option A to inspect the container.
upvoted 0 times
...
Carma
4 months ago
Make sure you are using the correct container name when running the command.
upvoted 0 times
...
Corinne
4 months ago
I agree, option B is the correct command to view the logs.
upvoted 0 times
...
Elinore
4 months ago
Try option B, it should display the error logs.
upvoted 0 times
...
...
Marilynn
5 months ago
I think the administrator should use option B) docker logs WEB.
upvoted 0 times
...
Maile
5 months ago
Option B is the correct answer, 'docker logs WEB' will show the error output of the container.
upvoted 0 times
Maynard
4 months ago
B) docker logs WEB
upvoted 0 times
...
Stefania
4 months 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