Key Concepts
Review these important points before starting the quiz
RPO determined by replication: Storage replication frequency defines maximum data loss during failover
Unified policy enforcement: NSX provides consistent policies across VMs and containers
Capacity planning includes overhead: HA, vSAN, management components consume usable capacity
POC testing validates assumptions: Lab testing provides highest confidence before production
Operational runbooks are critical: Day 2 teams need detailed procedures, not just diagrams
Domain isolation enables independence: Workload domains can be added without impacting others
Control plane latency matters: Management Domain communication affects operations responsiveness
Tagging enables chargeback: Automated metering requires resource tagging and integration
Management Domain is single point of failure: Failure impacts all workload domains
Regional instances for data sovereignty: Geographic compliance requires local data residency
Logical and physical views both needed: Intent and implementation details are complementary
Modular design balances growth and cost: Scalable architecture without over-provisioning
Availability zones impact cost and availability: More zones increase both
Stretched clusters have limits: Network partition creates split-brain scenarios
Change management is infrastructure-wide: Changes can cascade across layers and domains
Micro-segmentation balances security and flexibility: Policy-based controls provide both
Multi-tenancy requires isolation: Resource, network, and RBAC separation per tenant
Separate domains for different SLAs: Development and production require different policies
Non-functional requirements define success: Performance, security, availability are critical
Centralized logging for compliance: Audit trails require long-term log retention
Open standards reduce lock-in: Interoperability provides flexibility
Automated remediation has risks: Incorrect logic can cause cascading failures
Document rationale and alternatives: Context enables future architects to understand decisions
Standardization supports operations: Reduces complexity and enables automation
Design impacts operational efficiency: Architecture decisions affect Day 2 complexity