Configuring ACR Native Build with Source-Triggered Task
You have container source code stored in a Git repository. The container registry must automatically build and store a new container image whenever a developer commits code to the Git repository. You must minimize the use of an external build infrastructure. You need to configure Azure Container Registry (ACR) to manage the build process natively and automatically. Which two ACR components should you use? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.
Community Insight
The question tests the specific components of ACR Tasks for automation; the trap is confusing one-off builds (Quick tasks) with automated triggers (Source-triggered tasks).
This question covers Azure Container Registry (ACR) Tasks, specifically how to automate container image builds from Git repositories. It establishes that a source-triggered task combined with a quick task provides the correct native solution.
Many learners select Webhook because it relates to Git events, but Webhooks are external mechanisms or side-effects, not the native ACR component used to manage the build lifecycle itself in this context.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The question requires minimizing external infrastructure while automating builds on commit. In Azure Container Registry (ACR), a 'Task' is the resource that defines the build process. Specifically, you need two components: a Quick task (which defines the actual build instructions, like pulling code and building an image) and a Source-triggered task configuration (which links the repository to the task so it runs automatically upon Git commits). While Microsoft documentation often refers to the whole entity as a 'Task', in the context of exam options distinguishing between types, 'Quick task' represents the build definition and 'Source-triggered task' represents the automation trigger mechanism within the ACR Task feature set.Why the Other Options Are Wrong
Webhook: While ACR uses webhooks internally to listen for events, configuring a generic webhook is not the primary method for managing native ACR builds; it’s more manual and less integrated than using the built-in Task features. Artifact Cache rule: This is related to caching layers during builds to speed them up, not to triggering or defining the build process itself.Community Comment Notes
Community consensus strongly supports option B and D. User divya1986 correctly noted that a Quick Task allows ACR to perform the build natively without external tools. User joc_lefranc clarified that a Quick task is essentially the build definition, whereas the source trigger handles the automation, reinforcing why both are needed for the complete solution described.Official Reference
Exam Strategy
When asked about automating builds in ACR, look for 'Task' related options. If the scenario involves Git integration and automation, prioritize 'Source-triggered' or 'Task' definitions over generic networking terms like 'Webhook'.
Frequently Asked Questions
What is the difference between a Quick task and a Schedule-triggered task?
A Quick task is triggered immediately by events like Git commits or image pushes. A Schedule-triggered task runs at fixed intervals (e.g., daily) regardless of code changes.
Can I use GitHub Actions instead of ACR Tasks?
Yes, but the question specifies minimizing external infrastructure and using ACR natively. ACR Tasks run entirely within Azure, whereas GitHub Actions rely on GitHub's runner infrastructure.