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

Nutanix NCP-DB Exam - Topic 1 Question 1 Discussion

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

When trying to restore a database via Time Machine (TM), the option to restore data to a Point in Time is not available.

What should the administrator do to enable Point in Time Recovery?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Long
3 months ago
Manual snapshots are a good fallback, but not ideal for this.
upvoted 0 times
...
Alexis
3 months ago
Wait, is it really that simple?
upvoted 0 times
...
Avery
3 months ago
I thought updating the TM schedule would work too?
upvoted 0 times
...
Janessa
4 months ago
Totally agree, that's the way to go!
upvoted 0 times
...
Margo
4 months ago
You need an SLA that supports Continuous Log retention for Point in Time Recovery.
upvoted 0 times
...
Aretha
4 months ago
I'm leaning towards option D with the Brass SLA, but I feel like I need to double-check what the Log catch up frequency actually does.
upvoted 0 times
...
Lucia
4 months ago
I practiced a similar question where taking a manual snapshot was mentioned, but I don't think that's the main solution here.
upvoted 0 times
...
Raylene
4 months ago
I think updating the TM schedule might be the right approach, but I can't recall if that directly relates to enabling Point in Time Recovery.
upvoted 0 times
...
Noe
5 months ago
I remember something about SLAs and Continuous Log retention being important for Point in Time Recovery, but I'm not sure which option it was.
upvoted 0 times
...
Asuncion
5 months ago
The question mentions Time Machine, so I'm guessing the solution has to do with updating the TM schedule. I'll try option B.
upvoted 0 times
...
Tesha
5 months ago
Based on the question, it seems like taking a manual snapshot might be the best approach. I'll go with option C.
upvoted 0 times
...
Georgiann
5 months ago
I'm a bit confused on the difference between the SLA and TM schedule options. I'll need to review those details.
upvoted 0 times
...
Carlton
5 months ago
Hmm, this is a tricky one. I'll need to think carefully about the options here.
upvoted 0 times
...
Beatriz
5 months ago
Okay, let's see. I think the key is to enable continuous log retention, so I'll go with option A.
upvoted 0 times
...
James
5 months ago
Okay, I've got this. A data transform can be used to display the same data on multiple user views, and it can also be used to convert integer data to text data. Those are the two requirements I'll select.
upvoted 0 times
...
Marilynn
5 months ago
I'm a little confused by the wording of these answer choices. They all sound similar to me. I'll have to re-read the question and options a few times to make sure I understand the differences.
upvoted 0 times
...
Edmond
5 months ago
The time period for the response is an important detail, so I'll make sure to double-check my answer before submitting. I think A is the most likely correct option, but I'll review the scenario one more time to be sure.
upvoted 0 times
...
Vanesa
5 months ago
Hmm, I'm a bit unsure about this one. The question mentions a change in scope, so I'm wondering if the configuration management system might also be involved in reviewing the changes. I'll have to think this through carefully.
upvoted 0 times
...
Paris
2 years ago
Using Brass SLA and updating the Log catch up frequency may be necessary for enabling Point in Time Recovery.
upvoted 0 times
...
Katy
2 years ago
Taking a Manual snapshot and using it for DB recovery is also a valid option.
upvoted 0 times
...
Shalon
2 years ago
Another option could be to update the TM schedule to perform DB Log catch up.
upvoted 0 times
...
Norah
2 years ago
I agree with Lourdes. Continuous Log retention would allow for Point in Time Recovery.
upvoted 0 times
...
Lourdes
2 years ago
I think the administrator should use an SLA that supports Continuous Log retention.
upvoted 0 times
...
Alexia
2 years ago
Using Brass SLA & updating the Log catch up frequency could be another option.
upvoted 0 times
...
Melvin
2 years ago
But what about updating the TM schedule to perform DB Log catch up?
upvoted 0 times
...
Wade
2 years ago
I agree with User1, Continuous Log retention can help enable Point in Time Recovery.
upvoted 0 times
...
Sage
2 years ago
I think the administrator should use an SLA that supports Continuous Log retention.
upvoted 0 times
...
Ryan
2 years ago
Well, if it's on the exam, we'd better take it seriously. I'm going to go with option A. Continuous log retention sounds like the most reliable way to ensure we can restore to a specific point in time if needed. Gotta cover all our bases, you know?
upvoted 0 times
...
Colene
2 years ago
Okay, so the question is saying that the Point in Time Recovery option is not available when trying to restore a database from Time Machine. That's a bit of a head-scratcher.
upvoted 0 times
Adelina
2 years ago
User4
upvoted 0 times
...
Albina
2 years ago
User3
upvoted 0 times
...
Lorean
2 years ago
User2
upvoted 0 times
...
Rosalind
2 years ago
User1
upvoted 0 times
...
...
Roxanne
2 years ago
Hold up, are we talking about Time Machine here? I thought that was just for my Mac to back up my cat photos, not for enterprise databases. This is getting complicated!
upvoted 0 times
Sherell
2 years ago
No, we should use Brass SLA and update the Log catch up frequency.
upvoted 0 times
...
Val
2 years ago
Should we also update the TM schedule to perform DB Log catch up?
upvoted 0 times
...
Muriel
2 years ago
That makes sense. It ensures we have all the necessary logs for recovery.
upvoted 0 times
...
Alayna
2 years ago
To enable Point in Time Recovery, we should use an SLA that supports Continuous Log retention.
upvoted 0 times
...
Sherell
2 years ago
I didn't know Time Machine could be used for databases too.
upvoted 0 times
...
Muriel
2 years ago
Yes, we are talking about using Time Machine for database recovery.
upvoted 0 times
...
...

Save Cancel