Exam Radar
Core Priority: Ensuring underlying physical infrastructure meets standardized SDDC requirements before deployment.
High Frequency: Completion of the Deployment Parameter Workbook for management networking and host FQDNs.
Confusion Alert: Validating VLAN tagging and Jumbo Frames (MTU) via Cloud Builder versus post-deployment checks.
Scenario Logic: Utilizing Cloud Builder to verify DNS/NTP reachability and clean partition tables on ESXi hosts.
Version Delta: Strategic focus on standardized host preparation to ensure a functioning SDDC bring-up.
Atomic Deconstruction
Actionable: Finalize the configuration spreadsheet to define all management IP addresses and license keys prior to initializing Cloud Builder.
Parametric: Verify that Jumbo Frames are configured across the physical network to support vSAN and vMotion traffic requirements.
Causal: Successful host preparation, including standardized password configuration and version alignment, prevents automated bring-up failures.
SKILLS.md Matrix
| Task | Component | Operational Detail |
|---|---|---|
| Configuration | Parameter Workbook | FQDN and IP mapping |
| Validation | Cloud Builder Engine | MTU and DNS/NTP checks |
| Preparation | ESXi Host Cleanup | Clean partition tables/Correct version |
Exam Radar
Core Priority: Transforming individual ESXi hosts into a functioning Management Domain via automation.
High Frequency: The automated orchestration of vCenter Server, NSX Manager, and SDDC Manager deployment.
Scenario Logic: Automatic creation of the management vSAN cluster and initial management overlay segments.
Version Delta: Leveraging Cloud Builder to establish the foundational management plane for all future workload domains.
Atomic Deconstruction
Actionable: Monitor the automated bring-up process as it deploys the core management components and establishes the cluster.
Parametric: Confirm the creation of the management vSAN cluster, including the application of the default storage policy.
Causal: Initializing the NSX management cluster during bring-up provides the necessary networking fabric for all management-level services.
SKILLS.md Matrix
| Element | Logic | Atomic Detail |
|---|---|---|
| Automation | Orchestrated Deployment | vCenter, NSX, and SDDC Manager |
| Storage | vSAN Management | Automatic disk group creation |
| Networking | NSX Initialization | Management overlay segment setup |
Exam Radar
Core Priority: Preparing the management environment for day-two operations and workload expansion.
High Frequency: Importing and assigning licenses for vSphere, vSAN, and NSX-T within the inventory.
Scenario Logic: Integrating with Active Directory or LDAP for role-based access control (RBAC).
Version Delta: Setting up the bundle repository with My VMware credentials for binary downloads.
Atomic Deconstruction
Actionable: Connect SDDC Manager to the official bundle repository to enable the download of upgrade binaries and deployment images.
Parametric: Assign imported license keys to the correct infrastructure objects within the SDDC Manager inventory.
Causal: Proper identity integration ensures that infrastructure administrators can manage resources using centralized credentials instead of local accounts.
SKILLS.md Matrix
| Category | Atomic Requirement | Operational Detail |
|---|---|---|
| Licensing | Key Assignment | vSphere, vSAN, and NSX-T |
| Repository | Bundle Sync | My VMware credential integration |
| Identity | AD/LDAP Integration | RBAC for infrastructure admins |
Exam Radar
Core Priority: Orchestrating the creation of dedicated compute clusters for business applications via SDDC Manager.
High Frequency: Selecting storage types (vSAN, NFS, or VMFS on FC) during the Workload Domain Creation Wizard.
Confusion Alert: Differentiating between commissioning unassigned hosts and adding them to a specific VI Workload Domain.
Scenario Logic: Automated rollout of dedicated vCenter and NSX-T manager instances for localized workload management.
Version Delta: Utilizing host validation workflows to ensure networking and hypervisor compatibility before domain assignment.
Atomic Deconstruction
Actionable: Use the Workload Domain Creation Wizard to define domain names and select the appropriate vCenter OVA for deployment.
Parametric: Commission ESXi hosts by validating their networking and hardware configuration before adding them to the new VI cluster inventory.
Causal: Deploying a dedicated vCenter for each workload domain ensures management isolation and prevents a single point of failure for the entire SDDC.
SKILLS.md Matrix
| Task | Component | Operational Detail |
|---|---|---|
| Domain Creation | Creation Wizard | Storage and vCenter OVA selection |
| Inventory | Host Commissioning | Validation of unassigned hosts |
| Isolation | vCenter/NSX Rollout | Dedicated instances per VI domain |
Exam Radar
Core Priority: Establishing the bridge between the virtual overlay network and the physical infrastructure.
High Frequency: Deploying Edge Transport Nodes as virtual machines on the newly created VI cluster.
Confusion Alert: Distinguishing between the Tier-0 gateway (North-South routing) and Tier-1 gateway (Tenant-specific segments).
Scenario Logic: Configuring Uplink Profiles and Transport Zones to ensure correct traffic encapsulation for Edge nodes.
Version Delta: Strategic use of BGP or static routes on the Tier-0 gateway to connect to physical top-of-rack switches.
Atomic Deconstruction
Actionable: Deploy NSX Edge nodes via SDDC Manager or NSX Manager and associate them with the VLAN and Overlay transport zones.
Parametric: Create Tier-0 and Tier-1 gateways, ensuring the Tier-0 is configured for external BGP peering with physical routers.
Causal: Proper Edge cluster configuration is a prerequisite for enabling advanced network services such as Avi load balancing and distributed firewalls.
SKILLS.md Matrix
| Element | Logic | Atomic Detail |
|---|---|---|
| Edge Nodes | Transport Nodes | VM-based deployment on VI clusters |
| Routing | Tier-0 Gateway | North-South physical connectivity |
| Connectivity | Transport Zones | Uplink profile and VLAN/Overlay mapping |
Exam Radar
Core Priority: Initializing the load balancing management plane within the management or workload domain.
High Frequency: Forming a three-node Controller cluster to provide management plane redundancy.
Scenario Logic: Performing day-zero configuration including administrator passwords, DNS/NTP settings, and cloud type selection.
Version Delta: Importing the Avi Controller OVA into the Content Library as the first step of the deployment workflow.
Atomic Deconstruction
Actionable: Import the Avi Controller OVA and deploy the first node with a fixed management IP, then join two additional nodes to form a cluster.
Parametric: Complete the initial setup wizard by defining the management credentials and selecting the target cloud type (vCenter or NSX-T).
Causal: A three-node cluster ensures that the Avi database remains synchronized and the management interface remains available during a node failure.
SKILLS.md Matrix
| Category | Atomic Requirement | Operational Detail |
|---|---|---|
| Deployment | OVA Import | Content Library-based initialization |
| Redundancy | Cluster Formation | 3-node management plane setup |
| Configuration | Setup Wizard | DNS, NTP, and Cloud Type selection |
Exam Radar
Core Priority: Setting up the functional component that enables Write Access mode for infrastructure automation.
High Frequency: Mapping the Controller to vCenter credentials and selecting the Data Center, Cluster, and Content Library.
Confusion Alert: Distinguishing between vCenter Cloud setup (VM management) and NSX-T Cloud setup (Segment/Transport Zone discovery).
Scenario Logic: Troubleshooting "Yellow" or "Red" cloud status caused by SSL certificate mismatches or credential expiration.
Version Delta: Integration with IPAM and DNS profiles (e.g., Infoblox) to automate VIP and DNS record assignment.
Atomic Deconstruction
Actionable: Establish a connection to the NSX Manager or vCenter by providing API credentials and selecting the logical segments for Service Engine placement.
Parametric: Identify and select the specific vSphere Content Library where the Service Engine (SE) images are stored for automated cloning.
Causal: Configuring the Cloud Connector with correct permissions allows the Controller to automatically discover Tier-1 Gateways and network segments.
SKILLS.md Matrix
| Element | Atomic Requirement | Operational Detail |
|---|---|---|
| Connectivity | Infrastructure Sync | vCenter or NSX-T Manager API link |
| Discovery | Object Mapping | T1, Segments, and Cluster discovery |
| Automation | IPAM/DNS Profile | Automated IP and record assignment |
Exam Radar
Core Priority: Managing the data plane virtual machines that handle application traffic.
High Frequency: Triggering automated SE deployment via the creation of a Virtual Service in Write Access mode.
Confusion Alert: Understanding how the Controller uploads SE OVAs to the Content Library versus the deployment of VM instances.
Scenario Logic: Performing non-disruptive upgrades of SE software using canary or parallel update mechanisms.
Version Delta: Utilizing Service Engine Group (SEG) properties to define CPU/Memory sizing and HA modes for new SEs.
Atomic Deconstruction
Actionable: Initiate a software upgrade for an SE Group and monitor the Controller as it drains existing connections before replacing SE VMs.
Parametric: Define the maximum and minimum number of Service Engines allowed per group to control the scaling boundaries of the data plane.
Causal: Automatic lifecycle management ensures that SE images remain synchronized with the Controller version across all workload domains.
SKILLS.md Matrix
| Task | Logic | Atomic Detail |
|---|---|---|
| Provisioning | Automated VM Creation | Orchestrated via Cloud Connector |
| Scaling | SEG Assignment | Inherited CPU/RAM/HA properties |
| Maintenance | Rolling Upgrades | Disruption-free software updates |
Exam Radar
Core Priority: Securing application delivery through modern cipher suites and digital certificate management.
High Frequency: Configuring SSL/TLS profiles to meet compliance standards such as PCI-DSS or HIPAA.
Scenario Logic: Automating certificate issuance and renewal through integration with CAs like Let's Encrypt or Venafi.
Version Delta: Implementing application header insertion (e.g., X-Forwarded-Proto) during SSL termination.
Atomic Deconstruction
Actionable: Create an SSL/TLS profile that restricts versions to TLS 1.2 and 1.3 while disabling insecure ciphers to protect data in transit.
Parametric: Map a Certificate Management Profile to an external CA to enable automated renewal of application-facing certificates.
Causal: Terminating SSL at the Service Engine allows the load balancer to inspect traffic and insert security headers before forwarding to backend servers.
SKILLS.md Matrix
| Category | Atomic Requirement | Operational Detail |
|---|---|---|
| Compliance | SSL/TLS Profile | Cipher strength and version control |
| Automation | CA Integration | Automated cert issuance and renewal |
| Optimization | Header Insertion | X-Forwarded-Proto for backend visibility |
Exam Radar
Core Priority: Defining the logical relationship between the front-end VIP and backend application servers.
High Frequency: Selecting the correct Application Profile (HTTP, L4, DNS) to dictate traffic handling behavior.
Confusion Alert: Distinguishing between a Pool (group of servers) and a Pool Group (collection of pools for priority-based routing).
Scenario Logic: Implementing 80 to 443 redirection at the Virtual Service level to ensure secure client communication.
Version Delta: Utilizing modern health monitors that check for specific application strings rather than just TCP port availability.
Atomic Deconstruction
Actionable: Create a Virtual Service and associate it with a Pool containing backend server IP addresses and their respective service ports.
Parametric: Configure an HTTP Application Profile to enable features like connection multiplexing and compression for optimized delivery.
Causal: Correctly mapping a Virtual Service to a Pool ensures that the Service Engine knows exactly where to forward incoming client requests after processing.
SKILLS.md Matrix
| Component | Logic | Operational Detail |
|---|---|---|
| Virtual Service | VIP Presentation | Front-end IP and Port mapping |
| Application Profile | Protocol Behavior | HTTP/L4/DNS specific settings |
| Pool | Backend Targets | Server IP and Port group |
Exam Radar
Core Priority: Ensuring traffic is only sent to responsive servers and maintaining session continuity.
High Frequency: Choosing between HTTP Cookie persistence and Source IP persistence based on application needs.
Scenario Logic: Troubleshooting "Down" pool members by verifying HTTP response codes (e.g., Expect 2xx) in the monitor settings.
Version Delta: Strategic use of active health monitors to perform periodic sub-second checks on application health.
Atomic Deconstruction
Actionable: Attach an HTTP Health Monitor to a Pool and configure it to search for a specific "Expect" string in the server's response.
Parametric: Define a persistence profile with a specific timeout to ensure that users are not disconnected during long-running sessions.
Causal: Implementing robust health monitoring prevents the load balancer from sending traffic to a "zombie" server that is network-up but application-down.
SKILLS.md Matrix
| Element | Logic | Atomic Detail |
|---|---|---|
| Health Monitor | Response Verification | HTTP string and status code checks |
| Persistence | Client Affinity | Cookie-based session tracking |
| Reliability | Passive Monitoring | Real-time traffic failure detection |
Exam Radar
Core Priority: Establishing visibility into application traffic while managing data plane resource usage.
High Frequency: Configuring Significant Logs by default to capture errors while ignoring routine successful traffic.
Scenario Logic: Enabling Full Logs temporarily for specific client IPs to troubleshoot TCP handshake or SSL handshake failures.
Version Delta: Setting up Analytics Profiles to collect telemetry data that feeds the Avi Health Score.
Atomic Deconstruction
Actionable: Edit the Analytics Profile for a Virtual Service to set the log level to Significant and define the retention period for metrics.
Parametric: Enable Real-Time Metrics to provide sub-second visibility into throughput and latency during performance testing.
Causal: Properly configured logging provides the necessary forensics to perform root cause analysis without overwhelming the Controller's storage.
SKILLS.md Matrix
| Category | Atomic Requirement | Operational Detail |
|---|---|---|
| Logging | Significant vs. Full | Tiered visibility for resource efficiency |
| Telemetry | Real-Time Metrics | High-frequency performance monitoring |
| Forensics | Client Insights | Detailed browser and device visibility |
What is typically the first step when deploying VMware Avi Load Balancer in a vSphere environment?
Deploy the Avi Controller virtual machine.
The Avi Controller provides the control plane for the platform. It manages configuration, analytics, and orchestration.
During initial deployment, administrators deploy the Controller as a virtual appliance in vSphere using the provided OVA template.
After deployment, administrators configure:
network settings
administrator credentials
cloud integration settings
Only after the Controller is operational can the system automatically deploy Service Engines.
Exam questions describing initial deployment steps usually expect Controller deployment before any other component.
Demand Score: 91
Exam Relevance Score: 94
What role does the Avi Cloud configuration play during setup?
It connects the Avi Controller to the underlying infrastructure platform.
Avi Cloud configuration defines the environment where Service Engines will run.
Examples include:
VMware vSphere
VMware NSX-T
AWS or Azure
Kubernetes
The Cloud configuration allows the Controller to automate tasks such as:
deploying Service Engines
allocating networking resources
scaling infrastructure
Without configuring the Cloud, the Controller cannot automatically create Service Engines.
Demand Score: 85
Exam Relevance Score: 90
Why might Service Engines fail to deploy automatically?
Common causes include insufficient permissions, incorrect cloud configuration, or resource constraints.
Automatic Service Engine deployment relies on the Controller interacting with the infrastructure platform.
Common problems include:
missing vCenter permissions
incorrect network mappings
insufficient CPU or memory resources
invalid datastore configuration
Administrators should verify the Cloud configuration and infrastructure credentials.
Exam questions involving Service Engine deployment failures usually expect answers related to cloud configuration or infrastructure permissions.
Demand Score: 87
Exam Relevance Score: 92
What is required before creating a Virtual Service in Avi?
A Service Engine Group and Cloud configuration must already exist.
Virtual Services represent the load balancing configuration for an application.
Before creating one, the platform requires:
a configured Cloud environment
an available Service Engine Group
backend server pool definitions
Once these elements exist, administrators can define the Virtual Service to distribute traffic to application servers.
Demand Score: 81
Exam Relevance Score: 89
What component performs SSL termination in Avi?
The Service Engine.
SSL termination offloads encryption processing from backend servers. Service Engines decrypt incoming SSL/TLS traffic and forward it to application servers.
This improves application performance and allows centralized certificate management.
Demand Score: 72
Exam Relevance Score: 86
What object defines the backend servers used by a Virtual Service?
A Pool.
In Avi, a Pool represents a group of backend application servers.
Pools define:
server IP addresses
health monitoring settings
load balancing algorithms
Virtual Services send traffic to servers within the configured pool.
Demand Score: 74
Exam Relevance Score: 88