Search This Blog

Q11-Q15

Q11. What is Azure API management?
Q12. While doing deployment using ARM template the deployment carried out type is parallel, sequential?
Q13. What is Incremental mode of deployment?
Q14. What is Complete mode of deployment?
Q15. How to confirm that storage account is made before VM in templates?
---------------------------------------------------------------------------------------------------------------------------
Q11. What is Azure API management?

Answer:

Refer: Azure: API Management within this blog. 
---------------------------------------------------------------------------------------------------------------------------
Q12. While doing deployment using ARM template the deployment carried out type is parallel, sequential?

Answer:
Both Parallel and sequential. Resource Manager evaluates the dependencies between resources and deploys them in their dependent order.

By default, ARM template tries to deploy resources in parallel wherever possible. If resources are not dependent, then they will be deployed in parallel. 

For dependent resources for example, a SQL server must exist before attempting to deploy a SQL database. Resource Manager will use the sequential deployment. 
---------------------------------------------------------------------------------------------------------------------------
Q13. What is Incremental mode of deployment?

Answer:
By default, Resource Manager uses the incremental mode. [ADD, UPDATE, NO CHANGE]

ADD - Add as per new defined resources in ARM template
UPDATE - Update as per updated resources in ARM templates
NO CHANGE- Existing resources not defined in the template remain unchanged.

---------------------------------------------------------------------------------------------------------------------------
Q14. What is Complete mode of deployment?

Answer:
In complete mode, [ADD, UPDATE, DELETE]
ADD, UPDATE, DELETE resources to exactly match the ARM template.
DELETE- Existing resources not defined in the template will be deleted. 

---------------------------------------------------------------------------------------------------------------------------
Q15. How to confirm that storage account is made before VM in templates?

Answer:

 By defining dependsOn element or by using reference function. 

More about depends on
there can be other resources that must exist before the resource is deployed. 
For example, a SQL server must exist before attempting to deploy a SQL database. You define this relationship by marking one resource as dependent on the other resource. You define a dependency with the dependsOn element, or by using the reference function.
 
Resource Manager evaluates the dependencies between resources and deploys them in their dependent order. When resources are not dependent on each other, Resource Manager deploys them in parallel. 

You only need to define dependencies for resources that are deployed in the same template.
{
  "type": "Microsoft.Compute/virtualMachineScaleSets",
  "name": "[variables('namingInfix')]",
  "location": "[variables('location')]",
  "apiVersion": "2016-03-30",
  "tags": {
    "displayName": "VMScaleSet"
  },
  "dependsOn": [
    "[variables('loadBalancerName')]",
    "[variables('virtualNetworkName')]",
    "storageLoop",
  ],
  ...
}

---------------------------------------------------------------------------------------------------------------------------

By No comments:

Q6-Q10

Q6. Is it possible to create a Virtual Machine using Azure Resource Manager in a Virtual Network that was created using classic deployment?
Q7. What are virtual machine scale sets (VMSS) in Azure?
Q8. Are data disks supported within Virtual Machine scale sets?
Q9. What is an Availability Set?
Q10: What is the difference between VMSS and Availability Set?
----------------------------------------------------------------------------------------------------------------------------
Q6. Is it possible to create a Virtual Machine using Azure Resource Manager in a Virtual Network that was created using classic deployment?

Answer:
This is not supported. You cannot use Azure Resource Manager to deploy a virtual machine into a virtual network that was created using classic deployment.
----------------------------------------------------------------------------------------------------------------------------
Q7. What are virtual machine scale sets (VMSS) in Azure?

Answer:
VMSS allows you to deploy and manage group of identical, load balanced VM as a single unit. VMSS can be created directly from Azure Portal. 

Key features: 
  • autoscaling: Based on CPU metrics or any other custom metrics identicals VM can be added removed dynamically. 
  • High Avaliablity
  • Support Spots instances for cost effectiveness. 
Use Case:
  • Autoscaling during high traffic periods like festivals. 
  • Scale based on big data workload. If data size is big then increase no of VM doing the data processing. 
  • Use Spot VMs for background tasks like batch order processing, reducing costs
There is NO cost of VMSS itself. 
----------------------------------------------------------------------------------------------------------------------------
Q8. Are data disks supported within Virtual Machine scale sets?

Answer:
Yes. A scale set can define an attached data disk configuration that applies to all VMs in the set. Other options for storing data include:

Azure files (SMB shared drives)
OS drive
Temp drive (local, not backed by Azure Storage)
Azure data service (for example, Azure tables, Azure blobs)
External data service (for example, remote database)
----------------------------------------------------------------------------------------------------------------------------
Q9. What is an Availability Set?

