Explanation:
\
\
NO
YES
YES

An Availability Set in Azure is a logical grouping of two or more virtual machines that helps ensure your application remains available during planned maintenance events and hardware failures within Azure datacenters.
According to the Microsoft Azure Administrator (AZ-104) study guide and Azure official documentation, Availability Sets protect your VMs from both:
Hardware failures (through fault domains)
Planned maintenance events (through update domains)
A Fault Domain (FD) represents a group of virtual machines that share a common power source and physical network switch. By default, Azure assigns up to three fault domains per region to distribute resources across different racks or hardware clusters.
An Update Domain (UD) represents a group of virtual machines that can be rebooted together during planned maintenance by Microsoft. Azure never updates or reboots two update domains at the same time, ensuring high availability during maintenance operations.
When you have two VMs (VM1 and VM2) running the same application (App1), you should place them in an Availability Set with at least two update domains. This ensures that when Azure performs planned maintenance (updates to host OS or hypervisor), only one update domain is taken offline, while the other remains operational - maintaining service continuity for App1.
By default, an Availability Set provides 5 update domains and 3 fault domains, but the key requirement here is at least two update domains to ensure that maintenance on one host does not impact the entire application.
Therefore, to keep App1 available during planned maintenance of the hardware hosting VM1 and VM2, the Availability Set must include two update domains so that each VM resides in a separate update domain.

Explanation:

Explanation:
Azure Kubernetes Service (AKS) allows administrators to choose between two primary network models for pods and services - Kubenet (Basic) and Azure CNI (Advanced).
In the Basic (Kubenet) networking model - as shown in the image - AKS manages a separate internal network space for pods and services distinct from the virtual network (VNet) of the nodes.
Here's how each CIDR range functions in the network profile:
Pod CIDR (10.244.0.0/16)
This range is used by Kubernetes to assign IP addresses to individual containers (pods) within the cluster.
Each node gets a subset of IPs from this range, and pods on that node use these IPs for internal cluster communication.
These pod IPs are not routable outside the cluster unless Network Address Translation (NAT) is applied.
Service CIDR (10.0.0.0/16)
This subnet is used by Kubernetes to allocate virtual IP addresses for services (e.g., ClusterIP).
These IPs represent internal load balancers that direct traffic to the backend pods through kube-proxy.
The DNS Service IP (10.0.0.10) resides in this range, representing the internal DNS service (kube-dns or CoreDNS).
Docker Bridge CIDR (172.17.0.1/16)
This range is used for the Docker bridge network within each node to manage local container networking before being connected to Kubernetes.
It is not used for pods or services within AKS.
Therefore:
Containers (Pods) # IPs assigned from 10.244.0.0/16 (Pod CIDR).
Services # IPs assigned from 10.0.0.0/16 (Service CIDR).
These CIDRs are critical when integrating AKS clusters with other Azure VNets to avoid overlapping address spaces and ensure seamless connectivity.

According to the Microsoft Azure Administrator (AZ-104) official documentation and study guides, when a virtual machine (VM) in Azure is scheduled for maintenance, you can proactively move the VM to another host to minimize downtime. This process is called a self-service maintenance move.
When Azure schedules maintenance events that could affect the underlying host hardware, customers have the option to move their virtual machines within the same region and subscription to a healthy host by using either the Azure portal, PowerShell, or the Azure CLI. The operation that performs this action is called Redeploy or Maintenance Redeploy.
In this scenario, the proposed action - moving the VM to another subscription from the resource group blade
- does not satisfy the requirement. Moving a VM between subscriptions involves deallocation and redeployment, which does not guarantee that the VM will move to a new host to avoid maintenance. In fact, the VM will remain unavailable during the move process and may need to be reconfigured.
The correct solution to move a VM to another host immediately is to perform a self-service maintenance operation or redeploy the VM. This can be done by selecting the VM in the Azure portal, navigating to Help + support # Maintenance, and choosing "Move to a different host", or by using the Redeploy button under the VM settings.
Thus, moving the VM to another subscription does not meet the maintenance mitigation goal.