hello everyone this is Samuel and I'm

very excited that you're watching this

video and I would like to welcome you to

this as your interview preparation

session knowing as yours one thing

having worked on as your is another

thing and being able to answer interview

questions in Azure is a totally

different thing although one helps the

other it's still different skills and

our aim through this video is to prepare

you with common product and scenario

based interview questions so why wait

let's get started

a common cloud interview question is

what's the difference between SAS pass

and is we all know that a

software-as-a-service is thin client

model of software provisioning where

client in this case usually is simply a

web browser providing the point of

access to software's running on the

servers now SAS is the most familiar

form of cloud service for customers saz

moves the task of managing software and

its deployment to third-party services

meaning the vendor actually gets to

manage all that so

SAS is software as a service involving

applications being consumed and used by

organization so it's generally using an

application and usually organizations

pay for their use of this particular

application now some examples of SAS

would include office 365 salesforce is

another very good example of SAS and a

lot of Google Apps and storage solutions

lightbox and Dropbox are a very good

example of software as a service talking

about platform as a service or pass it

actually functions at the lower level

than SAS now typically it provides a

platform on which software can be

developed and deployed now here we

develop the software we deploy the

software now pass actually provides an

abstract of much of the work dealing

with servers and giving client an

environment in which the operating

system and the server software and the

hardware's the net

work or managed and taken care in other

words with a platform-as-a-service

all the things that I've mentioned like

these servers the server software the

hardware everything is managed by the

provider and we can focus on business

side of the scalability and we can focus

on application development of our

product or the service so in short

platform as a service is a service that

enables developers to build and work

with applications without even having to

worry about the infrastructure or

management of the underlying hosting

environments and some examples of paths

in Azure is SQL and Azure storage

talking about infrastructure as a

service I as now this is moving down the

stack even further now we get to the

fundamental building block of the cloud

service which is infrastructure as a

service I as now I as is fully off

highly automated scalable computer

resources I ask this full of storage I

as is full of the network capability

that's what I as is now I as clients

have direct access to the servers and

storage just as they would to do

traditional servers but in this case

it's going to be in the cloud in this

case it's gonna be more scalable so I

ask is very similar to what you would do

in your on-premises physical data center

but when we talk about is we get to do

everything but it's stored in the cloud

so if we need to build a definition

around I as I as our infrastructure as a

service provides users with components

it provides components it does not give

as in built environment it simply

provides a component such as operating

system and networking capabilities and

lot more now this is a paid for based on

the usage and can be used to host

applications in other words this is

pay-as-you-go type the more you use the

more you pay the less you use the less

you pay and some of the examples of I as

an azure is a virtual machine that's a

great example for I as and V nets for

networking that's another good example

for I as in a

another common question in as your

interview is what are the instant types

offered by a sure the main intention of

this question is how well have you

understood the different offerings in

Azure and how well are you trained to

pick the right offering for the right

service now one size does not fit all

and there are there are a lot of

services in Azure that under the carpet

it does the same thing but depending on

how different your requirement is we'll

have to pick the appropriate service so

this actually this question what are the

different incident types offered by as

your it's to test how well have you used

the product and services available on

Azure and how well have you applied them

for the given requirement you shouldn't

be provisioning more you shouldn't be

provisioning less at the same time so

it's kind of matching the right service

to the right requirement so what are the

instant types offered by Azure as you

seen the list we have general purpose

computer optimized memory optimized

storage optimized GPU virtual machines

and high performance computer virtual

machines now answering just the names

won't be enough in an interview you'll

have to go further and explain why and

in what scenario you would use general

purpose and what are the use cases

what type of servers is a good fit for a

general purpose and what type is a good

fit for computer optimized so on and so

forth and that's exactly what we're

gonna do now so the general purpose VMs

you know they provide a balanced CPU to

memory ratio and it's very good for

testing very good for a development

environment very good for small and

medium databases and also for low to

medium traffic web servers and some of

the use cases are like we said test

servers low traffic web servers small to

medium databases some enterprise great

applications it's also good for

relational database it's also good for

servers used for in-memory caching it's

also good for some small analytic

database very good for micro services

and if you're trying to build a proof of

concept for an idea that you just have

or a just parked and this is another

good server for doing

proof of concepts because you're not

gonna send actual traffic to it I just

want to show that you know your idea

works so general-purpose server is a

very good use case for those scenarios

and the largest instance size we can get

in general purpose is standard D 64 III

which comes with 256 gigabyte of memory

and 1,600 Giga bit of SSD temporary

storage on the other hand computer

optimized Williams have an a high CPU to

memory ratio and are very good for

medium traffic web servers are very good

for batch processing servers very good

for application servers now because it's

computer optimized and compute means a

CPU it's an excellent choice for

workloads that demand faster CPU but

does not need as much memory or

temporary storage which will CPU some of

the workloads that run very well on

computer optimized our analytic

workloads gaming servers require more

CPU they aren't really well a batch

processing are some of the applications

