AZ-104 Exam Dumps - Microsoft Azure Administrator

✅ ACR Tasks: ContReg1 and ContReg2 only

✅ Private endpoints: ContReg1 only

Azure Container Registry (ACR) provides multiple service tiers (SKUs)—Basic, Standard, and Premium—each offering different capabilities for scalability, performance, and features. These tiers determine what functionalities are available, including ACR Tasks and Private Link (Private Endpoints) integration.

Here’s how each tier differs according to Microsoft Azure Administrator documentation (AZ-104 Exam Study Guide and Azure Docs):

Feature

Basic

Standard

Premium

ACR Tasks (Build automation, image building, and updating)

✅ Supported

✅ Supported

✅ Supported

Private Link / Private Endpoints (Private access via Azure backbone)

❌ Not Supported

❌ Not Supported

✅ Supported

Geo-replication

❌ Not Supported

❌ Not Supported

✅ Supported

Content trust and RBAC integration

✅ Supported

✅ Supported

✅ Supported

Analysis:

ACR Tasks:

ACR Tasks allow you to automate image builds and updates when base images or application code changes.

Supported in Standard and Premium tiers (as per Microsoft Docs: “ACR Tasks are available in Standard and Premium service tiers.”).

Therefore, ContReg1 (Premium) and ContReg2 (Standard) support ACR Tasks.

ContReg3 (Basic) does not support advanced tasks automation at scale.

✅ Answer: ContReg1 and ContReg2 only

Private Endpoints:

Private Link (Private Endpoints) enables private network connectivity to the ACR from a virtual network.

According to Azure documentation:

“Private Link for Azure Container Registry is supported only in the Premium service tier.”

This ensures that access to the registry occurs via Azure’s backbone, preventing exposure to the public internet.

✅ Answer: ContReg1 only (Premium)

Verified Microsoft Documentation Extract:

From Microsoft Learn: Azure Container Registry service tiers overview:

“The Premium tier provides advanced capabilities such as geo-replication, content trust, customer-managed keys, and Private Link support.”

“ACR Tasks is available in both Standard and Premium tiers for continuous integration workflows and automated image building.”

When an Azure virtual machine is redeployed, Azure moves the VM to a new physical host. During this process, the OS disk and any attached data disks are preserved, but the temporary disk is not. On Windows VMs deployed with default settings, drive D: is the temporary disk, backed by local storage on the host. Microsoft documentation states that the temporary disk is non-persistent and data on it can be lost during maintenance, redeploy, or deallocation events.

Files created on drive C: reside on the OS disk, which is persistent and retained across redeployments. User profile and system settings such as screen saver timeout and desktop background are stored on the OS disk and therefore remain intact after redeploy. Consequently, the only change that will be lost is data written to drive D:.

Box 1: A Recovery Services vault

A Recovery Services vault is an entity that stores all the backups and recovery points you create over time.

Box 2: A backup policy

What happens when I change my backup policy?

When a new policy is applied, schedule and retention of the new policy is followed.

1. View template from deployment history

Go to the resource group for your new resource group. Notice that the portal shows the result of the last deployment. Select this link.

2. You see a history of deployments for the group. In your case, the portal probably lists only one deployment. Select this deployment.

The portal displays a summary of the deployment. The summary includes the status of the deployment and its operations and the values that you provided for parameters. To see the template that you used for the deployment, select View template.

App1 present in RG1 and in RG1 there is no lock available. So you can move App1 to other resource groups, RG2, RG3, RG4.

Note:

App Service resources can only be moved from the resource group in which they were originally created. If an App Service resource is no longer in its original resource group, move it back to its original resource group.