Answer:
An availability set is a logical grouping of VMs that allows Azure to place them in different Fault Domain and Update Domain to make HA and redundancy.  Availability Set is a concept of same Data Center, It's not distributed across Zones. 

Let say we have 6 VMs. 3 VMs for WebTier and 3 Vms for DB. So, to be sure that Web Tier all 3 VMs are down together, we can create an Availability set AV-Web and place all 3 Web VMs into that Availability set. Similarly for DB Tier. Azure will make sure that the VM of same Availability Set are down place in same Fault Domain and Update Domain. 


A Virtual machine can NOT be added to Availability Set once it is created. This discussion is to be taken at the time of VM creation. 

There is NO cost associated with Availability Set. You have to pay only for the VMs that are places in AS. 
----------------------------------------------------------------------------------------------------------------------------
Q10: What is the difference between VMSS and Availability Set?

Answer:

VMSS:
1. Centralized management and configuration of multiple VMs together and keep them identical. 
2. Supports Auto Scaling (Schedule, Metrics, 
3. Supports spinning around Zones also together with Update Domain and Fault Domain. 
4. Azure Load Balancer can also deploy to connect the pool of identical VM we have in VMSS.  Application GW option will be present as well while creating a VMSS. 


Availability Set:
1. Manual configuration of all VMs in AS is required. eg If I want to install a software in VMs I have to do it manually in all VMs. 
2. Manual scaling is required. VM need to add at time of creation into AS. 
3. With in Data Centre. Only around Update Domain and Fault Domain. 
4. LB need to be deployed manually. 

----------------------------------------------------------------------------------------------------------------------------
By No comments:

Q1-Q5

Q1. 
Q2. 
Q3. What is Azure Resource Manager ARM templates?
Q4. Which of the following web applications can be deployed with Azure?
a) ASP.NET,
b) PHP,
c) WCF,
d) All of the mentioned
Q5. Is it possible to call different ARM templates from master ARM templates example calling another template residing somewhere in Azure storage account, or a template residing in github etc?
----------------------------------------------------------------------------------------------------------------------------
Q1.

Answer:

----------------------------------------------------------------------------------------------------------------------------
Q2. 

Answer:

----------------------------------------------------------------------------------------------------------------------------
Q3. What is Azure Resource Manager ARM templates?

Answer:
Azure Resource Manager also known as ARM is used to “manage” infrastructures which involve a no. of azure services. It can be used to deploy, manage and delete all the resources together using a simple JSON script known as ARM Templates. 
>> It uses the concept of IaC (Infrastructure as Code)

  • They contain data in JSON format. 
  • It is automating the deployment process of many components like VM, Storage account, Virtual network, database, database server etc using ARM templates.  you can deploy resources consistently and repeatedly.
  • Various sections of ARM templates-
    • Schema: Defines structure of the template and the API version used. This is usually constant value. It is internally used by Azure to validate the script below based on schema version defined here. This defines features and capabilities avaliable within the template. 
    • Parameters: Enable dynamic input for customization during deployment phase.
    • Variables: Stores values that can be re-used within JSON template. 
    • Resource: used to specify the resource we want to deploy or update in Resource Group
    • apiVersion: apiVersion is tagged to resources. It defines properties and functionalities avaliable for that resource.
    • Functions: These are build in methods that enables you to perform certain operations like string manupulation, conditional logic, resource referring etc. 
    • Output: Values that are returned after deployment. 
----------------------------------------------------------------------------------------------------------------------------
Q4. Which of the following web applications can be deployed with Azure?
a) ASP.NET,
b) PHP,
c) WCF,
d) All of the mentioned

Answer:
D All of the mentioned

----------------------------------------------------------------------------------------------------------------------------
Q5. Is it possible to call different ARM templates from master ARM templates example calling another template residing somewhere in Azure storage account, or a template residing in github etc?

Answer:
Certainly, we can achieve this by Linked Template

Its very common to store the ARM templates at particular location like GitHub or Azure Storage account. We can access the ARM templates with TemplateLink Parameter

To deploy an external template, use the TemplateLink parameter


"properties": {
                "mode": "Incremental",
                "templateLink": {
                    "uri": "https://raw.githubusercontent.com/yourusername/repo/main/linked-template.json",
                    "contentVersion": "1.0.0.0"
                }
----------------------------------------------------------------------------------------------------------------------------
By No comments:
Subscribe to: Comments (Atom)