that can be placed in a computer

optimized N and by doing that we get the

actual benefit of the computer optimized

instance and a largest instance size or

the largest instance size type is

standard F 72s

or we - and here we get 144 gigabit of

memory and 576 gigabit of SSD temporary

storage in compute optimized Williams in

the same lines memory optimized to VM

they offer high memory to CPU ratio and

that are great for databases databases

require more memory so it's a great fit

for database and it's a great fit for

medium to large scale caches

applications that require in-memory

analytics so there's memory optimized

memories more so it's very good for

in-memory analytics applications and the

largest instance size we get here is

standard M 128 M and look at the gigabit

of memory it's thirty eight hundred

ninety two gigabit of memory and

look at the temporary storage it's 1,400

336 a gigabyte of temporary storage on

the same lines storage optimized now I

guess I don't have to explain to you

what storage optimized is used for you

might have easily guessed looking at the

flow yes

storage optimized we an offer high disk

throughput and i/o and are very ideal

for a big data sequel no sequel

databases data warehousing servers large

transactional databases and lot more and

some of the examples of the applications

that can be launched on storage

optimized our Cassandra MongoDB clowder

our Redis these are some familiar

applications that can get benefitted

when we run them on storage optimized

and one difference between storage

optimized and the other servers are and

they are generally optimized to use the

local disk on the node attached directly

to the VM rather than using an durable

disk which is actually an a remote a

disk space now what does this allow this

allows for greater input outputs per

second or a throughput for the workload

so that's what we get a greater

throughput at greater input outputs per

second is what we get when we use

storage optimized and the largest

instant size available and storage

optimized is standard l 32 s and the

memory is 256 gigabit and look at the

temporary storage

it's a 5630 gigabyte of temporary

storage GPU type Liam's easy to guess

GPU optimized to VMs are specialized

virtual machines available with multiple

GPUs attached to them now these sizes

are designed for or these VMs are

designed for compute intensive graphic

intensive visualization were closed that

require lot of graphical processing unit

attached to it so in short these are

virtual machines that specialize in

heavy graphic rendering and video

editing it also helps with model

training and interference in with a

standard and

24 RS which has 448 gigabyte of memory

and 2948 a gigabyte of temporary storage

and the last but not the least but the

best last but the best is

high-performance computer or as your

head CDs virtual machines now they are

the latest in high-performance computing

wheels and are aimed to handle workloads

like batch processing analytic molecular

modeling and fluid dynamics a lot of

complicated applications in this VM and

this is the fastest and powerful CPU

virtual machine with optional high

throughput interfaces and the largest

instant size that's available is a

standard l 32 s which comes with to 24

GB of memory and 20 hundred gigabyte of

SSD temporary storage and a third common

question is what are the deployment

environments offered by Azure

there are two main deployment

environments one is the staging

environment and the other one is the

production environment now in staging

environment let's talk about staging

first so when you are deploying a web

app or web app on Linux and you can

deploy them to a separate slot instead

of the default production slot when

running them in standard premium or

isolated app service plan tiers

now the deployment slots are actually

live app with their own host name and at

a later point that the staging

environment can be swapped with the

production environment so why do we need

an staging environment what are the

benefit of it so the benefit of

deploying our application to a non

production or staging environment it

provides a platform to validate changes

to our application before it can be made

live in the production environment and

in the staging environment the app can

be identified using the azores global a

unique identifier also called as the GU

ID URL and it's very very similar to the

production URL except that it has an

custom name in front of it that

identifies it as the staging environment

and for production environment this is

the live

production environment that serving

customers request that serving the

customer content now it can be slightly

different from the staging environment

in a way that the URL that's used to

identify the production environment

that's more of an DNS friendly name like

the name of the actual service dot Cloud

app.net that way it differs in case of

staging environment you have an custom

name right before it so the custom name

and then the cloud app dotnet but in

this case you get the direct service

name as the name of the URL so this is

live production environment which

receives and handlers and serves

customer traffic another commonly asked

question in Azure is what are the

advantages of scaling in Azure the

actual thought behind the question is to

see how much have you understood scaling

how much have you seen and how much have

you applied the scaling effect in the

production environment and have received

benefits in return so let's talk about

it

advantages of scaling in Azure some of

the advantages are or we get the maximum

application performance now auto scaling

is a built-in feature for the cloud

services be it

AWS your Google and couple of other

cloud service providers it's a built-in

feature for a cloud service a cloud

service should be auto scalable and that

includes mobile services virtual

machines and when we run our

applications on mobile services or

virtual machines the website actually

gets the best performance during the

change in the demand again a different

applications might require different

performance needs for examples for some

apps the performance measure based on

memory and another a good example is the

fluctuating demand for example you could

have a web app that handles millions of

requests during the day and literally

nothing at the night and auto scaling

this environment auto scaling any of

these environment will automatically

scale or fatten your environment so to

receive the all the incoming traffic and

during lean period it actually yet

slimmer answer

sort of help you with the car so it

