Welcome back. In this lesson,
we are going to talk about "Optimizing Resource Management".
And I'm just going to be upfront with you right
at the start, this is going to be kind of a weird lesson,
at least as far as the DP-203 is concerned.
See, there's a few topics in the exam requirements
that don't really tie to much of anything.
They're very vague.
So some are extremely clear,
like we need to figure out how to set up distribution.
Okay, well, I can teach you that.
But some of the things like this
are rather obscure or vague.
And so for the DP-203, there's not going to be
a ton of practical application,
but it is important because it is included
in the exam requirements.
So with that, I'm going to give you a few optimization tips
for your Azure environment.
All right. Number one, use ARM templates.
ARM templates are really helpful
because they help us to replicate our resources very fast.
We have our blueprint for how we made
all of the different resources in our environment.
It also helps to give us some control,
because there's something that we can go back with
and we can use to audit and figure out exactly
what we're building and why,
and build some continuity between multiple groups
building resources in Azure.
Second, don't put everything in the same subscription.
I've said this a couple of times,
but it is a very important point.
You don't want to have everything
in the same subscription because, one, defense in depth.
If everything is in the same subscription
and someone gets one of your admin accounts, you're done.
They have access to everything.
If you've built multiple subscriptions,
then they only have access to that 1 subscription.
Or it could be built on dev and production.
So if the dev environment is compromised,
you're still okay in the production.
So don't put everything in the same subscription.
The second reason is compliance.
A lot of times, there's regulatory requirements
for how data is stored in your environment,
and the separation that needs to be there for that.
So make sure that you're looking at compliance as well.
Third is management.
If you built up subscriptions in an appropriate way,
it's going to be easier
for you to manage your environment as well.
Third, Azure Advisor. Hey, this is a must-use.
And since we haven't actually
talked about Azure Advisor all that much,
or really I think at all in this course,
I'm going to actually jump into the portal,
and we're going to take a look at Azure Advisor
and how it functions.
So let's just go ahead and do that,
and I'll explain what it is as we go.
So here we find ourselves in the Azure portal,
and let's just go ahead
and open up my Synapse workspace that we've been looking at.
And you can see here, in our Synapse workspace,
if I scroll down under Monitoring,
there is Advisor Recommendations.
This is something that you should be
periodically looking at.
It's going to be very helpful,
and it's going to highlight anything
that you have wrong in your environment,
or ways that you can optimize as well.
Now, we can access Advisor
not just by going to the resource that we're interested in,
but we can also search for Advisor,
and I can go to it here.
And this will pull up Advisor
about my entire environment.
And so if I want to see,
you can see I have a couple of
different recommendations here.
If I clicked on that, it pulls up and it gives me
a little bit of information on what's going on.
So it wants me to add a policy to
audit VMs that don't use managed disks, right?
Now, for my case, I don't really care.
This is for a course that's going away.
So all of this environment's going to go away here.
So it's not a huge concern because I'm not really using VMs,
but it's something worth reading through.
Also, enforce inherit a tag from the resource group.
We've talked about how important tagging is.
If this was a real production, or even a dev environment,
this would be something I'd want to look at.
So make sure that you're looking at Advisor,
that's going to be very helpful for you
as you move forward in your career.
With that, let's do just a couple of key points
to remember to close this out.
First, think holistically.
We've talked about this in the course.
All of these concepts should blend together
into 1 large picture of data management.
So thinking about your ARM templates,
that's an important piece of data management.
Thinking about your security,
data management, that's importance.
So thinking about all of those different components,
and not just the data is going to help you
be a better data engineer.
Next, for the DP-203, assume a very small application.
This is something that's going to be helpful
for you to have a background on.
It's helpful because it was included
in the exam requirements,
but I wouldn't spend a whole lot of time here,
because I'm not expecting
a whole bunch of questions on the DP-203.
So with that, let's stop talking,
and I'll you see in the next video.