After upgrading a critical web service, engineers configure it to support only new TLS 1.3 cipher suites. Legacy barcode-scanning workstations running outdated browsers now report TLS handshake failures in their event logs and cannot connect to the service. Which remediation most directly resolves the cipher-suite mismatch while retaining encryption?
Deploy a load balancer that discards advanced ciphers in transit
Bind the updated application to a different address used only by newer systems
Configure the updated environment to allow a fallback set of ciphers alongside the newer ones
Disable encryption on the updated environment so older endpoints can connect
Enabling a fallback set of cipher suites that both the legacy workstations and the updated service support allows the TLS handshake to succeed while still keeping traffic encrypted. Disabling encryption removes security entirely, binding the service to a different address does not change the negotiation between client and server, and deploying a load balancer that discards advanced ciphers still leaves the underlying incompatibility unresolved.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a cipher, and why is it important in network security?
Open an interactive chat with Bash
What does a handshake failure indicate in this context?
Open an interactive chat with Bash
Why is enabling a fallback set of ciphers the best solution for this issue?