To achieve end-to-end encryption while allowing NetScaler to optimize responses, which configuration is used?

To achieve end-to-end encryption while allowing NetScaler to optimize responses, which configuration is used?

• A. HTTP protocol for the virtual server and HTTP protocol for services.
• B. SSL Bridge protocol for the virtual server and SSL protocol for the services.
• C. SSL protocol for the virtual server and SSL protocol for the services.
• D. SSL protocol for the services and HTTP for the virtual server.

Answer: (C)

End-to-end encryption with NetScaler optimization is achieved by using TLS on both legs: the frontend virtual server and the backend services. This lets the client talk to the NetScaler over HTTPS, while the NetScaler decrypts the outer layer to perform optimization, then re-encrypts the data when sending to the backend over TLS. In other words, the client-to-NetScaler leg stays encrypted and the NetScaler-to-backend leg also stays encrypted, allowing HTTP optimization to occur on the decrypted data in between while preserving encryption on both sides. If the front end used plain HTTP, the client traffic wouldn’t be encrypted; if the back end used plain HTTP, encryption wouldn’t be maintained to the backend.

End-to-end encryption with NetScaler optimization is achieved by using TLS on both legs: the frontend virtual server and the backend services. This lets the client talk to the NetScaler over HTTPS, while the NetScaler decrypts the outer layer to perform optimization, then re-encrypts the data when sending to the backend over TLS. In other words, the client-to-NetScaler leg stays encrypted and the NetScaler-to-backend leg also stays encrypted, allowing HTTP optimization to occur on the decrypted data in between while preserving encryption on both sides. If the front end used plain HTTP, the client traffic wouldn’t be encrypted; if the back end used plain HTTP, encryption wouldn’t be maintained to the backend.