A city wants the 311 classifier image rebuilt and pushed whenever code merges to main. Which ACR capability should they configure?
Select an answer to reveal the explanation.
Short Explanation
When code merges to main, you want an ACR Task to build and push the 311 classifier image automatically, without waiting for a volunteer’s laptop. Source-triggered Tasks keep the registry in sync with the branch your city trusts.
Full Explanation
ACR Tasks can trigger from source-control commits or pushes, such as a merge to main, then build the Dockerfile and push the resulting image to the registry. To rebuild the 311 classifier whenever code merges to main, configure a source-triggered ACR Task. This keeps the registry synchronized with the trusted branch without depending on a volunteer to build locally. A monthly calendar reminder for an operator to build and push the image manually does not provide the speed or consistency of an automated source-triggered build. Manual FTP of binaries into the registry with no Dockerfile does not follow the container build model ACR expects. Rebooting App Service nightly will not recompile an old image: hosts pull images, but do not rebuild them from source on reboot. Exam caveat: Other CI systems can also build on main and push to ACR, but among ACR capabilities, source-triggered Tasks are the registry-native answer. The question asks which ACR capability to configure, not whether other CI systems exist. Practical check: merge a trivial change to main, confirm the ACR Task builds and pushes a new 311 classifier tag, and verify the app platform can pull it. Remove any process that depends on monthly volunteer builds or FTP of binaries.