Q: 3
Refer to the exhibit. A developer wants to automatically deploy infrastructure for a containerized application. A .gitlab-ci.yml file must describe a pipeline that builds a container based on a supplied Dockerfile and executes an Ansible playbook on the configured container. What must be added where the code S missing to complete the script?
A)
B)
C)
D) 
Options
Discussion
I could see a case for C if the container didn't need to be reused by another pipeline job, but with that registry pull in stage two, I'd go D.
Definitely D
Its D here because docker push is required to get the built image from the runner to the GitLab Container Registry. Without that, the next pipeline stage can't pull the updated container image by tag. Pretty sure that's what they're testing for, since B and C don't get it into the registry at all. If there were extra steps about external/private registries, might be different-but for this case D lines up.
C here. In a lot of official guide examples, you just run the container after building without pushing to a registry so it matches C more closely. If you see similar questions on practice labs, the pattern is usually local execution for one-off jobs. I think that's why C fits but check your study labs to confirm.
C/D? Most examples in the official guide just run the container after build (like C), but since the exam sometimes pushes you to remember registry usage I might pick D. Check labs or GitLab docs if unsure, though.
Maybe C here. Looks like it just runs the container after building, which covers a lot of basic CI setups. Not sure if they really need to push to the registry unless there’s a later reuse step. Could be missing something though, anyone else see a catch?
Option C looks like what most practice pipelines use, and D might be a trap here.
C or D. Both look close, but my practice labs usually have a
docker push in the pipeline for later stages to pull the image. If anyone’s checked the official guide, let me know if I missed a detail.Feels like D, since docker push is needed for the next stage to pull from the registry.
So tired of these registry pipeline mixups. Probably C, diagrams can be misleading and C looks like it could work.
Be respectful. No spam.