To push a container image to Azure Container Registry (ACR) using the Azure CLI, the image must first be tagged with the registry's login server name name. This is a mandatory step in the Docker workflow.
After signing in to the registry using az acr login, the local container image must be tagged in the following format:
< registry-name > .azurecr.io/ < image-name > : < tag >
Azure documentation specifies that Docker determines the target registry based on the image tag. If the image is not tagged with the registry's login server name, Docker will not know where to push the image.
Listing images, deploying container groups, or configuring YAML files are optional or later steps and are not required to push an image to ACR.
Final Answer: A. Tag a container image with the name of the container registry ' s login server

Explanation:

In Azure Monitor, when an alert rule triggers, an alert instance is created. Each alert has a state and a user response status that helps track its lifecycle. The alert state (such as Fired or Resolved) reflects the current condition of the monitored resource, while the user response (such as New, Acknowledged, or Closed) indicates the operator's handling of the alert.
According to the Microsoft Azure Administrator study guide and official Azure Monitor documentation, once an alert has been closed, it enters a terminal state where no further status modifications are permitted - this is by design to preserve operational tracking integrity. Therefore, Alert1, whose user response is "Closed," cannot be changed.
For Alert2, which is in a "New" state, the response can be updated as part of the triage workflow.
Administrators can manually change the alert's user response to Acknowledged (indicating investigation is underway) or to Closed (indicating the issue is resolved).
This structure aligns with best practices outlined in the Azure Monitor alert lifecycle management documentation, ensuring consistent tracking, accountability, and auditability across alert operations.
Final Verified Answers:
* Alert1 (User response): cannot be changed
* Alert2 (User response): can be changed to Acknowledged or Closed #

Explanation:

In Azure App Service, a Web App must be hosted in an App Service Plan (ASP) that meets three key compatibility conditions:
The App Service Plan and the Web App must be in the same region.
The operating system (Windows or Linux) of the App Service Plan must match the Web App type.
The runtime stack of the Web App must be supported on the App Service Plan's OS.
Let's apply these rules to the scenario:
# App Service Plans:
Name
Operating System
Location
ASP1
Windows
West US
ASP2
Windows
Central US
ASP3
Linux
West US
# Web Apps:
Name
Runtime Stack
Location
WebApp1
NET Core 3.0
West US
WebApp2
ASP.NET 4.7
West US
1## WebApp1 (.NET Core 3.0, West US)
Region requirement: Must use an App Service Plan in West US # # ASP1 and ASP3 qualify.
Runtime requirement: .NET Core 3.0 supports both Windows and Linux App Service Plans.
(Microsoft Learn: ".NET Core apps can run on both Windows and Linux App Service plans.")
# Therefore, WebApp1 can use ASP1 (Windows, West US) or ASP3 (Linux, West US).
# Answer: ASP1 and ASP3 only
2## WebApp2 (ASP.NET 4.7, West US)
Region requirement: Must be in West US # # ASP1 and ASP3 qualify.
Runtime requirement: ASP.NET 4.7 is a Windows-only framework; it cannot run on Linux App Service Plans.
(Microsoft Learn: "ASP.NET (non-Core) apps require a Windows-based App Service Plan.")
# Therefore, only ASP1 (Windows, West US) is compatible.
# Answer: ASP1 only
# Final Verified Answers:
Web App
Compatible App Service Plans
WebApp1
ASP1 and ASP3 only
WebApp2
ASP1 only
Microsoft Documentation Extract (Azure App Service):
"App Service plans must be in the same region as the web app."
"Windows App Service plans host ASP.NET, .NET Core, and Node.js apps."
"Linux App Service plans host .NET Core, Node.js, Python, PHP, Java, and custom containers."
".NET Framework (ASP.NET 4.x) applications can only run on Windows-based App Service plans." Hence, the verified and Microsoft-official answer is:
# WebApp1 # ASP1 and ASP3 only
# WebApp2 # ASP1 only

Explanation:
In Microsoft Azure, Azure Policy allows administrators to enforce rules and compliance standards across management groups, subscriptions, resource groups, and individual resources. Policies can be assigned at multiple scopes, and the scope determines which resources the policy affects.
According to Microsoft Azure Governance and Policy documentation, an Azure Policy definition can be assigned to any of the following hierarchical scopes:
Tenant Root Group
Management Group
Subscription
Resource Group
All resources within the assigned scope, including nested resources (e.g., virtual machines within a resource group), inherit the policy. Therefore, a policy can be assigned at any level from the Tenant Root Group down to the Resource Group level, but not directly to individual resources such as a virtual machine (VM).
However, policy exclusions can be applied at any child scope under the assigned level. This means that if Policy1 is assigned at a higher level (for example, Tenant Root Group), you can exclude any lower-level scope, including:
A specific Subscription
A specific Resource Group
A specific Resource (e.g., VM)
Hence, Policy1 can be assigned at the Tenant Root Group, Management Group, Subscription, or Resource Group level, and excluded from lower levels (Subscription, RG1, or individual resources such as VM1).
Summary based on Microsoft Azure Policy design:
Assignable scopes: Tenant Root Group # Management Group # Subscription # Resource Group Excludable scopes: Any child scope within the hierarchy, including specific resources (VMs).
Therefore:
You can assign Policy1 to: Tenant Root Group, ManagementGroup1, Subscription1, and RG1 You can exclude Policy1 from: Subscription1, RG1, and VM1 only

Explanation:

Azure Load Balancers are offered in two SKUs - Basic and Standard - each with distinct capabilities, scalability, and configuration requirements as documented in Microsoft Azure Administrator documentation.
* LB1 - Basic Load Balancer (Basic SKU)The Basic Load Balancer is designed for small-scale, non- production workloads. It has certain limitations compared to the Standard SKU:
* The backend pool of a Basic Load Balancer can only include virtual machines in a single availability set or a single virtual machine scale set.
* This restriction ensures that the Basic Load Balancer maintains consistency and proper failover across VMs sharing the same availability set or scale set.
* It cannot span multiple availability sets or virtual networks.
Therefore, to load balance VMs using a Basic Load Balancer, those VMs must be created in the same availability set or virtual machine scale set.
# Correct Option for LB1: be created in the same availability set or virtual machine scale set.
* LB2 - Standard Load Balancer (Standard SKU)The Standard Load Balancer is designed for production- grade workloads and supports advanced features such as zone redundancy, secure by default configuration, and high scalability.
* It supports backend pools composed of virtual machines from different availability zones (in the same region) and multiple virtual machine scale sets.
* The only requirement is that all backend virtual machines must be connected to the same virtual network.
* Standard Load Balancer also supports both public and internal load balancing and provides richer metrics and diagnostic capabilities.
Therefore, for LB2 (Standard), the virtual machines only need to reside within the same virtual network, regardless of their availability sets or zones.
# Correct Option for LB2: be connected to the same virtual network.
Microsoft Azure Official Extract (summarized):
"For Basic Load Balancer, backend pool VMs must belong to the same availability set or virtual machine scale set. For Standard Load Balancer, backend pool members can be across availability zones and scale sets, but must be connected to the same virtual network." (From Microsoft Azure Administrator Study Guide - Load Balancer Configuration and Comparison; Azure Docs: azure.microsoft.com > Load Balancer SKUs Comparison.) Final Verified Answer:
# LB1: be created in the same availability set or virtual machine scale set
# LB2: be connected to the same virtual network