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 Exam 3V0-21.23 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:

Allene
27 days ago
I think using N + 1 storage volumes for current and future workloads is the best option for scalability.
upvoted 0 times
...
Azalee
30 days ago
I agree with Vashti, having separate volumes for each department will make management easier.
upvoted 0 times
...
Coleen
30 days ago
Option D sounds like a real 'storage array' of fun! Get it? Array? Storage? Ah, never mind.
upvoted 0 times
...
Tresa
1 months ago
I disagree, I believe we should use storage volumes based on applications for better organization.
upvoted 0 times
...
Iluminada
1 months 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
Justine
8 days ago
B) Use one storage volume per department and create new volumes for new departments.
upvoted 0 times
...
...
Jamal
1 months 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 months ago
D is the way to go. N + 1 volumes give you the flexibility to handle future growth without hassle.
upvoted 0 times
Alesia
24 days ago
User 2
upvoted 0 times
...
Elroy
28 days ago
User 1
upvoted 0 times
...
...
Vashti
1 months ago
I think we should use one storage volume per department and create new volumes for new departments.
upvoted 0 times
...
Craig
2 months ago
Option B makes the most sense. Separating by department ensures isolation and scalability.
upvoted 0 times
Rupert
24 days ago
Separating by department is a good way to ensure isolation and scalability.
upvoted 0 times
...
Marjory
25 days ago
Using one storage volume per department will make it easier to manage workloads.
upvoted 0 times
...
Janessa
28 days ago
Creating new volumes for new departments will definitely help with scalability.
upvoted 0 times
...
Mammie
1 months ago
I agree, option B seems like the best choice for this scenario.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77