Exam AZ-400 topic 7 question 63 discussion

Correct, but I found a better explanation: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/caching?view=azure-devops

I think the answer is A (Yes). "Containers provide isolation from the host and allow you to pin specific versions of tools and dependencies. Host jobs require less initial setup and infrastructure to maintain" https://docs.microsoft.com/en-us/azure/devops/pipelines/process/container-phases?view=azure-devops "Containers can be hosted on registries other than Docker Hub. To host an image on Azure Container Registry or another private container registry, add a service connection to the private registry. Then you can reference it in a container spec:" https://docs.microsoft.com/en-us/azure/devops/pipelines/process/container-phases?view=azure-devops#endpoints Since it's possible to build an application inside a container and the container can be generated via a custom image, I'd say that using in the build pipeline a container with an image that already has the js packages installed can be a great solution.

Correct Answer: A. Yes 🔍 Explanation: The scenario describes slow npm package installation (taking ~5 minutes) in an Azure Pipeline building a React.js app. The goal is to reduce the pipeline execution time. ✔ Why this solution works: Container jobs in Azure Pipelines allow you to run steps inside a Docker container. If you define a custom container image that already has the required JavaScript packages (node_modules) preinstalled, the pipeline doesn't need to download them again. This removes repetitive npm install times from the job, speeding up execution significantly. It's especially effective if your package dependencies don’t change frequently. 📝 Additional Notes: While using caching (npm ci with Azure Pipeline caching tasks) is another common approach, a prebuilt container with dependencies baked in is also a valid and efficient solution. It's important to update the container image when dependencies change, which is manageable through CI triggers on package.json changes.

A, Yes this meets the goal, but pipeline caching is the preferred

No for me. Use pipeline caching

Answer is Yes. You can build a Docker container image with these already installed and save it in your registry. Later, you just use it dirrectly.

https://docs.microsoft.com/en-us/azure/devops/pipelines/release/caching?view=azure-devops "Pipeline caching can help reduce build time by allowing the outputs or downloaded dependencies from one run to be reused in later runs, thereby reducing or avoiding the cost to recreate or redownload the same files again. Caching is especially useful in scenarios where the same dependencies are downloaded over and over at the start of each run. This is often a time consuming process involving hundreds or thousands of network calls. Caching can be effective at improving build time provided the time to restore and save the cache is less than the time to produce the output again from scratch. Because of this, caching may not be effective in all scenarios and may actually have a negative impact on build time." Answer is No

answer is B

It's not sure, but I think that YES, it decreases total time.

From Microsoft: Pipeline caching can help reduce build time by allowing the outputs or downloaded dependencies from one run to be reused in later runs, thereby reducing or avoiding the cost to recreate or redownload the same files again. Caching is especially useful in scenarios where the same dependencies are downloaded over and over at the start of each run. This is often a time consuming process involving hundreds or thousands of network calls.

Answer should be correct..container image wont rebuild but skip if nothing change

Wouldn't the docker image meet the goal anyway? maybe is not the best solution but I think it does meet the goal of reducing the time since you could have a base image with the packages. Any idea?