Which three technical requirements should be rejected or restarted ? (Choose three)

Proper requirements are specific, measurable, and testable, defining what a system must do, not how. Options A and B represent high-level business and financial goals, not technical requirements. Option A is a business continuity objective that must be translated into specific technical metrics like Recovery Time Objective (RTO) and Recovery Point Objective (RPO). Option B is a financial constraint (ROI) that governs the project's business case, not the SAN's technical function. Option D improperly dictates a specific solution ("hosted on SANs") without defining the underlying technical need, a practice known as "solutioneering," which can lead to inefficient and costly designs. These three should be rejected and refined into proper technical requirements.

C. This is a well-formed, measurable, and specific technical requirement. It clearly defines a Recovery Time Objective (RTO) of "Y minutes" for a specific set of servers, which is a valid input for technical design.

1. SNIA Press Publication: Somasundaram, G., & Shrivastava, A. (Eds.). (2012). Information Storage and Management: Storing, Managing, and Protecting Digital Information in Classic, Virtualized, and Cloud Environments (2nd ed.). Wiley.

Page 316, Section 12.2.1: Explains that business continuity requirements like "keeping the business running" (Option A) must be translated into specific, technical metrics like RTO and RPO to be actionable for IT design.

Page 410, Section 14.2.1: Distinguishes between business requirements (including financial aspects like ROI, related to Option B) and technical requirements during the infrastructure management lifecycle.

2. University Courseware: Saltzer, J. H., & Kaashoek, M. F. (2009). Principles of Computer System Design: An Introduction. MIT OCW.

Chapter 1, Section 1.5.1 "Separating mechanism and policy": This principle supports rejecting Option D. The requirement should state the policy (e.g., "servers must have 99.99% availability") not the mechanism ("use a SAN"). Dictating the solution prematurely constrains the design.

3. Vendor Documentation: Hewlett Packard Enterprise. (2017). HPE ConvergedSystem for SAP HANA Scale-up Configurations Compute Node Stretch Clustering and Disaster Recovery.

Page 6, "Disaster recovery requirements": This document illustrates how high-level business needs are defined by specific RTO and RPO values. This supports that Option C is a valid technical requirement, while Option A is an undefined business goal that precedes it.