actually maximizes the performance

that's what are the scaling does and

like we said auto scaling scales up and

scales down based on demand

it not only scales up but also scales

down so to help you with the cost and if

you know the particular pattern in which

the application is gonna receive traffic

then we can very well go ahead and

schedule scaling to our application or

schedule scaling that infrastructure

based on time if we already know that

money to Friday that's the traffic that

I would get and it's a constant one it's

not a public-facing but you know it's an

internal application so I know all the

500 users or the thousand or the 5,000

users who will be using itself at any

given point it's just 5,000 users it's

not gonna go beyond that and during

Saturday and Sunday lootellan nobody is

gonna be in office so no load at all so

in that case I pretty much know how the

pattern is gonna be I can go for

schedules killing if I know at the

pattern and auto-scaling like I said not

only helps with keeping the application

highly available it also helps with the

cost-effectiveness of our infrastructure

so anytime there's a VM or a group of

VMs running on less CPU auto scaling is

gonna actually get the environment

slimmer and slimmer so we're not

unnecessarily running any resources and

paying for it if you're being

interviewed for the infra site in Azure

this is another common question that

gets asked how are Windows Active

Directory and as your Active Directory

different let's talk about the Windows

Active Directory first the non cloud

Windows Active Directory was the service

was released along with Windows 2000

server edition and this Active Directory

is essentially a database that helps

organizations to organize the users

organize the computers and lot more it

provides authentication and

authorization to the applications not

only to the applications but also to

file servers to printers and a lot of

other on-premises resources that's what

they basically non-cloud Active

Directory does on the other hand the

azure active directory is not designed

to

web-based services the azure active

directory on the other hand was designed

to support web-based services that use

REST API interfaces for office 365

salesforce.com etc unlike the plain

active directory this uses an completely

different protocol so protocol wise it's

different and the services that it

support is quite different now besides

that it also has a couple of other

differences as well and let's look at

them so the actual Active Directory or

the windows actual directory is a

directory service that facilitates

working with interconnected complex and

different network resources in a very

unified manner on the other hand as your

Active Directory is Microsoft's

multi-tenant cloud-based directory and

identity management service and the

Windows Active Directory has five layers

to store data to store user details and

to issue the management certifications

on the other hand as your Active

Directory integrates or compresses the

five layers into just two layers here

Windows Active Directory works with

on-premises servers like Applications

file servers and Printers etc on the

other hand as your Active Directory it

works on web based services that use

restful interfaces if you're being hired

for the development environment or for

the cloud DevOps support environment or

even for the production support

environment you might find yourself

being asked this question what are the

types of queues offered by Azure now as

your supports two types of queue

mechanisms the storage queue and the

service bus queue let's talk about

storage queue first now the storage

queue which are part of Azure storage

infrastructure it provides a simple

rest-based interface simple rest-based

get put and peek interface it provides

reliable persistent messaging within and

between and the services it follows the

pub/sub model or a pub/sub messaging

infrastructure and it's best suited for

users that need to store more than 80

giver of messages in the queue it can

provide a logs for all the trans

actions executed against the users queue

so that's what we get with storage queue

and on the other hand service bus queue

the service bus queues are built on top

of broader messaging infrastructure and

they are designed to integrate

applications and applications component

that can span multiple communication

protocols so that way it differs so this

is good for applications and components

that may span multiple communication

protocols and even different totally

different Network environments so in

short these service buses or the service

bus queues in Azure are part of as yours

messaging infrastructure and they

integrate applications or application

components that can actually span

multiple different protocols and

multiple different network environments

it also provides an first-in first-out

style for delivery and the users queue

size has to remain under 80 gigabit

another familiar question is what are

the advantages of as your resource

manager now the resource manager helps

us to manage at the usage of the

application resources this question is

actually to test how well have you

tested how well have you used resource

manager and have gotten the benefit of

it this question actually tests how easy

it has become after the introduction of

resource manager compared to when doing

deployments or when provisioning

resources without the resource manager

so let's get it into the answers for the

question what are the advantages of as

your resource manager the ensured

resource manager is called AR M so the

AR M helps deploy manage and monitor all

the resources for an application a

solution or a group so all the

interconnected application all the

interconnected services can be monitored

as group using resource manager and

users can be granted to access to

resources that they require within a

resource manager so in an account I can

have like 10 different resources created

by a resource manager or a resource

group created by resource managers and I

can allow deny connection to those

services or only to those services based

on or whether the user should be

accessing one and not accessing the

other so that way it becomes easy to

give access to a group

of application it helps in getting

billing details for the group of

resources now which group is using more

which group is using less and which

group has contributed more to this

month's bill stuff like that so those

details can be obtained using as your

source manager and provisioning

resources is made much easier with the

help of this resource manager another

question is how has integrating hybrid

cloud being useful for Azure well with

the use of hybrid cloud we get the best

of both the worlds

so what's hybrid cloud it's nothing but

combining the public cloud and the

private cloud and allowing data on

