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-MCI Exam - Topic 6 Question 15 Discussion

Actual exam question for Nutanix's NCP-MCI exam
Question #: 15
Topic #: 6
[All NCP-MCI Questions]

An administrator needs to limit the amount of storage space that data stored in single container can consume.

Which action should the administrator take?

Show Suggested Answer Hide Answer
Suggested Answer: C

The storage policy value that can be inherited from a cluster is Compression. In the Nutanix Multicloud Infrastructure (NCP-MCI) 6.5, compression is a storage optimization feature that can be configured at the cluster level and inherited by all the entities within the cluster. This feature helps in reducing the storage footprint by compressing the data before writing it to the disk. The other options like IO performance, Storage Container, and QoS are not inherited from the cluster. They are configured and managed separately for each entity as per the requirements.


by Page at Jul 14, 2024, 07:47 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Denny
3 months ago
B is definitely the most straightforward option here.
upvoted 0 times
...
Keva
3 months ago
Wait, can you really limit storage with D? Sounds odd.
upvoted 0 times
...
Marg
3 months ago
A doesn't really limit storage, just rebuild capacity.
upvoted 0 times
...
Joanna
4 months ago
I disagree, C is better for managing snapshots.
upvoted 0 times
...
Lang
4 months ago
B is the way to go! Set that advertised capacity.
upvoted 0 times
...
Margery
4 months ago
I recall that storing VM snapshots separately can help with management, but it doesn't directly limit the container's storage. So, I don't think C is the answer.
upvoted 0 times
...
Lashaunda
4 months ago
I practiced a similar question where we had to manage storage limits. I feel like enabling reservations could be relevant, but I'm leaning towards B as well.
upvoted 0 times
...
Mohammad
4 months ago
I'm not entirely sure, but I remember something about thick provisioning potentially wasting space. That might not be the right choice here.
upvoted 0 times
...
Beckie
5 months ago
I think the answer might be B, setting an advertised capacity for the container. It sounds like a way to limit storage.
upvoted 0 times
...
Amie
5 months ago
I'm a little confused by the wording of the question. Is the administrator trying to limit the storage space for the entire container, or just for the data stored within it? I want to make sure I understand the problem correctly before selecting an answer.
upvoted 0 times
...
Kenneth
5 months ago
Okay, let me think this through. If the goal is to limit the storage space in a single container, then setting an advertised capacity for the container (option B) seems like the most direct approach. I'll go with that.
upvoted 0 times
...
Roxane
5 months ago
Hmm, I'm a bit unsure about this one. The options seem to be talking about different storage management techniques, but I'm not sure which one is the best fit for limiting the storage space in a single container.
upvoted 0 times
...
Rikki
5 months ago
This seems like a straightforward question about managing storage capacity. I think I know the right approach, but I'll double-check the options to be sure.
upvoted 0 times
...
Danica
5 months ago
I think we need to use a constructor to set the properties, but I'm not entirely sure which option does that correctly.
upvoted 0 times
...
Kami
5 months ago
I think the APP Security dashboard might be the one to use for tracking high-risk traffic, but I'm not completely sure.
upvoted 0 times
...
Gwen
10 months ago
C) is a good idea, but doesn't really 'limit' the space in the original container, just moves the problem elsewhere.
upvoted 0 times
Sharita
9 months ago
C) Store VM snapshots in a different container
upvoted 0 times
...
Myra
9 months ago
B) Set an advertised capacity for the container
upvoted 0 times
...
Deane
9 months ago
A) Enable reservation for rebuild capacity
upvoted 0 times
...
...
Luz
10 months ago
Haha, imagine an admin trying to 'rebuild' their way out of a storage problem. A) is a bit of a stretch.
upvoted 0 times
...
Sherron
10 months ago
I'm gonna go with B) because limiting the advertised capacity is a pretty straightforward way to cap the container's storage usage.
upvoted 0 times
Julieta
10 months ago
User 2: Yeah, that seems like the most direct way to limit storage usage in a container.
upvoted 0 times
...
Robt
10 months ago
User 1: I think B) is the way to go, setting an advertised capacity makes sense.
upvoted 0 times
...
...
Aja
10 months ago
I disagree. Storing VM snapshots in a different container would be a better option to limit storage space.
upvoted 0 times
...
Vashti
10 months ago
I agree with Glynda. Setting an advertised capacity will limit the storage space usage.
upvoted 0 times
...
Anthony
11 months ago
Thick provisioning the container in D) doesn't sound right, that's usually used to expand storage, not limit it.
upvoted 0 times
Joanna
10 months ago
C) Store VM snapshots in a different container
upvoted 0 times
...
Skye
10 months ago
B) Set an advertised capacity for the container
upvoted 0 times
...
Alyssa
10 months ago
A) Enable reservation for rebuild capacity
upvoted 0 times
...
...
Johnson
11 months ago
B) Set an advertised capacity for the container seems like the most direct way to limit the storage space for a single container.
upvoted 0 times
...
Glynda
11 months ago
I think the administrator should set an advertised capacity for the container.
upvoted 0 times
...

Save Cancel