Explanation/Reference:
A: OOP configuration does not support auto-discovery. You must create a fixed-target rule on the clientside Steelhead.
C: An out-of-path deployment is generally located on the server-side and is often described as a server- side outof-path deployment.
In an out-of-path deployment, only a SteelHead primary interface is required to connect to the network.
The SteelHead can be connected anywhere in the LAN. An out-of-path SteelHead deployment does not have a redirecting device. You configure fixed-target in-path rules for the client-side SteelHead. The fixed- target in-path rules point to the primary IP address of the out-of-path SteelHead. The out-of-path SteelHead uses its primary IP address when communicating to the server. The remote SteelHead must be deployed either in a physical or virtual in-path mode.
Incorrect:
Not D: You can use RiOS data store synchronization between the out-of-path SteelHeads for additional benefits in case of a failure.
Not E: OOP configuration does not support auto-discovery
References: SteelHead Deployment Guide Including the SteelCentral Controller for SteelHead Mobile, December 2014, page 352
https://support.riverbed.com/bin/support/download?did=hcsksjojd701t4t8v5s5qomoj7