Question 16
What is the benefit of configuring Datastore Sync between SteelHeads?
- It allows up to four SteelHeads in a cluster access to the same datastore
- It gives high availability to the warm data patterns in exactly two SteelHeads
- It allows for seamless transition when upgrading to a larger SteelHead
- It allows for seamless transition from a physical to a virtual SteelHead
- It allows more efficient use of references by synchronizing them end-to-end between branch and datacenter
Question 17
Which of these are true statements?
- Transparency is a global setting affecting all in-path interfaces
- Transparency for SSOOP can only be achieved using the CLI and not the GUI
- Port Transparency utilizes the connection pooling function, but Full Transparency cannot
- Addressing is transparent to the client and server using in-path deployments, but not when using SSOOP
- Transparency is a setting only relevant to cloud deployments
Question 18
What is required for optimization to occur when deploying SteelHeads on an 802.1Q trunk?
- A single IP address routable to the in-path interface of the remote SteelHead
- An IP address configured on all VLANs where optimization is required
- A single IP on a VLAN and all traffic set as Correct Addressing
- A single IP address on the default VLAN and Simplified Routing set to none
- Full Transparency as a catch-all in-path rule and Simplified Routing set to Destination Only
Question 19
When a SteelHead is on a VLAN trunk, what is the required simplified routing setting?
- Destination and Source
- All
- None
- Destination Only
Question 20
Which SteelHead appliance deployment mode uses the Primary interface for optimization?
- Virtual in-path
- Physical in-path
- Serial Cluster
- Server-Side Out of Path (SSOOP)
- Interceptor