applications to be shared between them

so whenever the compute or the

processing demand fluctuates hybrid

cloud computing gives businesses the

ability to seamlessly scale their

on-premises infrastructure in the public

cloud and handle any kind of overflow in

the requirement or overflow in handling

the application so it really helps it

helps it boost the productivity of our

on-premises application so with the

hybrid cloud we get a greater efficiency

with combination of Azure services

DevOps processes and tools for the

applications running in on-premises and

by having an hybrid cloud environment

users can take advantage of constantly

updated Azure service and other AWS

marketplace applications for their

on-premises environment and the other

benefit is with hybrid cloud environment

we can simply deploy applications

regardless of its locations in case of

on-premises we'll have to worry about

the location but when we expand our

on-premises environment in the cloud and

they can or we can pick any of the

locations and simply deploy it in them

and this enables the applications to be

created at a greater speed

what's federating in Azure SQL now this

question is very specific about SQL how

can we scale the SQL database now this

is a very good question or a valid

question or an important question in the

interview because many customers or

companies have an

been able to meet the user demand

because they could not scale out the

databases the theory of scaling out or

adding servers to accommodate the

increased workload and traffic is not

hard to understand but the implications

can be very complicated the implications

can be very expensive we are well aware

of scaling the web service that's very

common but how do we scale at the

database so Microsoft provides the tools

and technologies so we can scale out the

database in the cloud and that's what is

called SQL or Federation and as your SQL

so the way we scale out the SQL database

is by Charlaine charting the database so

sharding actually enables users to take

advantages of the resources in the cloud

not only that it allows users to have

their own database or a shared database

amongst each other because we're

creating a highly available database

because we're having shards in a

database it actually reduces the

possibility of a single point of failure

for our database and more importantly

because we're sharing because we're

using Federation and as your SQL it

provides an cost effective scaling of

our databases by using cloud resources

or by using billing only for the cloud

resources that we have used so no pre

provisioning no over-provisioning it

provisions the right amount and we pay

the right amount let's talk about this

one what are the different types of

storage offered by Azure

now the different types of storage

offered by as your are as you already

know and as you can see they are as your

blob storages table storages file

storage and queue storage so let's

expand one after the other

now blob storage are nothing but a

massive scalable object storage and

that's very good for storing text and

binary data and as your blob storage is

Microsoft's object storage solution for

the cloud a blob storage is optimized

for storing a massive massive amount of

unstructured data that can be in form of

text or or in form of binary data

so in short blob storage enables users

to store unstructured data and those

data can be in the

of pictures music video files and lot

more and it stores them along with their

metadata and another advantage or

another feature benefit that we get from

blob storage is when object is changed

it is verified to ensure it is off the

latest version number one and number two

it provides maximum flexibility to

optimize the users storage needs and

this unstructured data is available to

customers through an URL or an arrest

base object storage so they are the

benefits that come along with the blob

storage table storage on the other hand

is an a no sequel store for schema-less

storage of secured data now this as your

table storage is a service that stores

structured no sequel data in the cloud

and because this table is a schema less

it's very easy to save your data it's

very easy to adapt your data as the need

for your application grows and this

table storage is very fast and

cost-effective for many type of

applications so some of the some of the

type of data that we can store is table

storage is good for flexible databases

like user data for web applications

address book storage device information

storage and if you want to store

metadata this is a very good use case to

store them in as your table storage as

your files is another storage here it's

an managed file share for cloud or

on-premise deployment so file storage

provides the file sharing capabilities

accessible by the server messaging block

protocol and this can be accessed from

the cloud and this can be accessed from

on-premises as well now here in file

storage the data is protected by SMB 3.0

and haich-d dps are protocols and the

more important thing is as your takes

care of managing hardware and the

operating system deployments for as your

file storage so this additional file

storage can be used when we want to

burst the storage capacity in

on-premises so on-premises the primary

and cloud is the secondary or the

extended on-premises storage so it

actually improves the on promises

performance and capabilities for our

on-premises

data center and then we have Q's as your

Q's it's a messaging store for reliable

messaging between the application

components we spoke a little about this

in the previous question so the as your

Q storage is a service for storing a

large amount of messages that can be

accessed from anywhere in the world we

are HTTP or HTTPS a protocol and here

the a single message can be up to 64

kilobits in size and in a queue we can

have millions of messages and the limit

can actually go up if we have not

reached the limit after the storage

account so its millions and millions of

requests that can be stored in the

storage queue or the Q storage so the Q

storage in short provides message

queuing for large workloads and it

enables users to build flexible

applications and separate the function

so one from another so one failing

doesn't affect the other application

which is running healthy and this Q

storage it ensures the application is

scalable and less prone to individual

component failures because they are

decoupled separate now it also helps in

monitoring the queue which ensures the

customer's demands are met so Q is a

great place to monitor or a great

component to monitor so we understand

how much peak have you reached for a

particular application service or a

container

what is text analysis API in Azure

machine learning now text analysis is

