Alone we'll come back with one more lecture on the ideas practice questions.
What are these future that will allow you to restore your database within five minutes of a specific
day time during that interim period.
So let's say one of your administrators by mistake he removes part of the database or the server failed
or you had the automated backups available.
And Id like to restore in those because you had a problem with the main instance.
So what you have is are these future relate to the story that is within five minutes of a specific date
time doing that engine.
A.
It is.
Are these multi easy features.
The Multi is the feature will give me high availability not restore.
There would be a primary and a standby.
And if the primary fails or this will direct all the reads and writes in a standby.
So this is not the restore part.
Be it obvious are the manual snapshots you can cannot do.
I mean deciding that you would like to restore to within five minutes of a specific incident or event
or date and time.
That means you are doing exactly your point in time the restoration or point in time recovery and maintenance
not shots can not help you with that.
They are not used for point in time recovery.
Yes.
Are these three replicas the replicas are two key.
If I have a primary standby or even a standalone are to kill that need operations that need performance.
So this is irrelevant in my case.
The ABs are the point in time recovery as a feature utilizing are these automated backups and transaction
logs.
And this is exactly what it is.
I can only do up to five minutes in time recovery of Restore of a database if I have the automated backups
and the transaction logs.
So basically the transaction logs will be applied to the automated backup snapshot that makes the most
sense for that specific date and time or five minutes and then you can recover that.
And if that is within the retention period you can even do better than that.
You can do up to a few seconds.
So that's the accuracy you can do.
You can say that I want to recover it to Thursday to 15 and 35 seconds P-A.
So that's how granular you can go if you you're within the detention period as well.
So is incorrect is incorrect see is incorrect and the is the correct answer.
A refresher.
You can specify a point in time restore to any given second during the retention period.
And when you initiate a point in time recovery or store the transaction logs the database transaction
logs are applied to the most appropriate daily backup.
Remember when you said that automated backups are done once every 24 hours on a daily basis to restore
your database to that point in time when you restore a database instance only the default database parameters
and security groups are associated with is restored instance so you will not get everything.
So you need to do manual customization or just copy a configuration again once that is you need to associate
apply the custom on the custom database parameters and security group settings right.
Next question is are these automated backups and data be snapshots.
For my sequel database engine are currently supported for which storage engine.
And this is again one of the questions that you need to know the answer to and it is wrong.
Oracle I assume it's not my ICM although my ass I mean supported but there are issues when you try to
restore from my eyes.
Correct.
My sequel.
Monk.
So the correct answer is C.
And again this is something that you need to know about this idea so azing correct me is incorrect C
is correct.
This is incorrect and your correct answer is C refresher for this question.
Automated backups are currently supported only for the storage engine for my sequel and not for my sim
engine.
The point in time restore and snapshot restore features of a sequel are supported for that you need
to be a storage engine.
Only although my sequel supports multiple storage engines including my sem not all of them are optimized
for crash recovery and data ability we need to restore.
We would like to do to retain the data properly and to be able to do a recovery from a crash to the
database in a to b is the recommended and supported storage engine for my sequel data with instance
on Amazon Ardis next question does a charge for launch.
But idle our DSD instances so if you have launched data with instances and you're not using them they
are not in production they're not being tested they're not.
There is nothing happening on them.
Would you be charged for that.
A This will be treated like stop two instances so no charge.
B depends on the region and they are Diest that every instance is launched into C only if it was launched
in the government cloud.
Yes you will be the yes you will be charged regardless and that is the correct answer.
It's not like you see two instances when you stop it you don't pay for it.
As long as it is launched it is not terminated and it is then you are paying for it.
So is wrong is wrong seems wrong.
The is the correct answer.
Next question which licensing types are available on E.W. as our ideas for Oracle database engine.
So if you want to bring Oracle or you want to use Eric Oracle from E.W. us what are the licensing options
that they have.
Do I have to get it from me.
Yes.
Do I have to bring licenses a roll based license and license included license included is correct.
Because if I'm going to take it from E.W. us but through all brazed license is wrong.
So the quick answer is zonk be bring your own license and enterprise license.
The first one is correct.
Then the second half is wrong.
And again these are facts.
You know it or you don't not see Bring your own license and license included.
This is correct.
And these are the two licensing models are licensing options available for Oracle on either of us public
clouds the enterprise license unless it's included the phone is correct.
This one is wrong.
That's why the over all is wrong and the correct answer is C
next question how will it w s r d s ensure a seamless fill over to the standby database instance in
an RDF multi easy deployment deployment.
If the primary instance fails many will feel over is initiated.
So if you have a multi easy deployment primary and standby The question is how can it.
Are these servers ensured a seamless spillover from the primary to the standby due to a primary that
is instance failure or manual feel over is initiated.
So either it is manual or automated.
How can that be done seem as seamlessly such that the application or applications access to these databases
will not be stopped or impacted.
So if there was an application or applications accessing the data through the primary.
Now how can we as our audience do they feel over such that the application access to the database although
it's going to be from the standby the application will not see any difference that has happened during
the fall over from the primary to stand by and the application access database will continue and you
need to choose to answers a day that his audience will have an internal IP which will read direct requests
to the new data.
So this is talking as if the R S is an L B that will have an IP address.
The application will point to that IP address and then it will either go to primary or secondary.
This is not how it works.
So this is wrong.
Be intelligence already relies on DNS to switch over to the standby seamlessly.
This is correct although not fully explained in this option but that's correct.
And basically what it does is it points to the endpoint of the Multi is the audience intimidation and
the end point is the same for the primary and stand.
However the end point when the primary is up the audience will populate the DNS entry for the end point
to point to the IP address of the primary if the primary fails over to the secondary then it will that
the community can name or the seen him record in the DNS will point Ardelia's will change it to point
to the secondary instance or the Stand by instance and not the primary see it up here.
Our audience will have both primary and standby and independently switch over must be done manually.
Of course this is not what we learned for what we know about our audience.
We know that they are in primary standby and there is a continuous synchronization and the primary will
be the source of reads and writes the standby it is not for read or write until a field over happens.
So they're not running independently at all and that's why the answer is wrong.
The scene him or the canonical name record is updated from primary standby.
Basically they're seen in record in the DNS will point initially that the endpoint will map to the IP
address of the primary when the switch over happens then it will point to the IP of the.
Exactly standby.
So be is correct so the correct answers are D and D quickly official for the scope doing feel over the
scene seam of the audience that instance is updated to map to the stand by IP address instead of the
primary IP address.
This is why it is always recommended if you want the application not to be impacted or affected that
the applications must point to the end point of the database and not to the IP address of the primary
or standby.
But if you point if the application points to the IP address will it work.
Yes but if a film ever happens you need to go into the application and change the IP address to be done
by IP address the name does not change because the audience is in point does not change.
However the mapping to the IP address changes.
Right so last question our audience your client has a global presence with offices all over the world.
So your client has offices all over the world all connected built in different regions.
ASL is tracking three tier application is used in every region leveraging multi Izzi my secret RDL database
instances the client has a requirement to build an analytics based reporting application in the HQ region
that will need to do intensive queries to the regional databases to collect information and generate
reports.
So what are we saying.
This is a long story now.
So we have multiple regions and this company is a global company it has a headquarter that is deployed
in the region but also has different regions across the globe where they have a sales tracking or a
sales reporting three tiered application.
Okay could be that data entry is happening all the time on the web layer of the application and then
stored in the database.
Anyways I have here my sequel multi that is in every region.
So I have primary standby in every region and every region is responsible for collecting its own information
fine.
So what do you need to do now.
I need to run analytics reporting application and the application needs to intensive to do intensive
reads queries to the different regional implementations of the database collect information out of them
and then generate reports to the top or the higher management in the headquarter the gushingly Humvee's
How can you architect the database access database access and the analytics to to query a database such
that the original database performance is not impacted.
Now I have other applications may be happening here and querying the database locally.
Now I don't want these to be impacted by the intensive queries.
I will do by the analytical analytics for application.
The solution is cost effective and the reports can be done quickly.
So these are the requirements in place the sent by instance for each region in the HQ region.
I cannot do that because we know that the primary and standby for a multi is the database or are the
US must be in the same region different availability zones.
We create our snapshots and save them in an S3 bucket in the HQ region.
So here they are talking about manually creating snapshots of the database and saving them in an as
three.
But the question is if you have the snapshots What can you do with them.
You're not going.
Each time you want to restore from a snapshot you are creating and you that is instance and if you do
that hourly It wouldn't make sense that I'm going to create 24 instances of the 24 hour snapshots that
I'm going to take hourly every day.
So this is nonsense and that's why I will rule this one out as well.
See.
Use Google dial connect lengths to connect all regional sequel deployments to the HQ region and run
the database queries over DX links.
So is suggesting that you create direct connect links from the HQ to every single region globally which
is heaps and heaps of money.
It is very very very expensive.
And then use the direct connect links to query that.
So this one has two problems.
The first problem is the region and that there is performance will be impacted because I'm quitting
doing that intensive queries on the database itself and also is not cost effective.
So I am losing two of the requirements that I am going to rule this one out.
Let's look at the for each region.
Create across the region the replica in the HQ region.
So from each region since you have primary in standby create a replica from each region into exactly
into the headquarter region.
So that becomes makes it very close to the HQ analytics application so that can quickly query the databases
locally.
And these are really replicas so I'm not impacting the original or the original performance of the databases.
It is cost effective because I'm creating only there because now and it can be done quickly.
So compared to the other options this one seems to be the one that makes perfect sense.
So Jerry's analysis is wrong be wrong seems wrong and D is the correct answer.
All right.
So remember that read replicas are very handy when you are talking about cross the gender application
when you are talking about Diyar and you want your analytics application to do quitting intensive quitting
grid operations on the database and you don't want the death of Jesus to be impacted version of the
beast to be impacted.
All right so that brings us to the end of the audience examplar difficulty level practice questions
and I hope now RLDS is much easier for you.
This practice had grouped a lot of ideas that you might see in the exam or you might see very close
ideas in the exam and I think we have covered the full nine yards.
Whichever you answered try to associate that you are doing that requires our D.S. competency I think
you have reached a very high competency level by doing this practice which is very important.
OK so until we meet in the next section please be safe and I will see then.