Azure: 2020

Q31-Q35

Q31. What is Azure service bus?

Q32. What are Azure Durable functions?

Q33. What are azure orchestrator functions?

Q34. What are the various Azure services you have used in your project?

Q35. What is the difference between triggers and binders in azure functions?

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

Q31. What is Azure service bus?

Answer:

Azure Service bus is of two types

1) Azure Service bus Message Queues and

2) Azure Service Bus Topics

Message Queues:

>> Supports FiFo, Duplication detection, Long Pooling service

Topics:

>> Pub/Sub model

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

Q32. What are Azure Durable functions?

Answer:

Azure Durable Functions is an extension of Azure Functions that allows you to write stateful functions in a serverless compute environment. This means you can define workflows that maintain their state even after the function execution is paused or restarted

Key Features:

1. Orchestrator Functions: These functions define the workflows using code. They can call other functions, wait for their results, and manage the state of the workflows. Can be used for Function Chaining

2. Stateful Entities: These are functions that manage state explicitly, allowing you to build applications that require stateful interactions

3. Patterns: Supports various application patterns such as function chaining, fan-out/fan-in, async HTTP APIs, monitoring, human interaction, and aggregators1

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

Q33. What are azure orchestrator functions?

Answer:

Azure Durable Functions.

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

Q34. What are the various Azure services you have used in your project?

Answer:

Now, during an interview, you can answer with this neat flow:

Hosting/Compute → Where apps live.
API Management & Integration Services → How apps talk to each other.
Networking/Delivery → How users reach apps.
Storage → Where data lives.
Security → How apps & users are secured.
Monitoring → How we track and improve.

1. Application Hosting & Compute

App Service

Azure Web Apps – Hosting web applications.
Azure Logic Apps – Workflow automation and integration.
Azure Functions – Serverless compute for event-driven task

IAAS Solutions

ARM Templates – Infrastructure as code.
Docker Images – Containerized application packaging.
ACI, Azure Container Instances – Lightweight container hosting.
ACR, Azure Container Registry – Container image storage and management.
AKS, Azure Kubernetes services.

2. API Management & Integration Services.

API Management

API Gateways – Authentication, policies, rate limiting, throttling for APIs.

Integration Services

Azure Event Grid – Event routing service.
Azure Event Hubs – Big data streaming platform. Event Ingestion service.
Azure Service Bus – Enterprise messaging with topics and queues.
Azure Queue Storage – Simple queue-based messaging.
Azure Notification Hubs – Push notifications to mobile devices.

3. Networking & Deliver
Azure CDN (Content Delivery Network) – Caching and global content delivery.
WAF
Azure Redis Cache – In-memory data store for fast access.
Azure Front Door – Global load balancing and web application firewall.

4.     Storage Solutions
o   Disk Storage – Managed disks for VMs.
o   Cosmos DB – Globally distributed NoSQL database.
·       Azure Storage
o   Blob Storage (unstructured data, images, video)
o   File Storage (SMB-based file shares)
o   Table Storage (key-value store)
o   Queue Storage (simple message queue)

5.     Security
o   AAD, Entra ID, Azure Active Directory (SSO, MFA)
o   OAuth2 Authentication
o   Shared Access Signature (SAS), limited access to storage blob etc
o   RBAC (Role-Based Access Control)
o   Key Vault – Secure storage for secrets, keys, and certificates.
o   Azure Managed Identities.

6. Monitoring & Diagnostics

o Application Insights – Application performance monitoring.
o Azure Monitor – Infrastructure and resource monitoring.

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

Q35. What is the difference between triggers and binders in azure functions?

Answer:

In Azure Functions, triggers and bindings are concepts that help define how functions are invoked and how they interact with other services.

Triggers:

- Defines how a function is invoked. HTTP triggers, Timer triggers, Blob Storage triggers, Queue Storage triggers, Event Grid triggers

Bindings:

- They can be used to pass data into the function (input bindings) or to send data from the function (output bindings).

- Example: An input binding can read data from a storage account and pass it to the function. An output binding can write data to a storage account after the function processes it.

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

Q26-Q30

Q26. What is Docker? How it is different from container?

Q27. What is azure Kubernetes Service, AKS?

Q28. What are Cluster and Nodes in microservices?

Q29. What are the different types of storages options provided by azure?

Q30. What types of Messaging options we have azure?

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

Q26. What is Docker? How it is different from container?

Answer:

Docker is a platform that allows developers to build, deploy, and manage applications inside containers. It provides a consistent environment for applications, ensuring they run the same way regardless of where they are deployed.

Containers, on the other hand, are lightweight, standalone, and executable software packages that include everything needed to run a piece of software, such as code, runtime, system tools, libraries, and settings. Containers virtualize the operating system, allowing multiple containers to run on the same machine while sharing the OS kernel

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

Q27. What is azure Kubernetes Service, AKS?

Answer:

