Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Nutanix Exam NCP-DB Topic 5 Question 14 Discussion

Actual exam question for Nutanix's NCP-DB exam
Question #: 14
Topic #: 5
[All NCP-DB Questions]

An administrator is asked to refresh a database everyday at 9:30PM with data from as close to the refresh time as possible.

What is the best way achieve this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: D

. This is because it allows the database to be refreshed at the exact time specified (9:30 PM) with the most recent data. The other options either perform the snapshot before the desired time or do not specify when the snapshot would occur. Please note that the exact answer might depend on the specific database system and its capabilities. Always refer to the database's documentation for the most accurate information.


Contribute your Thoughts:

Gladys
4 months ago
Option B is the way to go, unless you want to be doing log catchup all night long. It's like trying to catch a moving train, but with databases!
upvoted 0 times
...
Queen
4 months ago
I'm surprised option A is even an option, 9PM is way too early to get the latest data.
upvoted 0 times
...
Vince
4 months ago
Option C is out of the question, log catchup alone won't give you the freshest data.
upvoted 0 times
Trevor
3 months ago
B) Schedule an SLA policy that performs a snapshot at 99M and log catchup for every 15 min.
upvoted 0 times
...
Rhea
4 months ago
A) Schedule an SLA policy to perform snapshot everyday at 9PM.
upvoted 0 times
...
...
Judy
4 months ago
I'd go with option D, scheduling the snapshot at 9:30PM. That way, the data will be as fresh as possible.
upvoted 0 times
Lauran
3 months ago
Yeah, option D is definitely the way to go for refreshing the database at the closest time possible.
upvoted 0 times
...
Ollie
3 months ago
I agree, scheduling the snapshot at 9:30PM seems like the most efficient option.
upvoted 0 times
...
Kris
4 months ago
Option D sounds like the best choice. The data will be really fresh that way.
upvoted 0 times
...
...
Paz
5 months ago
Option B seems like the best way to get the latest data, but wouldn't that result in a lot of log catchup overhead?
upvoted 0 times
Izetta
3 months ago
Option B might have some overhead, but it ensures the data is as close to the refresh time as possible.
upvoted 0 times
...
Matthew
3 months ago
B) Schedule an SLA policy that performs a snapshot at 99M and log catchup for every 15 min.
upvoted 0 times
...
Lasandra
3 months ago
A) Schedule an SLA policy to perform snapshot everyday at 9PM.
upvoted 0 times
...
Dannette
3 months ago
Maybe we should consider the trade-off between getting the latest data and the log catchup overhead.
upvoted 0 times
...
Kayleigh
3 months ago
Yes, but it might result in a lot of log catchup overhead.
upvoted 0 times
...
Emile
4 months ago
Option B is the best choice for getting the latest data.
upvoted 0 times
...
...
Jerry
5 months ago
I think option A is not the best choice because it schedules the snapshot too early at 9PM.
upvoted 0 times
...
Yvonne
5 months ago
I'm not sure, but I think option B could also work because it includes log catchup every 15 minutes.
upvoted 0 times
...
Lanie
5 months ago
I agree with Beatriz, option D seems like the most efficient way to achieve the requirement.
upvoted 0 times
...
Beatriz
5 months ago
I think the best way is to schedule an SLA policy to perform snapshot everyday at 9:30PM.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77