actually an cloud-based analytics API

and it provides an advanced natural

language processing over the raw text

and it has got four main functions like

the sentiment analysis and the key

phrase analysis language deduction and a

few other things now what do you mean by

sentiment analysis now sentiment

analysis is from the logs from the

comments from the text comments that we

receive do an analysis and find out

whether that sent positive or a negative

statement now if it is a the API the API

returns and the sentiment score

between zero and one and one is positive

and zero is negative and then in text

analysis we have a key phrase extraction

which is it will automatically extract

at the key phrase to quickly identify

the main points in that key phrase for

example if you're analyzing and text

which says the food was delicious and

there were wonderful stuff then the API

returns the main talking points of that

phrase like food food is the main

talking point and wonderful stuffs that

was a main talking point so that's

another feature that this text analysis

has and then we have language deduction

in text analysis irrespective of what

you pasted it can try to gauge and try

to align it to the 120 or up to 120

languages that it supports so I can

simply take text from the internet and I

can paste it and text analysis software

is going to identify the language and

then can run phrase and sentiment

analysis on those texts alright so in

short text analysis is an API a set of

web services that can be used for text

analysis it can be used to analyze

unstructured statement sentiment

analysis keyphrase extraction and lot

more and the results are generally

between 0 & 1 & 1 being positive and 0

being the negative sentiment there is no

much training or in other words this is

not as complicated as a couple of other

text analysis softwares are available in

the market we can simply paste we can

simply upload the text and we can call

the service and it runs a sentiment

analysis on it all by itself let's look

at this question what are the advantages

of as your queue storage if you're gonna

work in a development environment if you

are gonna work in an environment that

embraces DevOps this could be a question

what are the advantages of your queue

storage now as your queue storage is

built to flexibly operate the

applications and separate the functions

between the applications that run large

workloads so when we design applications

for scale these applications can be

d couple so that they can scale

independently you know and thing

happening on an application is not

dependent on another application and

anything happens to and section of the

application will not affect the other

application because they are now

decoupled and corrected through the

queue storage so the cube storage gives

us asynchronous message queuing for

communication between the applications

irrespective of whether they are running

in the cloud or whether they are running

in desktop or whether they are running

on premises or on mobile devices so in

short this Q storage enables message

queuing for large workloads and as

simple and cost effective and a durable

manner

talking about the advantages advantages

is it provides rich client libraries for

Java Android C++ PHP Ruby and lot other

services getting added during every new

release from Azure and the main

advantage again is it enables users to

build flexible apps and separate the

functions for bigger or greater

durability again introduction of queues

into our application it ensures our

users applications are scalable and less

wrong to individual component failures

meaning one component failing is not

going to take the whole application down

right if one component fails it's just

that component that stays fails the rest

are healthy and the rest are going to

function it also helps us to monitor the

queues and ensure the servers are an

over held by sudden traffic burst so how

much do I have in the queue kind of

determines the traffic for my

application and if the queue is more I

can always go and auto scale my

environment and the queue was less I can

always go and shrink or make my

environment thinner so it can save cost

and anytime there is more data in the

queue I can autoscaler monitor the

metric and do auto scaling based on that

metric so the environment knows that

there are more data coming in I need to

expand myself to handle that much amount

of data this is a very common question

what are the two kinds of as your web

service roles now a service role is a

set of many

and load-balanced virtual machines that

work to perform some tasks and based on

what it's gonna run on top of it is it

gonna run web service or is it gonna run

worker service defines what kind of

roles that gets attached but that goes

on this virtual machines so we have two

types web role and worker roles the web

role is a cloud service role that's

configured to run web applications

developed on programming languages

technologies and majorly they support is

Internet Information Service and they

support asp.net PHP windows

communication foundation and so on so

that's web roles and these web roles it

automatically deploys and hosts

application through the users I is

Internet Information Service on the

other hand worker roles are roles that

runs applications and service level

tasks which generally do not require I

ASO is is actually the differentiating

factor so in worker roles is is not

installed by default the worker roles

are mainly used to perform supporting

background process along with web roles

and do tasks automatically compressing

or uploading the images running scripts

and or doing some changes in the

database getting new messages from the

queue and processing and a lot more you

know the work the applications are the

work that does not require IES that's

what this worker role does again the

main difference between the web role and

the worker role is that the web role

automatically deploys and host your

application through is whereas the

worker role does not use IES and runs

our obligation as standalone this is

another classic question what is your

service fabric so as your service fabric

is actually an distributed system

platform that makes it easy to pack

deploy and manage a scalable and

reliable micro services and containers

now service fabric also addresses some

of the significant challenges in

developing and managing cloud native

applications and the problem that it

addresses and fixes is now developers

and administers can avoid complex

infrastructure

and focus on implementing

mission-critical and demanding workloads

that can be scaled and that can be

managed through the console or from the

single place in short service fabric

provides a platform that makes the

process of developing micro services and

managing application lifecycle lot

easier and the advantages of service

