VMware NSX Advanced Load Balancer: Global Server Load Balancing Design and Deploy — Lesson 1: GSLB use cases, DNS concepts, NSX ALB architecture, sites, leaders and followers, service discovery, authoritative domains, requirements, latency, and failure scenarios

Learning Objectives

• Break down the prerequisites, components, roles, and decision points involved in GSLB use cases, DNS concepts, NSX ALB architecture, sites, leaders and followers, service discovery, authoritative domains, requirements, latency, and failure scenarios.
• Complete a controlled activity for GSLB use cases, DNS concepts, NSX ALB architecture, sites, leaders and followers, service discovery, authoritative domains, requirements, latency, and failure scenarios and capture GSLB requirements matrix and multi-site architecture.
• Challenge the result with a delegated domain remaining dependent on one DNS path during a site outage, then justify the corrective action.

Detailed Topics

• GSLB use cases
• DNS concepts
• NSX ALB architecture
• Sites
• Leaders and followers
• Service discovery
• Authoritative domains
• Requirements
• Latency
• And failure scenarios
• Decision ownership, prerequisites, and acceptance evidence for GSLB use cases, DNS concepts, NSX ALB architecture, sites, leaders and followers, service discovery, authoritative domains, requirements, latency, and failure scenarios
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The instructor builds a representative scenario for GSLB use cases, DNS concepts, NSX ALB architecture, sites, leaders and followers, service discovery, authoritative domains, requirements, latency, and failure scenarios, narrating each decision and showing how it contributes to a global server load-balancing design that directs users to healthy application sites based on availability, geography, performance, persistence, DNS behavior, and recovery requirements. The demonstration records GSLB requirements matrix and multi-site architecture so learners can compare design intent with observable behavior.

Hands-On Exercise

Build or execute GSLB use cases, DNS concepts, NSX ALB architecture, sites, leaders and followers, service discovery, authoritative domains, requirements, latency, and failure scenarios for a defined scenario. Introduce the condition “a delegated domain remaining dependent on one DNS path during a site outage,” inspect the evidence, correct the cause without discarding the audit trail, and document the accepted state in GSLB requirements matrix and multi-site architecture.

1. Record the starting state, assumptions, identities, topology, and expected outcome.
2. Execute the planned workflow and collect evidence at each material checkpoint.
3. Test one valid path, one boundary condition, and the stated failure scenario.
4. Document the correction, retest result, rollback option, and follow-up owner.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for GSLB use cases, DNS concepts, NSX ALB architecture, sites, leaders and followers, service discovery, authoritative domains, requirements, latency, and failure scenarios.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how GSLB requirements matrix and multi-site architecture should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

When GSLB use cases, DNS concepts, NSX ALB architecture, sites, leaders and followers, service discovery, authoritative domains, requirements, latency, and failure scenarios produces an unexpected result, reproduce the issue with the same scope, identity, workload, and time context. Inspect GSLB requirements matrix and multi-site architecture, test whether “a delegated domain remaining dependent on one DNS path during a site outage” explains the evidence, apply the smallest reversible correction, and retest an unaffected path for regression.

Validation Checklist

• The requirement for GSLB use cases, DNS concepts, NSX ALB architecture, sites, leaders and followers, service discovery, authoritative domains, requirements, latency, and failure scenarios is linked to an owner and observable acceptance condition.
• Gslb requirements matrix and multi-site architecture contains enough detail for another practitioner to repeat the check.
• Normal operation, one boundary condition, and the identified failure path have been tested.
• Access, security, downstream impact, rollback, monitoring, and support ownership are recorded.

Lesson Outcome

Learners can apply GSLB use cases, DNS concepts, NSX ALB architecture, sites, leaders and followers, service discovery, authoritative domains, requirements, latency, and failure scenarios, explain the decisions made, and defend the result with GSLB requirements matrix and multi-site architecture.