Nutanix NCP-US Exam - Topic 9 Question 32 Discussion

Actual exam question for Nutanix's NCP-US exam

Question #: 32
Topic #: 9

A team of developers are working on a new processing application and requires a solution where they can upload the ... code for testing API calls. Older iterations should be retained as newer code is developer and tested.

ACreate an SMB Share with Files and enable Previous Version

BProvision a Volume Group and connect via iSCSI with MPIO.

CCreate an NFS Share, mounted on a Linux Server with Files.

DCreate a bucket in Objects with Versioning enabled.

Show Suggested Answer

Suggested Answer: D

Nutanix Objects supports versioning, which is a feature that allows multiple versions of an object to be preserved in the same bucket. Versioning can be useful for developers who need to upload their code for testing API calls and retain older iterations as newer code is developed and tested. Versioning can also provide protection against accidental deletion or overwrite of objects. Reference: Nutanix Objects Administration Guide

by Vallie at Jul 15, 2024, 08:45 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Laurel

3 months ago

iSCSI with MPIO seems overkill for this task.

upvoted 0 times

...

Caprice

3 months ago

Wait, can you really keep older code that way?

upvoted 0 times

...

Holley

3 months ago

Definitely go with the Objects bucket for versioning!

upvoted 0 times

...

Laura

4 months ago

I think NFS is a better option for Linux servers.

upvoted 0 times

...

Julianna

4 months ago

SMB Share with Previous Versions sounds solid!

upvoted 0 times

...

Taryn

4 months ago

I vaguely recall that using objects with versioning is a common practice for managing code versions, so I’m leaning towards option D as well.

upvoted 0 times

...

Florinda

4 months ago

I practiced a similar question about file storage solutions, and I feel like NFS shares are more for Linux environments, so option C might not be the best fit here.

upvoted 0 times

...

Una

4 months ago

I'm not entirely sure, but I think SMB shares can keep previous versions too. Maybe option A could work?

upvoted 0 times

...

Cristy

5 months ago

I remember studying about versioning in cloud storage, so option D seems like it could be the right choice for retaining older iterations.

upvoted 0 times

...

Jade

5 months ago

Alright, I think I've got this one figured out. The key requirement here is the need to retain older versions of the code, which points me towards option D - creating a bucket in Objects with Versioning enabled. That would give them a simple, scalable way to upload new versions of the code and easily access previous iterations. Yep, I'm pretty confident that's the best solution for this scenario.

upvoted 0 times

...

Avery

5 months ago

Whoa, this is a tricky one. I'm not super familiar with all these storage options, to be honest. I guess I'd lean towards the iSCSI solution (option B) since that seems like it could provide the versioning and scalability they might need. But I'm not 100% sure. Hmm, maybe I should review the differences between these approaches before deciding.

upvoted 0 times

...

Darnell

5 months ago

Okay, let me think this through. They need a way to store and version the code, and it sounds like they're looking for a file-based solution rather than a database. I'm a bit torn between the SMB share with Previous Versions (option A) and the NFS share on Linux (option C). Both of those could work, but I'm not sure which one would be the better fit.

upvoted 0 times

...

Leanora

5 months ago

This seems like a pretty straightforward storage question. I'd start by considering the requirements - they need a way to upload and retain older versions of code for testing API calls. Hmm, I think option D, creating a bucket in Objects with Versioning enabled, might be the best approach here.

upvoted 0 times

...

Letha

5 months ago

Okay, I think I've got a handle on this. The key is to find a way to get the hot-fix deployed quickly without compromising the integrity of the production environment.

upvoted 0 times

...

Cordie

5 months ago

I practiced a similar question where we had to evaluate different scenarios with caps and floors. I think I need to remember how to handle the math for this specific situation.

upvoted 0 times

...

Desirae

2 years ago

Hold up, are we sure we can't just use a time machine to go back and retrieve the older code? I'm pretty sure option D is the right answer, but the time machine idea has some potential.

upvoted 0 times

...

Socorro

2 years ago

D. Can't go wrong with good old object storage. Just make sure to enable versioning, otherwise it's like trying to debug code without a version control system!

upvoted 0 times

Ollie

1 year ago

Definitely, we need to make sure we can easily revert back to older versions if needed.

upvoted 0 times

...

Rebbecca

1 year ago

Object storage with versioning sounds like the way to go for this project.

upvoted 0 times

...

Casie

1 year ago

Agreed, versioning is key for tracking changes in the code.

upvoted 0 times

...

Lera

2 years ago

Let's go with option D, create a bucket in Objects with Versioning enabled.

upvoted 0 times

...

Nicholle

2 years ago

I don't know, I'm still trying to figure out what an 'SMB Share' is. Is that like a SharePoint site or something? I'll just go with D, sounds like the most straightforward option.

upvoted 0 times