fabric is that now we can produce

application with faster time-to-market

because all the worry about the

infrastructure is taken away from us we

don't have to design and infrastructure

all that we need to worry about is

simply the application and the

application lifecycle again the

advantage is it supports Windows it

supports Linux not only that it supports

servers on-premises and in the cloud

with service fabric we can scale up our

environment to even thousand machines in

just a single command or if there is an

immediate need for thousand machines I

can immediately scale them up to

thousand machines that's possible with

service fabric now let's look at this

question you can expect this question if

the customer is running hybrid

environment meaning having some of the

applications and on-premises and running

some of the applications from the cloud

and for some reason when classifying the

application that goes to the cloud and

that stays on premises they have decided

to keep the database in-house so in that

environment a lot of customers do that

so in that environment this is a classic

and a scenario based question a client

wants the front-end of their application

to be hosted on Azure in the cloud and

once the database to be hosted in

on-premises for security reasons or to

have full control on their databases how

do we go about suggesting a solution for

this customer the ideal solution in this

scenario is to use the v-net based point

to site VPN a solution so all the

front-end applications will be in the

cloud and they'll be hosted in a V net

and from the Wynette they'll be

connecting to the database through

endpoint to site VPN so the traffic and

the writings and the reads are not

coming through the internet but through

a point to site VPN link that's

connecting the as you

vennett and on-premises environment and

this model or this approach or the

solution is best suited for scenarios

where there are only a limited number of

resource that needs to be connected

between on premises and the cloud this

is a very common question what's as your

traffic manager of course we know more

running applications on a single server

we know more running applications on our

from a single environment the same

applications is being run from multiple

environments within Azure and it can be

running from Azure and on-premise as

well so multiple environments between

Azure and on-premises and a lot of

customers have such environment and if

you are facing an interview with such

customer this could be an ideal question

what is as your traffic manager now the

audio Traffic Manager is a DNS based

traffic load balancer that actually

enables us to distribute traffic between

services across as your global regions

and by doing this it provides a good

availability and a good responsiveness

to the application and this traffic

manager it uses DNS to direct client

requests to the most appropriate service

endpoint based on the traffic routing

logic and the health of the endpoints

that it maintains so in short this

traffic manager is a load balancer that

enables users to provide high

availability and responsiveness by

distributing traffic in an optimal

manner across the azure when we run the

same application in different regions so

some of the advantages or some of the

use cases of using as your traffic

manager is it provides multiple

automatic failover options it also helps

with reduced downtime it also helps with

the distribution of user traffic across

multiple locations so one location is

not overloaded and then it helps with

users knowing from where our customers

are getting connected from that's

another big use case with as your

traffic manager let's look at this

question thread this is an ideal

question now there are group of servers

connected together within an virtual

network and now we need to move them or

create a separation between them how

go about achieving it so the question

goes like this you need to isolate

network traffic among VMs in a subnet

which is part of a virtual network with

little downtime and impact on the user

so that's the given scenario and the

best way we can do it is create a new

virtual network and move all the VMS in

that subnet to the new virtual network

now this feature is not possible with a

lot of other cloud service providers

like AWS and a lot of other providers

now in those environments we might need

to shut down we might need to stop the

VM create a new we am based on the image

and it's an hefty process but here in

Azure I can simply move the VMS from one

subnet to another virtual network

without needing for any additional

security like the network security group

I can simply isolate them if I need to

by creating a simple new virtual network

and moving the servers to the new

virtual network look at this one this is

another common question with respect to

Azure what is probably private and

hybrid cloud so this is really to test

how well have you understood the

different cloud offerings in the market

public private and hybrid or at least

the three basic offerings in the market

public private and hybrid cloud now the

public cloud is the most common way of

deploying cloud computing applications

and it has resources like servers

storage and are owned and operated by

third party cloud service providers like

Microsoft Azure Microsoft Azure is a

very good example of public cloud so

here every component that the user is

using is running only on Azure that's

public cloud let me talk to you about

some of the advantages of public cloud

some of the advantages is low cost

because there's no need to purchase

hardware or software and we pay only for

the services that we use in public cloud

and there is literally no maintenance

because the service provider maintains

the environment for us and with public

cloud we have nearly unlimited

scalability meaning we can get resources

on demand and can meet our business

requirements on demand and the public

clouds are very highly reliable because

they have a vast network of servers and

they ensure that our application does

not fail so there are some advantages of

public cloud let's talk about private

cloud now private cloud consists of

compute resources used extensively by

one business or one organization now

this private cloud can be physically

located at our organization's on-site

data center or it can be hosted by a

third party service provider whichever

the case the private cloud services and

infrastructure are always maintained on

a private network and they are

maintained on hardware and software that

are dedicated solely for one

organization or solely for your

organization
so in short private cloud in Azure is

Azure services being run within an

on-premises data center or on-premises

data center used by the user to host

systems or applications and some of the

advantages some of the advantages is it

gives more security resources are not

shared with others so a higher level of

