Q #1 Explain the fault domain
that it is a logical
working domain in which the underlying hardware is sharing a common power
source and switch network. This means that when VMs is created the Azure
distributes the VM across the fault domain that limits the potential impact of
hardware failure, power interruption or outages of the network.
Q #2 Explain the Update domain
It is a logical group
that undergoes maintenance by rebooting the system. The system automatically
distributes the created VMs across the updated domain that enables the user to
run any one of the applications while the Azure platform is undergoing
maintenance. The update domain does not work sequentially to the manual
rebooting.
Q #3 What is blob and how many types are there in Azure
Blobs – Blob stands for Binary large objects & Azure Blob storage is
Microsoft's object storage solution for the cloud. Blob storage is optimized
for storing massive amounts of unstructured data. We have 3 types of blobs
·
Block blobs – this is made up of blocks of data that can be
managed individually upto 4.7TB. It stores text and binary data.
·
Append Blobs – this is also made up of block as block blob
but are optimized for append operations. This is ideal for scenarios such as
logging data from virtual machines.
·
Page Blobs – This is for random access files up to 8 TB in
size. Page blobs store virtual hard drive (VHD) files and serve as disks for
Azure virtual machines
Q #4 Difference between AV-Set and AV-Zone
Q #5 What is Service Principle & if you have
contributor access can you create Service Principle.
An Azure
service principal is an identity created for use with applications, hosted
services, and automated tools to access Azure resources. This access is
restricted by the roles assigned to the service principal, giving you control
over which resources can be accessed and at which level. For security reasons,
it's always recommended to use service principals with automated tools rather
than allowing them to log in with a user identity.
Create an
App >> Assing Role (permissions) >> Use App ID & certificates
to give access to the app, hosted service and automated tools.
Contributor
can not create the SP because its about giving access to the application.
Q #6 Are there any restrictions on using IP addresses within these
subnets and what’s the smallest subnet that we can create.
Yes. Azure reserves 5 IP addresses within each
subnet. These are x.x.x.0-x.x.x.3 and the last address of the subnet.
x.x.x.1-x.x.x.3 is reserved in each subnet for Azure services.
- x.x.x.0: Network address
- x.x.x.1: Reserved by Azure for the default gateway
- x.x.x.2, x.x.x.3: Reserved by Azure to map the Azure
DNS IPs to the VNet space
- x.x.x.255: Network broadcast address
The
smallest supported IPv4 subnet is /29, and the largest is /8 (using CIDR subnet
definitions). IPv6 subnets must be exactly /64 in size.
Q #7 How to reset the local admin password of VM
We can do
that from Azure portal from the VM pane under Support and troubleshooting we
have Password reset Option.
Q #8 How to reset the NIC
Q #9 Why we re-deploy the VM & what it does.
If you
have been facing difficulties troubleshooting Remote Desktop (RDP) connection
or application access to Windows-based Azure virtual machine (VM), redeploying
the VM may help. When you redeploy a VM, Azure will shut down the VM, move the
VM to a new node within the Azure infrastructure, and then power it back on,
retaining all your configuration options and associated resources. You will
loose the data on temp disk.
We can
Redeploy from Azure portal under support and troubleshooting.
Q #10 What all you will do, if you are unable to
RDP on Azure VM
1. Reset Remote Desktop configuration.
2. Check Network Security Group rules / Cloud
Services endpoints.
3. Review VM console logs.
4. Reset the NIC for the VM.
5. Check the VM Resource Health.
6. Reset your VM password.
7. Restart your VM.
8. Redeploy your VM.
