1V0-701 · Question #90
Which three requirements should be gathered during a design workshop? (Choose three.)
The correct answer is A. Constraints C. Manageability D. Risks. See the full explanation below for the reasoning.
Question
Which three requirements should be gathered during a design workshop? (Choose three.)
Options
- AConstraints
- BRecoverability
- CManageability
- DRisks
- ERequirements
How the community answered
(19 responses)- A74% (14)
- B16% (3)
- E11% (2)
Community Discussion
6
Wesley A.Mar 4, 2026The correct answers are A, C, and D. Constraints, Manageability, and Risks are the three things you gather during a design workshop because they shape what the solution actually has to work within and account for, not just what it needs to do. The trap that got me the first time was picking E, Requirements, which feels obvious, but in the VMware framework Requirements is what you produce from the workshop, not something you gather during it. Recoverability is a characteristic you design for later, not a workshop input either.
Imani T.Mar 17, 2026The word "Requirements" as an answer choice on a requirements-gathering question is a trap that reads like a joke, but E is wrong because you are gathering requirements, not listing "requirements" as a category you collect during that session. A, C, and D cover Constraints, Manageability, and Risks, which are the actual buckets VMware wants you to associate with design workshop inputs.
Konstantin H.Mar 6, 2026Recoverability has to be in there because it is a non-functional requirement that directly shapes your BCDR posture before you ever touch a logical design, and if you leave it ungathered in the workshop you end up reverse-engineering RPO and RTO constraints from a platform that was never sized to meet them. You cannot treat recoverability as something you bolt on in the physical design phase, it belongs on the whiteboard on day one alongside whatever else you are capturing from the business.
Dervla O.Mar 8, 2026Konstantin, recoverability is genuinely important but the question is asking what you gather in the conceptual design phase, and at that stage you are focused on entity relationships, business rules, and data volume estimates, not disaster recovery constraints, which land in the logical and physical phases where you have an actual schema to size against.
Dervla O.Mar 21, 2026Constraints, risks, and manageability fit the "workshop output" bucket, not recoverability or requirements themselves - does that distinction make sense to you?
Imani T.Mar 22, 2026Manageability I would push back on slightly since it can surface just as easily in a post-implementation review as in a workshop, but the core separation between what a facilitated session produces versus what a change inherently has as a property, that tracks.