Azure DevOps Interview Questions and Answers | Azure DevOps Interview Call | Azure DevOps Pipeline

Video Statistics and Information

Video
Captions Word Cloud
Reddit Comments
Captions
hey folks my name is raish and welcome back to another video in the series of devops interviews now I have a profile with me so the person is having around 7 years of total experience in it and relevant experience in devops is around 4 years and relevant experience in cloud is around four years the preferred public cloud provider is azure for the person and I've asked a few questions on the service connections uh with him so this interview is mostly concentrated on Azure devops and and I have been saying this quite since quite long that whenever you go for an interview whenever you go for any s devop space interview know your application and at least the build cycle build cycle means if there are five steps 10 steps or 15 Steps in your production pipeline or in your pipeline from step one till step end like first step would be what like checking out of the code and the last step would be like deploying to production you should know each and every step because the person who is going to interview you he's going to ask you like okay this is something uh that what you have done in uh what you have done differently and if I want to create a new Pipeline and if you are a team lead how will you do it so these are the questions that are mostly based on the step by step so you need to know each and every step and if you want to practice this just take out a pen and paper and practice each and every step and uh practice in front of a mirror that okay if the interview is going to ask me this question how I'm going to answer this question okay so this is one important thing so in this uh interview you'll be uh seeing that I'll be asking the step by-step thing like how the code checkout is happening how the build is happening what kind of project he has worked on is a Java based C B net based something like that all right so uh and how it goes till production all right so that would be the interview for today all right so uh again I would like to request that if you're new where here and see me for the first time my name is Rish and I create content for devops and Cloud related stuff kindly subscribe the channel because it really motivates me to create more content like this so without further ado let's get [Music] started uh what is your total years of experience 6 years 10 months 6 years yes yes okay and uh in devops in devops four years okay and in Cloud yeah on cloud again I have a four years but uh I have not worked on much much functional actually only creating a VMS uh creating app Services okay uh which Cloud do you prefer Azure Azure okay cool um yeah can you just walk me through the project yes sure uh prior to this organization I work with where we work for a project called Health Management System so there we have different kinds of applications all applications are net core and Net Framework so my my day-to-day activities and my ma major role is that so I need to onboard the onboard the client of project whatever the new project is there and I need to create the uh dashboards Azure Azure Azure dashboards for that to monitor their project and I need to assign the particular work work template according to their requirement um after that I need to create a reports uh uh and using that report I need to create cacd pipelines so once it is everything is done I can hand over it to the team so these are my day-to-day activities okay okay so um you worked on Azure devops most of the time right yeah maure devops yes okay okay so how do you create a service Connection in Azure devops service connection yes uh suppose like uh we have sonar Cube uh to we integrated sonar cube with a the apps mhm uh while integrating actually sonar ke was uh uh it was not it was not there and I have went to the marketplace and I downloaded it from there uh and I and I create and I configured with a Dev that I that time I use that service connection I'm asking how do you create it uh sorry I'm not able to recollect it now actually I you did it long back in when I was in ABM okay okay um so what were the things that you were doing in aured devops uh that only uh onboarding the clients and creating a report and creating CD pipelines when our infrastructure is all ready so the we use the same infrastructure or same Resource Group to deploy our applications and sometimes if it is not ready if on the on the Fly we need to create we just created the VMS they provide the details whatp the where exactly and Azure they create they will give the details uh for which which which network that needs to be created so on that using the details we created it um okay let's not move to Azure as of now we'll stay on Azure devops only so I'm just asking what were your responsibilities in Azure devops yeah that's that's what done what all my responsibilities I need to create CD pipelines for the new projects okay okay uh what do you understand by azure uh like to to maintain our project uh to monitor our work items like uh status of the project who are working on what work items so we have Azure boards Azure boards will help us to track that okay is there any other tools in the market like that yeah we have zir yeah yeah yeah we have zir so why should I use Azure boards if I have already have jira yeah if you already have jir like if you use the Azure Dev apps uh you can like uh already along with the Azure Dev apps you'll get the Azure boards right so you can track and you will get uh uh updates what at all what at all you have and you'll take immediate actions right suppose uh I raised like have I have one pipeline which needs to be deployed so for that I created a task and uh uh so that task like need to be approved to get executed so I feel like uh when we already have something in a apps and we are using Azu Dev apps so I feel that we'll go with that okay okay uh what are all the containers does Azure devop support containers yes uh containers do are like uh any containerization tools you're talking about yes what all the tools that it supports have you ever written any pipeline or something in which we use some containers uh pipelines I did but we use only classic editor pipelines only no not yaml no not yaml so only classic only classic do you know the difference between both of them classic and with yaml uh difference like what I feel like uh uh so we can pick the task whatever we do in classic editor but the for the same task we need to write uh uh to call that particular task we need to write ml ml script so I feel that okay and and we can say if if we are going with AML we can save that into our repos as well so whatever we do updates that will get uh reflect in our repos as well so that is a major uh difference I feel okay so you said that you have worked on net based projects have you ever worked on any any other projects like Java base any any other thing uh no Java base I did not work and in Highland I got a chance to work on Sear projects but actually already that like pipelines are already exist their main concern is that like that are getting more time like uh four to 5 hours to build a package single package so that is their concern that they requested to cut it down to half an hour like so I I seen that pipeline but I haven't created c p okay uh C+ okay so uh consider a scenario okay in which uh a person from the development development team is writing code in C or net based anything and he's putting his code into repositories uh take okay Azure devops may like you can take get GitHub or you can take just Azure repos anything okay now can you create a pipeline till production uh from that and what are all the steps that you will use in the pipeline and uh the tools and Technologies and what would be uh the way you will deploy till production can you just create a pipeline and walk me through the steps yeah yeah sure so first we need to build the package to build the package we need to create a c PIP plan uh we'll before before creating a p plan we'll select the repo from where the exactly code need to be pulled so C right you said mhm so first we'll uh uh collect that uh code and after that we'll take a step called Nate nugate restoration so so nugget step we'll take it so after that uh uh we'll we'll take uh sharp application build so ask for it and after that if any testing is there like sonar CU anything is integrated no no wait wait wait wait the first step is uh checking out the code okay yeah you just check out the code okay yes yes the Second Step would be uh building the code right yeah step right so how do you build the code yeah uh using net you can say Ms build using Ms build or visual Visual Studio build we can build the code you were talking about uh new get something right what happened to that suppose uh if any references in the code we have uh we need to use that into our something we used in our code so to call that we'll use this new get restor okay okay what is the next step third step y after building the code we need to test it right any test case we return uh does building your code produce produces anything artifacts it will give okay what kind kind of artifacts it all build artifacts that's what I'm saying what is a build artifact like what does it produce there could be some kind of file right yeah it it will create uh um build package file will build package okay any any okay I'll quote an example okay when you create a Java artifact it will produce class files and then you can pick it up in jar file file or an air file what happens to C orness based code what kind of package is it produced some kind of files right any kind yeah yeah extension yeah file extens any IDE any idea what kind of file it produces uh just some like oh no no no what uh no I'm not able to recollect it now have you heard about D files oh sorry yeah yeah what what exactly is the dll file uh dll file is is that uh while while we publishing like while producing the artifact it will give the in DL files only right net codes no no do you know the full form of D D full form uh no not okay any idea like what does it contain uh it contains like uh whatever manually if you're building a code it will have the package right in the DLS also the same way we'll have okay uh what is the next step after you produce uh after produce if any sonar Cube or anything integrated um we'll test that uh uh package so after that we'll publish it into artifactory storage like any sh shed storage if you have we can store there or otherwise it will store into Aur Factory okay so whenever you produce these artifacts uh these dll files uh you just keep it like lying over there or you just put it into some kind of artifactory or a place yeah that's is what I'm saying artifactory which artifactory Azure artifactory Azure Cloud yeah Azure cloud or Azure artifactory yeah I mean to say Azure artifactory only the naming okay okay Azure artifacts take all right uh after that uh the fifth step uh after you were talking about something related to testing right yeah yeah yeah the sonar Cube and stuff yes yes okay so what what happens uh with sonar Cube testing this uh fifth step uh like if you not mentioning any any Uh custom custom rules so it will automatically test how many number of lines of code is there and whether the code is are warnable or whether the code is good or correct what is the percentage of that code so these all details it will give okay okay so what do you understand by technical debt in in sonar Cube uh technical I did not get you going brief it technical de DBT technical okay okay uh technical so what is the uh use technical depth in the sense I'm get the meaning of it you can explain just the meaning or a definition anything anything would yeah yeah yeah yeah yeah actually uh sonar Cube it will help uh it help help the developer uh to like write the code accuracy of that code uh it will it will help like it will suest like the number of lines of code should be less then it should be produ like application application wise productivity it will improve okay uh what is the sixth step sixth step you deploy the code right okay okay so this is I'm talking about CA once the ca is completed then we will deploy the code using CD okay if already the environment is set up and resource groups is already created MH uh I will just try to deploy using uh whatever the whever the I'm saying we we stored it in Azure artifact right so we'll we'll try to take it from there um we we'll face it that so as an as an input so that uh we will create a tasks we'll create a jobs so if suppose simple task only one server we need to deploy so we will uh deploy it into part we'll create only one task for it and we'll create deploy it into the particular server only one server or one Service uh one I mean to say only one application is there that needs to be deployed and only one okay one service yes okay so this application is kind of a web service app service or you deploy it in a VM or something uh it's service only we are most of the things what we have okay uh so there is no Dev QA stage environment directly deployment production no no you no you like uh you ask me about dou production right so direct step I'm saying but we have we have D we have QA we have stage we have production four environments we have okay okay so first it goes to Dev stage then QA then QA then then to production yes yes okay I think I'm done thanks for your time
Info
Channel: LogicOps Lab
Views: 9,366
Rating: undefined out of 5
Keywords: azure devops interview questions and answers, devops interview questions, devops interview, devops interview recordings, devops interview questions and answers, devops interview questions for experienced, azure devops engineer interview questions, azure devops interview questions, azure devops interview, devops azure interview questions, azure devops interview call, end to end pipeline, azure end to end pipeline, azure devops pipeline tutorial step by step, azure devops piepline
Id: GsLZeNkMIQU
Channel Id: undefined
Length: 17min 34sec (1054 seconds)
Published: Sat Oct 28 2023
Related Videos
Note
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.