Home / Microsoft Azure

Microsoft Azure Fabric Interview Questions

Rating: 5.0Blog-star
Views: 7674
by Ravindra Savaram
Last modified: June 24th 2021

If you're looking for Microsoft Azure Fabric Interview Questions for Experienced or Freshers, you are at the right place. There are a lot of opportunities from many reputed companies in the world. According to research, the average salary for Microsoft Azure Fabric is approximately $98,450 pa. So, You still have the opportunity to move ahead in your career as an Azure Developer. Mindmajix offers Advanced Microsoft Azure Fabric Interview Questions 2021 that helps you in cracking your interview & acquire your dream career as Azure Service Fabric Architect.

If you want to enrich your career and become a professional in Microsoft Azure Fabric, then enroll in "Microsoft Azure Fabric Training". This course will help you to achieve excellence in this domain.

Top 20 Microsoft Azure Fabric Interview Questions and Answers

1. Define Azure Service Fabric.

Azure Service Fabric is termed as a stage for distributed systems that eases the work of deploying, packaging, and managing reliable and scalable microservices. It also handles noteworthy problems related to the development of cloud applications. 

2. Define Service Fabric Cluster.

Service Fabric Cluster can be described as a shared pool of machines. These clusters can have thousands of machines and can expand their areas globally.

3. Describe the importance of application instances in Azure Service Fabric.

Application instance in Azure Service Fabric can be run as a separate process even though they are on the same Fabric Service node. One can have as many application instances of any type as they want in a cluster. Each application instance will have a specific name in a cluster and independently managed and versioned from the rest application instances of the same or different type. Moreover, resources and security isolation can be defined by them.

4. Define cluster in Azure Fabric Service

A cluster can be described as a collection of virtual/physical machines that are connected by a network. On these machines only, application instances are getting deployed.

5. Define node in Azure Fabric Service

A node in a cluster is an addressable unit. It has unique IDs and placement properties. The cluster can be formed as different nodes.

6. Does a cluster have any minimum size limit? If yes, what and why?

Yes. Azure supports a minimum of 5 nodes for the production environment for a Service Cluster. For dev/test environments, Azure supports three nodes of the cluster. This minimum node requirement exists as Azure runs a collection of Stateful Services. These services are directly dependent on consistency. And this strong consistency is directly dependent on the ability of any service to obtain a quorum for an update to the state of them. Quorum amounts to the majority of replicas for a given service.

7. Define Service type in Azure Service Fabric.

A service type is a coding unit or a configuration that runs independently. An application type can have one or more service types. For example, Queue Service

8. Define Service instance in Azure Service Fabric.

The service instance can be defined as code which instantiated for each service type. Every service instance is associated with a specific application instance and will have a unique name.

9. Define application package in Azure Service Fabric

Application packages are composed of service code packages and configuration files of a particular application. For example, an email application package is a combination of a front-end service package, queue service package, and database service package.

10. Explain MicroService.

MicroService applications are formed of scalable, compact, stand-alone, and customer-focused services, which converse with each other using standard protocols and well-defined interfaces.

11. Describe different types of MicroServices.

Below are two types of MicroServices:

1. Stateless Microservices – they don’t continue to keep an inconsistent state outside of any request and its response from the service. For example, Azure Cloud Services worker roles, web proxies, etc.
2. Stateful Microservices – They continue to keep an inconsistent state beyond the request and its response from the service. For example, Shopping carts, queues, etc.

Today’s Internet-scale applications composed of a combination of stateless and stateful microservices.

12. Define Application type in Azure Service Fabric.

The application type is a collection of one or more service types or we can describe them as a collection of microservices. 

13. Brief about Programming models available in Azure Service Fabric.

To build applications in Azure Service Fabric, we have two programming models:

1. Reliable Services: An API to develop stateful and stateless services using StatelessService and StatefulService .NET classes and save state in .NET collections like dictionary and queue. 
2. Reliable Actors: An API to build stateless and stateful objects using the virtual actor programming model that is suitable for applications with different independent units of state and compute.

14. How the Nodes in Service Fabric behave in case of OS updates?

As of now, nodes in Azure Service Fabric don’t receive OS updates automatically. Azure doesn’t support automatic OS updates in nodes of Service Fabric.

15. Is it feasible to turn off the cluster during weekends/night for saving money?

No, it is not at all a feasible option. If we turn off the cluster during weekends/nights when we restart them afterward, almost all the nodes will obtain a brand-new host and in turn, makes the system unrecoverable.

Learn Microsoft Dynamics 365 Tutorial

16. What is a Container?

The container is an individual component that can be run independently and as an isolated instance to gain the benefits of virtualization which an OS gives. It provides a varying environment for the application to run with different types of isolation.

17. Explain the advantages of the container over virtual machines.

Below are the advantages of the container over virtual machines.

1. Smart: Use a single storage space and layer versions to increase efficiency
2. Fast: Start faster as no need to boot an operating system
3. Portability: Application image can be ported to run on the cloud, virtual machines, premises or physical devices
4. Resource Governance: Resources can be limited consumed by the host.

Container over Virtual Machines

18. Which two metrics affect resource governance that is supported in Service Fabric?

Two metrics affects resource governance, supported in Service Fabric:

1. CPU: metric name - servicefabric:/_CpuCores
2. Memory: metric name - servicefabric:/_MemoryInMB

These two metrics map total cluster capacity and how much load a node can bear.

19. Define horizontal scaling.

Horizontal scaling can be termed as scaling by increasing machines in the pool of resources.

20. Define vertical scaling.

Vertical scaling can be termed as scaling by increasing more power like CPU or RAM to a machine.

About Author

author
NameRavindra Savaram
Author Bio

 

Ravindra Savaram is a Content Lead at Mindmajix.com. His passion lies in writing articles on the most popular IT platforms including Machine learning, DevOps, Data Science, Artificial Intelligence, RPA, Deep Learning, and so on. You can stay up to date on all these technologies by following him on LinkedIn and Twitter.