control and security over our resource

and application is possible and then we

have a hybrid cloud now hybrid cloud is

the best of both worlds so it combines

the features of both public and private

cloud and some of the user components

are being run on Azure and others within

on-premises data center so they kind of

share the resources in other words they

kind of share the application half of

the application would be running in on

premises and a half of them would be in

the cloud and they will be working in

harmony to support the application and

the business need so that's hybrid cloud

this is one another good example

question that wants to test how well you

pick services or how well have you

understood as your products and services

and are picking the right service for

the need so the question would go like

this what kind of storage is best suited

to handle unstructured data there are

lot of storage options available and the

requirement here is what or which one

would you choose

for unstructured data the answer for

that question is blob storage because

lot of storage is designed to support

unstructured data it works in this way

it places the data into different tiers

based on how often they are accessed

different tier means different

performance different performance means

different cost associated with it so lot

of add-on advantages will we get when we

use blob storage for unstructured data

in addition to it any type of

unstructured data can be stored in blob

storage this is not true with couple of

other storage options that we have in

Asscher only with blob storage we can

store any type of unstructured data and

the data integrity is maintained every

time an object is changed in the blob

storage and the best part is the blob

storage helps increase applications

performance and reduces the bandwidth

consumption and reduces the bandwidth

consumption for that applications they

are the benefits that we get for blob

storage and blob storage are the ones

that are well suited for unstructured

data and that's what your answer should

be it's really an five-step process and

if you've worked and if we have done

some labs some basic labs with Azure you

can easily answer this question so it's

a five step process first step is to log

into this your the second one is to

create and resource resource or a

resource manager and within the resource

manager you would be selecting the

resource and then pick the offering

system do you want Windows or Linux and

within Windows what's the flavor you

want or within Linux what's the flavor

you want to decide on it and then

entering the relevant information

relevant information like the name of

the instance or the VM that we got a

launch and the password the URL that

goes with it and a couple of other

relevant information that goes gets

itself attached with the VM and then

select the size of the virtual machine

different size different types available

for the kind of application and for the

intensity of the application that we'll

be running on top of it so select the

virtual select the size of the virtual

machine review everything whether

they're good or not if there are any

changes required go back and edit them

and then come back and launch and your

VM is there for you to start working

with in like three or four minutes not

even five minutes within three or four

minutes it gets ready and you can start

working on it

so it's a quick and it's a five-step

process and you should be able to answer

it easily if you have done a few labs in

Azure

let's now look at some scenario based

question you've been posed with a

scenario so we thought through it and we

picked some comment scenario based

questions that are being asked in an

interview and I thought we present it

for you with answers with explanation so

you can get benefitted through it so

let's look at this question you're asked

to make sure your virtual machines are

able to communicate securely with each

other to ensure security or to have good

amount of security what would you do and

the correct and the best answer for this

would be using virtual network in Azure

which enables us to communicate with the

internet securely which enables us to

communicate with on-premises data center

in a secure fashion so the advantage of

using virtual a network is users can

create their own private network users

can pick their own private IP ranges

users can create their own subnet users

can create their own routing between

those two subnets a lot more goes into

that virtual network so it's very

customizable and the users are provided

with an isolated and highly secure

environment for applications it's

completely isolated from other customers

it's completely isolated from other

applications that are running in other

virtual network that we own so within

our account we can have multiple virtual

networks and one application running on

a virtual machine is completely isolated

from other applications running on other

virtual machines and of course all

traffic stays within the azure network

as your virtual machine or within the

azure Network depending on how you setup

the routing if they have set up a

routing to go or reach the internet it's

gonna go otherwise it's gonna stay with

them as your if you have set up routing

to reach on-premises then it's gonna go

and reach on-premises otherwise it's not

gonna go and reach on-premises it's

gonna stay within the azure and it also

allows users to design their own network

like we already discuss picking up IP is

picking routing you know picking subnets

you know how many servers should be

present in that

particular subnet or how many servers

should that subnet accommodate the size

of the subnet the IP ranges the natin

the masking of IPs creating of VPN all

that's possible with the virtual network

so it really allows users to design

their own network and using virtual

machine is how we secure applications in

the cloud let's look at this other

scenario how do you ensure that every

time a user logs in they are not asked

to re-enter the password as part of

authentication so you really don't want

your users to re-enter the password

every time they log in to a different

application well all the applications

have their authentication mechanism in

place all of them wants to authenticate

the user before they log in ensuring the

user does not log in every time does not

mean that no wiping away all the

authentication and authorization that's

present in that application you still

need that in place but how do you make

the user hassle-free so they're not

asked to re-enter the password or the

same password again and again let's look

at the options available the first one

is to enable Microsoft account

authentication well it's not gonna fix

because with that the user will still

need to re-enter the username and

password I deploy Express route it's not

gonna fix either because Express route

is a network level service that connects

on-premises to the cloud so that has got

nothing to do with prompting or not

prompting for password and then we have

set up VPN between on-premises data

