A hardware load-balancer lead time is delaying publication of the motor-vehicle portal. Which traditional challenge is that, and what identify-level alternative does virtual networking offer?
Select an answer to reveal the explanation.
Short Explanation
A crate on back-order should not keep the motor-vehicle portal dark. Software load balancing is a service you turn on, not a pallet you wait for. The city already has the platform.
Full Explanation
Appliance lead time for a hardware load balancer delaying the motor-vehicle portal is addressed by software load-balancing services that can publish the civic portal without waiting on a physical load-balancer appliance. Claiming the portal must wait and NSX cannot load-balance in software is incorrect at the identify level. Horizon Connection Server is not the city's general software load balancer for motor-vehicle HTTPS. Carbon Black rules on endpoints do not replace a portal virtual IP. Exam caveat: capacity, certificates, and Edge sizing still matter for production software load balancing. Operational check: publish a non-prod motor-vehicle VIP using NSX load balancing and validate health checks without a hardware LB purchase order. Keep municipal naming and change tickets aligned with the software objects so civic audits can trace intent. Prefer verifying with a non-production agency workload before promoting the same pattern to life-safety systems. Record realization state and underlay health in the runbook used by on-call city operators. Keep municipal naming and change tickets aligned with the software objects so civic audits can trace intent. Prefer verifying with a non-production agency workload before promoting the same pattern to life-safety systems.