When a company network architect is working on a new network design, they are expected...

In addition to business requirements, network architects must also account for non-business constraints such as legal, regulatory, and industry compliance. These may include standards like GDPR, HIPAA, PCI-DSS, or country-specific data sovereignty and retention laws.

Compliance is not typically driven by direct business value but by external mandates that influence how the network must be designed, implemented, and operated. Ignoring compliance requirements can result in significant legal or financial penalties and is therefore a core component of any responsible network design.

Other options such as:

A. Location — may impact design (e.g., latency, availability), but it is often categorized as a technical or logistical consideration.

B. Cost — is a business constraint.

C. Time — is considered a project or delivery constraint, also typically business-driven.