Azure Kubernetes Service (AKS) is a managed Kubernetes service provided by Microsoft Azure. It simplifies the deployment, management, and scaling of containerized applications using Kubernetes

AKS reduced the complexity and operation overhead of health monitoring, maintenance, scaling for you in comparison to plain old K8s.

AKS integrate seamlessly with other Azure services and devops tool. K8 is more time taking activity.

AKS has built in security features while K8 its our duty to keep security intact.

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

Q28. What are Cluster and Nodes in microservices?

Answer:

Cluster: A network-connected set of virtual or physical machines into which your microservices are deployed and managed. Clusters can scale to thousands of machines.

Node: A machine or VM that's part of a cluster is called a node. Each node is assigned a node name.

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

Q29. What are the different types of storages options provided by azure?

Answer:

Azure storage include - Blob, table, files and queues and VM Disks

Blog Storage is basically storage for unstructured data that can include pictures, videos, music files, documents, raw data, and log data

Table storage, as the name indicates, is preferred for tabular data, which is ideal for key-value NoSQL data storage. Table Storage is massively scalable and extremely easy to use. Like other NoSQL data stores, it is schema-less and accessed via a REST API

Queues: You can store large numbers of messages to be shared between independent components of applications and communicated asynchronously via HTTP or HTTPS

https://cloudacademy.com/blog/azure-storage-service-overview/

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

Q30. What types of Messaging options we have azure?

Answer:

Azure has multiple types of messaging services.

Azure Service Bus

Azure Service Bus Queue - Point to point communication. One receiver
Azure Service Bus Topics and Subscription

Azure Storage Queues: used for large number of messages where message size is big.
Azure Event Grid: Event driven architecture. Real time event processing.
Azure Event Hub: Ingest millions of events per sec. Used in IOT devices. Streaming of events. Save streamed data to Azure Data Lake.

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

Q21-Q25

Q21. Difference between Azure Functions and Azure Logical apps?

Q22. What is WebApp, API App and Mobile App in Azure? are they different from App services?

Q23.

Q24. Difference between Azure Functions and Azure app service WebJobs as both are code first approach?

Q25. How you call azure functions from your angular code?

=======================================================================

Q21. Difference between Azure Functions and Azure Logical apps?

Answer:

Both are PAAS.

Azure Functions:

1. Azure functions are serverless compute service design to run small piece of code. It's ideal for building microservices, APIs. They are good in event handling tasks.

2. Azure functions are code first approach.

3. Azure functions can run in various environments like self-managed servers, locally, azure, containers.

4. Automatically scales based on demand.

5. Ideal for real time processing, background tasks and lightweights APIs.

6. You have two options qua pricing. You can opt for a fixed cost of an App Service Plan. In that option you reserve compute power on which you can run Azure Functions, but also Web, Mobile and API Apps. The second option is completely serverless, with a consumption plan based on resource consumption (memory/s) and number of executions

Azure Logical Apps:

1. Azure LA are workflow automation service helps to integrate different apps, data, systems and services. It is designed to do orchestrating difficult workflows with minimal code.

2. L Apps are design first approach. u can do in Visual studio with designer plugin.

3. L Apps can be run only in Azure.

4. Autoscales

5. Best for business process automation, integrating disparate systems, and orchestrating complex workflows.

=======================================================================

Q22. What is WebApp, API App and Mobile App in Azure? Are they different from App Services?

Answer:

App Services now replaces all Mobile, Api and Web Apps flavors as a single app framework with all the functionality rolled over to make things more accessible across application types. Currently all of Web, Mobile and Api Apps are collectively called App Services under Azure App Service Plan. We still offer customer to be able to create a Mobile App and a Web App in the gallery but that is basically resolve into an App Service App.

Microsoft Azure App Services are a platform as a service (PaaS) offering

various App services available

Web App - ideal for web applications, CMS, e commerce websites.
API App - Ideal for hosting APIs that can be consumed by Web Apps.
Mobile App - Ideal for work like Authentication, data sync and push notifications.
Logic App - Workflows.
Functions - Code first.
Web jobs - backend Jobs hosted within same server where WebApp is hosted. It can be found with in settings section of newly created WebApp.

=======================================================================

Q23.

Answer:

=======================================================================

Q24. Difference between Azure Functions and Azure app service webjobs as both are code first approach?

Answer:

Both are built on Azure app service.

Both supports Code first approach.

Both can integrate with application insight.

Both Supports multiple languages like C#, JavaScript, Python, Java

Azure Functions

Two plans 1) Consumption plan/ Pay-per-use plan and 2) App Service plan
In-browser development is supported.
Integration with Logical Apps

Azure app service WebJobs

Can be paid only as a part of App service plan.
In-browser development is Not supported.
No Integration with Logical Apps

=======================================================================

Q25. How you call azure functions from your angular code?

Answer:

It would be Http trigger function and from angular service layer you have to make simple httppost request where functionURI is the URI to the azure function.

this.http.post(functionURI, input, { headers: headers } ).subscribe(data => {
      console.log(data);
    });

