199-01 practice questions, page 11 of 14, with answer review and explanations.
Question 51
Refer to the exhibit. What configuration option is most relevant on Steelhead A to enable Steelhead Mobile Client R to set up the most efficient optimized connection to Server B?
Enhanced auto-discovery
Simplified Routing
no in-path peering manual enable
in-path rule pass rulenum start
in-path peering rule pass rulenum 1
Question 52
Refer to the exhibit. What option in the Acceleration policy used on Steelhead Mobile Client A will most likely enhance the users experience connecting to Server B, if Server B is an Exchange 2003 Server?
Enable MAPI NSPI
Increase the datastore size
Enable latency-based location awareness
Enable SSL optimization and import the Exchange certificate for Server B into Steelhead B
Peering rule rejecting optimization with Steelhead A
Question 53
Refer to the exhibit. If Server A is an FTP server, which setting will enable active FTP optimization on Steelhead Mobile Client R?
Steelhead A. in-path auto srcport 20
Steelhead A. in-path auto dstport 20
Client R: in-path auto dstport 20
Default auto-discovery rules will work
None of the above
Question 54
Refer to the exhibit. If Steelhead Mobile Client B offers up a share on the network, what is needed on Steelhead Mobile Client R to open an optimized connection to this share if enhanced auto-discovery is enabled on all Steelhead appliances?
Default auto-discovery will work fine without modification
The connection to Client B cannot be optimized because the Steelhead Mobile Controller cannot optimize incoming connections
A fixed-target rule to Client B's IP address is needed in order for optimization to occur on Mobile Client B
The addition of a peering rule
Question 55
Company X has many offshore oil rigs they want to bring optimization to. The only available connection is through a satellite that has frequent bursts of packet loss. There are very few users per rig and HTTPS-based SharePoint performance is so poor they often time out pulling down even a small file. CIFS often does not work at all. They are considering the Steelhead Mobile solution to solve this problem. You suggest they deploy a Steelhead in-path at the data center and:
Steelhead Mobile with FEC turned on to help with lossy links
Steelhead Mobile with HS-TCP configuration
Steelhead Mobile running MX-TCP to deal with the loss
Deploy Steelhead appliances with MX-TCP to deal with the loss
Deploy Steelhead appliances with HS-TCP, Window Scaling, fixed-target rules, and TCP New Reno to overcome the loss