KALEEM YASIR

Yes. Myself, Kalim here. I have a total of 14 years of IT experience, and I started my career with Wipro as a data center analyst. After that, I worked on Linux, Solaris, VMware, Windows, and storage systems including NetApp, EMC, and Pure Storage. I then switched to the cloud platform, like Azure. Over the past 5 to 6 years, I've been working on Azure Cloud as a cloud ops and cloud DevOps team member. On a project with shared resources, I was working. I've worked on Azure, AWS, Linux, and Windows. Based on the tickets, I work on multiple platforms. That's all from my end regarding my roles and responsibilities. Moving on to my roles and responsibilities, I can say that I created resources and managed and monitored them. I created resources using the Azure portal, PowerShell, ARM templates, and Terraform as code. I also used IAC tools to create resources. Using DevOps, I created infrastructure and end-to-end processes, including CA to CD, and managed application deployment and branching strategies. I have experience with all these things.

Yes. Coming to the implementation of automatic scaling of resources, there is a provider in place in Terraform. In that provider, we need to specify AWS or Azure. And inside that, we need to add a subscription ID, tenant ID, and all these things, we need to keep it in the features. Like, in the provider's field, we need to add this. Or if you are using a module concept, like creating one module for root volume, you can create a number of resources, and you can call that module, and you can place a service principal in place, and you can call every time to that module, and you can create multiple resources. Okay? Same way, you can create your AKS cluster or EKS cluster or any kind of resources with the help of Terraform. Yes, that's all.

Coming to the zero-downtime deployment in Kubernetes, we are having a blue-green concept. Okay? Or blue-green strategy, we can say. Like, instead of, we have a blue-green deployment where it's active and passive. Okay? Till the active VMs are up and running, the secondary will be sitting idle, or you can do any modifications on the secondary site. And once anything goes wrong with the primary site, you can switch your VPCs or scale it up. Okay? The service can switch to the secondary. Nothing but the green one. Okay? And you can upgrade anything in the green as well, and you can directly switch your service to your secondary or clean green. Yes. That's all.

Coming to the logic apps, I haven't worked on Azure Logic Apps. Sorry. I'm not difficult here. An answer about this because I haven't worked on Azure Logic App. Yes. Sorry. Thank you.

Coming to migrating an on-premise application to AWS using a Docker container, we can upgrade or migrate using Azure Migrate. In Azure Migrate, we have a feature like an initial unit to create a project. In that project, you need to select the project key. And once you do the primary step, while you're going to upgrade or migrate your on-premise web app. In the web app, while you're going to upgrade or migrate, then you have an option called containerization. You can migrate your application to an AKS cluster or the app service in a container. These are the two areas where we can migrate our application to containerization.

Okay. If you want to do this, we can use a Terraform in place. Like, we can use the same code. What are the code we are going to implement for AWS? We can create a resource with the help of Terraform in Azure also. Okay? In this way, we can manage the code uniformly and just we need to change the provider in place. Okay? Rest everything remains same.

Analyzing this Python function design to list all the unique features. Sorry. I'm not aware of this answer, because I'm not familiar with the Python, but I am aware of the file PowerShell script.

Name is equal to instance - where that is environmental. Okay, here, there is some code that is wrong. We need to correct that here. Name is equal to, instead of this instance, we need to go to some other field.

Coming to this question, like, we can create a web application using Terraform. Like, we can create one module. Inside that module, you need to create a main file as well as the variable file. Okay? In that main file, you can place all the service principal kind of things. And in variables, you can call out what are the variables you are going to declare in respective modules. Like, if you want to create a resource group or if you want to create an application gateway or app services, all these things you are going to place in the submodules of your module. Okay? And inside those submodules, you are going to declare the variables and then redirect them to your root module. In that way, you can create your web application as well as a multi-tier web application.

Coming to this answer, I have worked on Azure monitor where we can check the metrics. It shows live metrics. And based on that, we can create an alert rule. Okay. As well as there is a Log Analytics workspace. Using that Log Analytics workspace, we can write a query in the query language, and we can get the output in a graphical view. Okay? And I also worked on Grafana. Okay? You can integrate your Grafana with Azure monitor so that you can track or check all the metrics with the help of Grafana also. Okay? In that way, I worked on Azure monitor, the Log Analytics workspace, as well as Grafana. We also have Splunk, but I am not aware of it. Yes.

Like in Azure, I'm familiar with it. We are having a log analytics workspace where it will be centralized. It is a centralized logging solution. If you want to get any output with the help of push to query language, we can get the output. Okay, the main centralized logging solution for Azure is Log Analytics Workplace. Okay, that's all. For AWS, I'm not aware of it. Yes, thank you.