Helen will come back more of the US practice questions.
And here is another one why doesn't your support increasing the Ardis database instant storage for Microsoft
sequel server.
There is no one limitation.
And because of which we cannot do that.
How about the other ideas of the big engines.
Can we increase the storage.
Yes you can.
So what are the answers.
A Microsoft sequel server is not a native.
It obviously there is engine.
Thats why I would vote against it.
Why.
Because Oracle is not native us equal is not only native E.W. us but they you support it b because of
the extensibility limitation of striped storage attached to the Microsoft Windows Server and that is
that documented known reason See this is not correct.
You can increase storage on Microsoft sequel server or this instance and this is wrong.
There is no documented limitation.
There is.
So the correct answer is B.
Next question your junior sit administrator is wondering if it is possible to downsize the RDA.
Did it be instant storage.
After it was launched.
So you have launched an idea that is instance and lets say it has one terabyte of storage can you.
After you launched it can you bring it down to let's say 500 gigabytes instead of one terabyte answer.
The database engine is what determines that.
And this is wrong.
B It is possible for my secret but not for other engines.
And again this is wrong.
See it is not possible to scale storage down you can only scale it up.
And this is the correct one so this is again and this is not a tweaked question or anything.
This is something you need to know that it was already a service will not allow you to scale down or
downsize the storage that you have.
You can keep it as is when you create when you create the instance you can scale it up if you want.
And if you need to but you cannot get it done the audience does not allow changing the size at all after
that instance launch.
This is partially true.
You cannot change it down but you can change it up.
So thats why I see it is the correct answer.
Next question one should I choose provision IOPS over standard.
Are the US storage so you have in the abs you know that the US use on the ABS does not use instant stores
so if you have a question in the exam that challenges you which US which block storage that you can
use with the R D s instances and one of the choices is instant store 100 percent it is not one of the
options.
So you need to focus on the remaining options of the of the answers or the multiple choices but the
instant store is deaf and cannot support.
The question is straight asking you can use instant store volumes with obvious instances.
So the answer is an absolute no.
It's non-supported.
So Tony yes but you know the ABS has general purpose has the provision IOPS and has the magnetic among
other types.
Right.
So here's the question is when should you prefer to choose provision IOPS over the standard audio storage
over this one or this one.
A for batch oriented workloads so batch processing be for workloads that are not sensitive to consistent
performance which is I mean this one is wrong.
This one is wrong.
Why.
Because provision IOPS will provide consistent performance.
So why would you choose it because you don't need that consensus performance doesn't make sense.
See for small workloads smaller to those you can live with the magnetic You can live with a general
purpose.
You don't need the provision types the for production online transaction processing all T-P workloads
and this is the correct answer.
That's the command when we use it for production online transaction processing workloads that require
consistent performance high rate of IOPS.
This is where you need the provision lives.
So C is incorrect ABC are incorrect the is the correct answer and an important refresher for this one
that you need to remember.
Amazon RLDS provision of storage to improve performance.
So use the Amazon Diest provision IOPS to improve performance for any production application that requires
fast and consistent performance with a common provision provision of storage type that delivers fast
predictable and consistent throughput performance.
And it is optimized for online transaction processing workloads that have consistent performance requirements.
So we have workloads.
If the question was different and they said you have an application that requires consistent database
read and write performance and this is a must have requirement what would you recommend as a storage
option for this instance.
And again it becomes the audience if the question asks you that you have an OLTP workload and you are
about to architect a solution that has already passed instances which is volume which storage would
you choose and then Ill give you the magnetic The general purpose there and provision IOPS which one
would you choose.
Okay.
So that same question can be tweaked in different ways but you need to be aware that production workloads
consistent performance and oil T.P. kind of workloads can predictable and fast performance.
All of that is exactly is provisioned.
The next question is it possible for clients to test there are database instances against a new version
before deciding to upgrade.
So now I am at version six point zero for instance of my and my sequel and I would like to go to 6.5
but I have a production and the production is very important to me and I don't want to upgrade.
And then I start finding issues in 6.5 and I have to roll back again to one point to 6 percent.
So is there a way I can somehow test 6.5 and then if I am comfortable that this is what I want and will
deliver they expected then I would go to my production and take that from six point thirty six point
five.
Thats where the question is asking.
In this instance the answer is no.
It is our this is full is a fully managed service and you just need to put a request for it to be asked
to upgrade does that make sense if you think about it doesn't make sense.
So you put in a request and then your old production environed becomes messy because of a bug or because
of inconsistency or because the new version does not deliver what you are expected be.
Yes it is possible.
Create a snapshot off of the existing Ardis instance create a new artist instance of the snapshot then
upgrade the new instance then do testing.
So I have lets say its multis you have my primary production my standby.
So what this is suggesting.
Why dont you go ahead and.
Exactly.
So stand by standby create a snapshot of the snapshot.
Create another Ardis instance that has nothing to do with the primary and stand by the production ones
and of the not when you have the earliest instance in should the request to AWOS to upgrade to 6.5.
OK so they upgrade the instance to 6.5 same instance.
Now do all your testing and and simulated production testing on this instance.
If everything looks fine then you can go ahead and submit a request to upgrade this one also to 6.5
and you can choose.
By the way when you when you want to do any changes to your ideas did it be like you want to upgrade
you want to scale up and all that stuff.
You can choose for that change to happen immediately or you can choose to wait until the maintenance
window when this will will happen.
So you have the choice.
OK so this one looks as feasible and logical doable option.
But lets go through CND.
You need to launch an easy to instance and install the new database engine version test then upgrade
your data.
Are these instances this is not correct because you need to do that on an already managed instance instead.
Instead there might be commonalities but is it 100 percent.
No you need to simulate the same environment on a test bed and then you find out you're testing whether
it passes everything.
And then you can upgrade it.
So this one is wrong.
It is very close.
The No you cannot test before upgrade.
You can test after a grade which doesn't make sense because as I mentioned before if you upgrade and
then you have problems then you have to roll back and you cannot do testing after you upgrade.
Why.
Because we know that it is only 30 minutes for the maintenance window that you have and doing that 30
minutes you cannot do a lot of testing and all that so you are better off doing this and then you can
upgrade
because so a C and D are wrong and B is the correct answer and a quick refresher or two that you can
test a database engine against a new version before upgrading.
You do this by creating a database up shot of your existing data is instance and if it is not easy this
will be created from the standby to avoid suspending.
I was on the primary second step restoring from the database snapshot to create a new database instance
initiating a version upgrade for the new database instance.
And now you have a new version test that you can test and then you can do your test.
You can experiment safely on the upgraded clone of your data instance before deciding whether or not
to upgrade your original production database instance
another question you asked our guest if not otherwise specified will perform Ardelia's instance changes
using the maintenance window the user has the option to select a maintenance window.
So that's a fact.
Now we're sitting in fact now if you launched an arduous instance and did not specify the maintenance
wounded during launch.
When will it be as ready as carry out the required maintenance or implement changes the user requests
to be done.
So what is what.
The question is simply you launched an obvious instance during the launch you have the option to check
to select when your maintenance window is going to be for this or this instance.
You skipped that and you launch the obvious instance.
The question now is if you want to do any changes here and you don't want that to be immediate What
will our ideas do.
Given that you have not specified a maintenance when did you launch a will not allow any updates or
changes until the user configures a maintenance window.
And this is wrong.
B If the user requests any changes or updates AWOS will prompt the user for a maintenance window.
And again this is not how it works.
See the user must terminate the previous instance and launch a new one and specify during the launch
of the new one the desired maintenance window.
Frank this will select the default maintenance window if not specified by the user and that's the one
that makes the most sense.
Why do you need to rip apart your are instance just because of a change window.
And it's not going to prom.
Q When you do the change it will ignore the fact that he did not specify.
I mean a maintenance window and there is a default depending on the region depending on where you launch
that instance there will be a default maintenance window that it will pick it up for you and will do
your changes during that.
And that's the one that makes the most sense.
So it is incorrect because incorrect is incorrect and the is the correct answer.
Refresher every instance has a weekly maintenance window and that could be also a question maybe more
to the office but you never know maybe charge up the maintenance window for you.
Are these instances that you launch in any region in a VPC is weekly daily hourly monthly or yearly.
Which one is the right one.
Exactly.
It's a weekly maintenance window.
If you did not specify one at the time you create that it would be instance it will choose one randomly
for you and that's 30 minutes long.
1.
All right so let's take a break and we'll continue on.
Don't go anywhere please.
We'll continue on with more.
Yes.
Practice questions because practice makes perfect.
And I'll see you in the next election.