Here is my simple HTTP trigger function using Javascript:

module.exports = function (context, req) {

context.log('JavaScript HTTP trigger function processed a request.');

if (req.query.name || (req.body && req.body.name)) {

context.res = {

// status: 200, /* Defaults to 200 */

body: "Hello " + (req.query.name || req.body.name)

};

} else {

context.res = {

status: 400,

body: "Please pass a name on the query string or in the request body"

};

}

context.done();

};

=======================================================================

My Other Blogs

Angular 9 https://himanshugoel2018angular.blogspot.com/
API https://himanshugoel2018webapi.blogspot.com/
AWS https://himanshugoel2018aws.blogspot.com
Azure DevOps https://himanshugoel2018azuredevops.blogspot.com/
Azure http://himanshugoel2018azure.blogspot.com/
Coding Questions https://himanshugoel2018coding.blogspot.com/
C-Sharp https://himanshugoel2018csharp.blogspot.com/
dotnet Core http://himanshugoel2018core.blogspot.com/
HTML + CSS https://himanshugoel2018css.blogspot.com/
JavaScript ES6 https://himanshugoel2018javascript.blogspot.com/
Learning Habits https://himanshugoel2018learninghabit.blogspot.com/
Learning Topics https://himanshugoel2018learningtopics.blogspot.com/
Managerial https://himanshugoel2018managerial.blogspot.com/
Microservices https://himanshugoel2018microservices.blogspot.com/
Mongo DB https://himanshugoel2018mongodb.blogspot.com/
MVC http://himanshugoel2018mvc.blogspot.com/
Node JS https://himanshugoel2018nodejs.blogspot.com/
Softmind http://softmindit.blogspot.com/
SQL https://himanshugoel2018sql.blogspot.com/
System Architect https://himanshugoel2018systemarchitect.blogspot.com/

Q16-Q20

Q16. What is Azure Web Jobs? How they are different from Azure Functions?

Q17. What is Tenant ID, Client ID and Client secret key in Azure AD?

Q18. What is Azure Service Fabric?

Q19. How many instances should be deployed to satisfy the azure SLA?

Q20. Give examples of Azure PAAS? Platform as a service?

============================================================================

Q16. What is Azure Web Jobs? How they are different from Azure Functions?

Answer:

Azure WebJobs :

>> We can find Azure Web Jobs as follows Azure App Service > Create, Web App > Goto Settings "Azure Web Jobs"

>> Azure WebJobs is a feature of Azure App Service that allows you to run background tasks or scripts within the same instance as your web app.

>> Azure webjobs has no additional cost. its a part of Azure App Service Plan.

>> Best Use case: Long running task or background process.

>> Cost Model: Included in App Service Plan.

>> Hosting: Runs with App Service.

Azure Functions:

>> its a serverless compute service, use to run small piece of code. Highly scalable.

>> Good choice of event driven architecture.

>> Best use case: Event driven, serverless application. small piece of code.

>> Cost Model: Consumption plan (Pay per use) or App Service Plan.

>> Hosting: Runs without App service. Its a serverless service.

============================================================================

Q17. What is Tenant ID, Client ID and Client secret key in Azure AD?

Answer:

In Azure Active Directory (Azure AD), the Client ID, Tenant ID, and Client Secret Key are essential components for authenticating and authorizing

applications.

Tenant ID

Definition: The Tenant ID is a unique identifier for your Azure AD tenant, which is essentially your organization’s directory in Azure.

Purpose: It is used to identify the directory that your application belongs to.

Client ID

Definition: The Client ID, also known as the Application ID, is a unique identifier assigned to your application when you register it in Azure AD.

Purpose: It is used to identify your application during authentication and authorization processes.

Client Secret Key

Definition: The Client Secret Key is a password-like value that your application uses to authenticate itself when requesting tokens from Azure AD.

Purpose: It is used in conjunction with the Client ID to securely authenticate your application.

We have multiple ClientID for single TentantID. ClientID is like application ID, there could be many applications in a single Tenant.

============================================================================

Q18. What is Azure Service Fabric?

Answer:

Azure service fabric is like Kubernetes, red hat OpenShift. It's an orchestration platform.

You can have your containers running in it. you can increase decrease the count of nodes running in service fabric.

============================================================================

Q19. How many instances should be deployed to satisfy the azure SLA?

Answer:

The Windows Azure service level agreement guarantees that when you deploy two or more role instances in different fault and upgrade domains, Microsoft will guarantee at least a 99.95% uptime

=============================================================================

Q20. Give examples of Azure PAAS? Platform as a service?

Answer:

SaaS: Office 365, Skype, Dropbox, Cisco webex.

PaaS: Web Apps, Mobile Apps, Logic Apps, Web Jobs, Functions

IaaS: Azure Virtual Machines

PaaS: We are responsible for development and management of application.

========================================================================

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",

...

}

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

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.

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

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.

https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview

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

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"
                }

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

Search This Blog