center and as your set up ad domain

controller in VM and implement

integrated windows authentication well

you can use the same username and

password for on-premises and the cloud

but this set up the VPN and the ad

controller setup it's not gonna stop you

asking for repeated passwords so this is

all about using the same password in

on-premises and in the cloud and this

has got nothing to do with not prompting

the user to re-enter the password

alright that's same password is

different from not prompting the user to

reenter the password they are two

different scenarios so

that is also out of the equation and the

last one is configured ad sync to use

single sign-on that's the right one so

when we configure the ad to use a single

sign-on then it's going it's not gonna

ask for the username and password every

time we access an application because we

have logged in and that login is gonna

stay active for like 24 hours or so

depending on how you configure it and

within that time you can access a lot of

other applications and it's not gonna

ask for the username and password

because you already have a single

sign-on and you have signed in using the

right credentials let's look at this one

you need to ensure that virtual machines

remain available while migrating to

Azure what would be the appropriate

service to use right let's look at the

options traffic manager traffic managers

is literally and DNS service and then

let's look at the other one update

domains it again has to do with traffic

manager updating the URL so now the

traffic manager gets updated and then

starts sending a request to that

particular URL it's gonna take some

downtime because when you update the URL

they will have to be populated to all

different places and it takes time so

within that time any user trying to

access it's gonna fail and then we have

Express route and cloud services Express

route could be the in fact it's the

right answer because Express route it's

an extension of your on-premises and

cloud environment and in this question

it really comes out from a customer

who's having n hybrid environment so

they have applications running in

on-premises they have applications

running in the cloud and they want to

have a way to migrate obligations from

on-premises to the cloud in other words

kind of do a cut over between on

premises and the cloud and this Express

route is a service that connect between

on premises and the cloud so when you do

the cut over the traffic is now sent to

the cloud instead of being handled in

on-premises in fact the services and the

application is getting down are getting

shut down in on-premises so the request

will come in the same pattern instead of

there being handled in on-premises they

are now routed to the cloud using

Express route and the

API calls get addressed or the the

queries gets answered in the cloud

through the express route service look

at this question you are an

administrator for a website called web

game and you are required to validate

and deploy changes made to your website

by your development team with minimum

downtime so the real question is how do

you validate the deployment changes

that's made by the development team

let's look at the options create a new

linked resource

create a staging environment for the

site enable remote debugging on the

website and then create a new website

well why would you want to create a new

website just to validate the changes and

doing a remote debugging is not gonna

help

because debugging only captures logs of

the changes happening it does not do

anything with validating the changes

create a staging environment could be or

is the right answer because when we have

staging environments anything that we

run on production can be run on staging

environment and any failures that would

happen in production if we simply run it

in production can be captured when we

run the application in the staging

environment so that way staging

environment is a very helpful and useful

service and that way I can catch any

errors in other words I can validate the

changes that were done by my development

team before I move it to production and

that reduces the downtime in the

production environment look at this one

last question that we have for you it's

a standard ter application is used

across the world and uses as your

website standard tier it uses large

amount of image files so you can get it

this could be an e-commerce website

which has a lot of pictures in it and

this is causing the application to load

slow how can we handle this situation

let's look at the options given config a

blob storage with custom domain

well this application has pictures but

the pictures only the pictures is not

all that the application has right so

configuring blob storage might not help

this could be an very interactive

website and that can't be run from blob

storage let's look at the other options

configure as your website auto scaling

to increase instance

at high loads now it's the picture

that's causing issues for the website

it's not the CPU or it's not the memory

unavailable memory not enough that's

causing the application to be slow so we

need to identify what's causing the

application to be slow so it's not the

CPU it's not the memory so configure as

your for auto scaling is not gonna help

and then what are the other options

let's see configure as your CDN to cache

all responses from the applications web

endpoint a CDN could be the right answer

but look at that it says a CDN to cache

all responses from the applications web

endpoint Sirian is not designed for that

though it can do it that's not the best

way to use CDN to capture all responses

from the applications web endpoint the

proper design for CDN would be to cache

the frequently used once in other words

cache the static content which are

photos videos logos and pictures and lot

more in a static content that never

changes let's look at the last option

configure as your CDN to cache site

images and content store in Azure blob

storage absolutely right so here we will

have to redesign the application to

store the pictures high quality lazy

loading or slow loading pictures because

of the high quality and the bigger size

so store them in CDN and then the

content let it be stored and as your

blob storage that's the right way of

designing the application and if we do

it this application is going to run

faster or the application is gonna

respond faster to the users that's all

we had for this video it looked like we

just started and here we are after

reviewing some 25 classic interview

questions and now you are one step

closer to cracking that as your

interview all the very best everyone we

appreciate the time and effort that you

put in learning new technologies and we

are very glad that we are able to help

you with such videos hope to see you

again in another video like this thank

you

hi there if you like this video

subscribe to the simple learn YouTube

channel and click here to watch similar

videos to nerd up and get certified

click here