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

Docker Exam DCA Topic 4 Question 76 Discussion

Actual exam question for Docker's DCA exam
Question #: 76
Topic #: 4
[All DCA Questions]

You are troubleshooting a Kubernetes deployment called api, and want to see the events table for this object.

Does this command display it?

Solution: kubectl get deployment api

Show Suggested Answer Hide Answer
Suggested Answer: B

Better caching when building Docker images is not an advantage of multi-stage builds. Multi-stage builds are a feature that allows you to use multiple FROM statements in a single Dockerfile. Each FROM statement begins a new stage of the build, with its own base image and instructions. You can selectively copy artifacts from one stage to another, leaving behind everything you don't want in the final image. The advantages of multi-stage builds are:

Reducing the size of the final image by removing unnecessary dependencies or intermediate files.

Improving the security of the final image by minimizing the attack surface and avoiding leaking secrets.

Simplifying the development workflow by using different tools or environments in different stages. Better caching when building Docker images is not an advantage of multi-stage builds, as it depends on other factors, such as the order and content of the instructions in each stage, the availability and freshness of the base images and intermediate layers, and the use of build arguments or environment variables that may invalidate the cache. Reference: https://docs.docker.com/develop/develop-images/multistage-build/, https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#leverage-build-cache


Contribute your Thoughts:

Giovanna
1 months ago
Wait, you mean I can't just type `kubectl get magic` and see all the events? Dang, Kubernetes is really making me work for it!
upvoted 0 times
Jolene
8 days ago
A) Yes
upvoted 0 times
...
...
Arlette
1 months ago
Ah, classic Kubernetes trickery! The answer is B, of course. You need to use that `describe` command to see the juicy event details.
upvoted 0 times
...
Veronika
1 months ago
Haha, no way! That command is just gonna give you the deployment info, not the events. You gotta be more specific, my friend.
upvoted 0 times
Francesco
1 days ago
B) No
upvoted 0 times
...
Hobert
20 days ago
A) Yes
upvoted 0 times
...
...
Stephanie
2 months ago
Hmm, I don't think that's the right command. Isn't it `kubectl get events --for-resource deployment/api`? That should do the trick.
upvoted 0 times
Dorcas
11 days ago
No
upvoted 0 times
...
Derrick
13 days ago
Yes
upvoted 0 times
...
...
Vanda
2 months ago
No, that command just shows the deployment status, not the events. We need to use `kubectl describe deployment api` to see the events table.
upvoted 0 times
...
Glenn
2 months ago
I believe the command only shows the deployment details, not the events table.
upvoted 0 times
...
Thurman
2 months ago
I'm not sure, but I think it only shows the deployment information.
upvoted 0 times
...
Walton
2 months ago
I think the command should display the events table.
upvoted 0 times
...

Save Cancel