Azure Devops Frequently Asked and Interview Questins And Answers:

1.What challenges exist when creating DevOps pipelines?

Ans: The deployment is actually triggered in multiple steps. The first step in the pipeline starts the build process of the application. The migrations are run in the application context. If the migrations are successful, they will trigger the deployment pipeline if not the application won’t be deployed.

2. How do Containers communicate in Kubernetes?

Ans: A Pod is a mapping between containers in Kubernetes. A Pod may contain multiple containers. Pods have a flat network hierarchy inside an overlay network and communicate to each other in a flat fashion, meaning that in theory any pod inside that overlay network can speak to any other Pod.

3. How do you restrict the communication between Kubernetes Pods?

Ans: Policies can restrict based on IP addresses, ports, and/or selectors. (Selectors are a Kubernetes-specific feature that allow connecting and associating rules or components between each other. For example, you may connect specific volumes to specific Pods based on labels by leveraging selectors.)

4. What is a Virtual Private Cloud or VNet?

Ans: Cloud providers allow fine grained control over the network plane for isolation of components and resources. In general there are a lot of similarities among the usage concepts of the cloud providers. But as you go into the details there are some fundamental differences between how various cloud providers handle this segregation.

5. What is CNI, how does it work, and how is it used in Kubernetes?

Ans: The Container Network Interface (CNI) When the CNI plugin is added, a virtual ethernet device pair is created and then connected between the Pod network namespace and the Host network namespace. Once IPs and routes are created and assigned, the information is return to the Kubernetes API server.

6. How does Kubernetes orchestrate Containers?

Ans: Kubernetes Containers are scheduled to run based on their scheduling policy and the available resources. Every Pod that needs to run is added to a queue and the scheduler takes it off the queue and schedules it. If it fails, the error handler adds it back to the queue for later scheduling.


7. What is the difference between orchestration and classic automation? What are some common orchestration solutions?

Ans: Classic automation covers the automation of software installation and system configuration such as user creation, permissions, security baselining, while orchestration is more focused on the connection and interaction of existing and provided services. (Configuration management covers both classic automation and orchestration.)

8. What is the difference between CI and CD?

Ans: CI stands for “continuous integration” and CD is “continuous delivery” or “continuous deployment.” CI is the foundation of both continuous delivery and continuous deployment. Continuous delivery and continuous deployment automate releases whereas CI only automates the build.

9.Describe some deployment patterns?

Ans: Blue Green Deployments and Canary Releases are common deployment patterns. In blue green deployments you have two identical environments. The “green” environment hosts the current production system. Deployment happens in the “blue” environment.

10. [AZURE] How do you setup a Virtual Private Cloud (VPC)?

Ans: VPCs on AWS generally consist of a CIDR with multiple subnets. AWS allows one internet gateway (IG) per VPC, which is used to route traffic to and from the internet. The subnet with the IG is considered the public subnet and all others are considered private.