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.

An Availability Zone in an Azure region is a combination of a fault domain and an update domain. For example, if you create three or more VMs across three zones in an Azure region, your VMs are effectively distributed across three fault domains and three update domains. The Azure platform recognizes this distribution across update domains to make sure that VMs in different zones are not updated at the same time.
Reference link
https://learn.microsoft.com/en-us/training/modules/configure-virtual-machine-availability/5-review-availability-zones

Explanation:
The average CPU percentage is calculated 24 times per day. This is because the exhibit shows the CPU percentage for ASP1 in a 24-hour period, with one data point for each hour. Therefore, the average CPU percentage is calculated once per hour, or 24 times per day1.
ASP1 must be scaled out to optimize CPU usage. This is because the exhibit shows that the CPU percentage for ASP1 is consistently above 80%, which indicates that the app service plan is under high load and needs more instances to handle the traffic. Scaling out means adding more instances to an app service plan, which can improve the performance and availability of the apps hosted on it2. Scaling up means changing the pricing tier of an app service plan, which can increase the resources available for each instance, but not necessarily reduce the CPU usage3.

https://docs.microsoft.com/en-us/azure/role-based-access-control/rbac-and-directory-admin-roles#:~:
text=The%20User%20Access%20Administrator%20role%20enables%20the%20user%20to%20grant,Azure%
20subscriptions%20and%20management%20groups.

When you perform a VM restore using Azure Backup with the "Replace existing" option:
* Azure Backup replaces the existing VM's operating system disk and configuration with what was captured at the time of the backup.
* Data disks added after the backup are not part of the recovery point and are therefore not restored.
Other post-backup changes:
* VM size change: Automatically reverted to the size captured in the backup configuration.
* File addition (Budget.xls): Not present, because only data up to the backup time is restored.
* Password reset: Resetting password does not persist because OS disk from backup overwrites current one.However, when restoring, you can always reset credentials later - but that is expected behavior.
The only configuration that requires manual re-creation after restore is any new data disk added after the backup snapshot.