New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Nutanix NCP-DB Exam - 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.


by Pearly at Jul 11, 2024, 01:26 PM

Limited Time Offer

25%

Off

Get Premium NCP-DB Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Barrett
3 months ago
C is just too late; it won't meet the requirement.
upvoted 0 times
...
Carissa
3 months ago
A snapshot at 9PM won't get you fresh data by 9:30PM.
upvoted 0 times
...
Lorean
3 months ago
Wait, can we really do a snapshot at 99M? Sounds odd.
upvoted 0 times
...
Cora
4 months ago
I disagree, D is more straightforward for a 9:30PM refresh.
upvoted 0 times
...
Lashawnda
4 months ago
Option B seems like the best choice for near real-time data.
upvoted 0 times
...
Emilio
4 months ago
I feel like option D is too late since it schedules the snapshot at 9:30 PM. Wouldn't we want to capture the data before that time?
upvoted 0 times
...
Markus
4 months ago
I’m a bit confused about the difference between snapshots and log catchup. I thought snapshots were for backups, but maybe they’re also for refreshing data?
upvoted 0 times
...
Winfred
4 months ago
I remember practicing a similar question where timing was crucial, and I feel like scheduling at 9:30 PM might be the best way to ensure the data is fresh.
upvoted 0 times
...
Cherelle
5 months ago
I think option B sounds familiar, but I'm not entirely sure if the 99M snapshot is the right choice for a daily refresh.
upvoted 0 times
...
Gladys
5 months ago
I'm not totally sure about the difference between a snapshot and a log catchup. Can someone clarify which one is better for this scenario? I want to make sure I select the right answer.
upvoted 0 times
...
Fabiola
5 months ago
Okay, I've got it! The key is to schedule the snapshot as close to 9:30PM as possible, so Option B with the 15-minute log catchup seems like the best way to achieve that. Nice!
upvoted 0 times
...
Derick
5 months ago
Hmm, I'm a bit confused by the wording of this question. Is there a difference between scheduling a snapshot at 9PM versus 9:30PM? I'll need to think this through carefully.
upvoted 0 times
...
Kayleigh
5 months ago
I think the best approach here is to schedule an SLA policy that performs a snapshot at 9:30PM, as that will give us the most up-to-date data possible. Option D seems like the clear choice.
upvoted 0 times
...
Desirae
5 months ago
This one seems straightforward - the issue is likely co-channel interference between MAP-1 and MAP-3 talking to RAP-2.
upvoted 0 times
...
Gladys
2 years 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
2 years ago
I'm surprised option A is even an option, 9PM is way too early to get the latest data.
upvoted 0 times
...
Vince
2 years ago
Option C is out of the question, log catchup alone won't give you the freshest data.
upvoted 0 times
Trevor
2 years ago
B) Schedule an SLA policy that performs a snapshot at 99M and log catchup for every 15 min.
upvoted 0 times
...
Rhea
2 years ago
A) Schedule an SLA policy to perform snapshot everyday at 9PM.
upvoted 0 times
...
...
Judy
2 years 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
1 year ago
Yeah, option D is definitely the way to go for refreshing the database at the closest time possible.
upvoted 0 times
...
Ollie
2 years ago
I agree, scheduling the snapshot at 9:30PM seems like the most efficient option.
upvoted 0 times
...
Kris
2 years ago
Option D sounds like the best choice. The data will be really fresh that way.
upvoted 0 times
...
...
Paz
2 years 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
1 year 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
1 year ago
B) Schedule an SLA policy that performs a snapshot at 99M and log catchup for every 15 min.
upvoted 0 times
...
Lasandra
1 year ago
A) Schedule an SLA policy to perform snapshot everyday at 9PM.
upvoted 0 times
...
Dannette
1 year ago
Maybe we should consider the trade-off between getting the latest data and the log catchup overhead.
upvoted 0 times
...
Kayleigh
1 year ago
Yes, but it might result in a lot of log catchup overhead.
upvoted 0 times
...
Emile
2 years ago
Option B is the best choice for getting the latest data.
upvoted 0 times
...
...
Jerry
2 years ago
I think option A is not the best choice because it schedules the snapshot too early at 9PM.
upvoted 0 times
...
Yvonne
2 years 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
2 years ago
I agree with Beatriz, option D seems like the most efficient way to achieve the requirement.
upvoted 0 times
...
Beatriz
2 years ago
I think the best way is to schedule an SLA policy to perform snapshot everyday at 9:30PM.
upvoted 0 times
...

Save Cancel