Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

VMware 3V0-21.23 Exam - Topic 2 Question 5 Discussion

Actual exam question for VMware's 3V0-21.23 exam
Question #: 5
Topic #: 2
[All 3V0-21.23 Questions]

A company will be replacing the external storage array that is currently providing storage to the vSphere environment. The architect must design a storage architecture for existing and future workloads. Company policy required storage separation of workloads by departments.

Which design decision should the architect make to satisfy the requirement and scale for additional departments?

Show Suggested Answer Hide Answer
Suggested Answer: B

The company policy requires storage separation of workloads by departments. To meet this requirement, the architect should design the storage architecture to create a dedicated storage volume for each department. This approach allows for logical separation of each department's data, ensuring that workloads from one department are isolated from the others.

Creating new storage volumes for new departments provides scalability. As new departments are added, new volumes can be provisioned without affecting the existing volumes or requiring reconfiguration of the existing department's storage.


Contribute your Thoughts:

0/2000 characters
Bok
4 months ago
D seems overkill for just separating departments.
upvoted 0 times
...
Lennie
4 months ago
A could work too, but it might get messy with too many apps.
upvoted 0 times
...
Odette
5 months ago
Totally agree, B is the way to go!
upvoted 0 times
...
Shayne
5 months ago
Wait, how does extending volumes for new departments work? Sounds risky.
upvoted 0 times
...
Kate
5 months ago
I think option B makes the most sense for department separation.
upvoted 0 times
...
Tonja
5 months ago
I recall that using storage volumes based on applications could complicate things. I lean towards option B, but I'm not completely confident in that choice.
upvoted 0 times
...
Cathrine
5 months ago
I practiced a similar question where we had to consider future growth. I think option D might be overkill, but I can see the appeal of N + 1 for redundancy.
upvoted 0 times
...
Allene
6 months ago
I'm not entirely sure, but I feel like using one storage volume per department could lead to management issues down the line. Maybe option C is better?
upvoted 0 times
...
Bette
6 months ago
I remember discussing the importance of separating workloads by departments in our study group. I think option B makes sense for scalability.
upvoted 0 times
...
Yolando
6 months ago
I'm leaning towards Option C. Extending the current volumes for new departments seems like a more efficient approach than creating entirely new volumes each time.
upvoted 0 times
...
Stefania
6 months ago
Option B looks like the best choice to me. Creating a separate storage volume per department will provide the required separation, and we can easily add new volumes as new departments are added.
upvoted 0 times
...
Leatha
6 months ago
Hmm, I'm a bit unsure about this one. The question is asking for a design decision, so I'll need to carefully consider the options and how they address the requirements.
upvoted 0 times
...
Selene
7 months ago
This seems like a straightforward storage design question. I think the key is to focus on the requirement for storage separation by department and the need to scale for future growth.
upvoted 0 times
...
Allene
1 year ago
I think using N + 1 storage volumes for current and future workloads is the best option for scalability.
upvoted 0 times
...
Azalee
1 year ago
I agree with Vashti, having separate volumes for each department will make management easier.
upvoted 0 times
...
Coleen
1 year ago
Option D sounds like a real 'storage array' of fun! Get it? Array? Storage? Ah, never mind.
upvoted 0 times
...
Tresa
1 year ago
I disagree, I believe we should use storage volumes based on applications for better organization.
upvoted 0 times
...
Iluminada
1 year ago
B looks good to me. Separating by department is a no-brainer for this scenario. Plus, it's easier to manage.
upvoted 0 times
Stevie
12 months ago
B) I agree, separating by department makes it easier to manage.
upvoted 0 times
...
Elke
12 months ago
A) Use storage volumes based on applications.
upvoted 0 times
...
Justine
1 year ago
B) Use one storage volume per department and create new volumes for new departments.
upvoted 0 times
...
...
Jamal
1 year ago
I'm going with C. Extending existing volumes is more efficient than creating new ones for each new department.
upvoted 0 times
...
Shakira
1 year ago
D is the way to go. N + 1 volumes give you the flexibility to handle future growth without hassle.
upvoted 0 times
Alesia
1 year ago
User 2
upvoted 0 times
...
Elroy
1 year ago
User 1
upvoted 0 times
...
...
Vashti
1 year ago
I think we should use one storage volume per department and create new volumes for new departments.
upvoted 0 times
...
Craig
1 year ago
Option B makes the most sense. Separating by department ensures isolation and scalability.
upvoted 0 times
Rupert
1 year ago
Separating by department is a good way to ensure isolation and scalability.
upvoted 0 times
...
Marjory
1 year ago
Using one storage volume per department will make it easier to manage workloads.
upvoted 0 times
...
Janessa
1 year ago
Creating new volumes for new departments will definitely help with scalability.
upvoted 0 times
...
Mammie
1 year ago
I agree, option B seems like the best choice for this scenario.
upvoted 0 times
...
...

Save Cancel