830-01 Practice Exam Questions with Answers RCPE Certified Professional WAN Optimization Certification

5

4

3

2

1

WCCP

HighSpeed TCP

Routing

Port Labels

HTTP Protocol

Initial utilization of 30% becomes 75%

Drop from 90% of utilization to 70%

Initial utilization of 73% becomes 90%

Drop from 75% of utilization to 48% and shot up to 68%

Drop from 75% of utilization to 48% and shot up to 78%

Port 7800 is being blocked between the Steelhead Mobile Controller and the Steelhead appliance

Port 7810 is being blocked between the Steelhead Mobile client and the Steelhead appliance

Port 7801 is being blocked between the Steelhead Mobile client and the Windows TCP Stack

Port 7850 is being blocked between the Steelhead Mobile Controller and the Steelhead appliance

Port 7801 is being blocked between the Steelhead Mobile Controller and the Steelhead appliance

The Primary interface cannot be on the same subnet

The LAN In-path interface will be disabled

The WAN In-path interface will be disabled

The Steelhead appliance listens for the Interceptor on TCP port 7860

The connection is passed through

The next rule in the list is examined

The Interceptor appliance triggers an alarm

The Interceptor appliance discontinues redirecting any new connections and places this rule in admissions control

Organization of groups

Configuring individual Steelhead Mobile client users with different license groups

Configuration of fixed-target rule groups

Configuration of pass-through rule groups

All of the above

1

2

3, 4

1, 3, 4

1, 2, 3, 4, 5

Acceleration policy

Authentication policy

Endpoint policy

Port labels

Enable the “no in-path accept new” CLI command

Create an in-path rule on the Steelhead appliance to bypass the connections

On the Interceptor appliance, click on “Pause” for that particular Steelhead appliance

Schedule a job on the Steelhead appliance to remove itself from the cluster

All of the above

When upgrading a Virtual Steelhead appliance, it is not possible to preserve the existing datastore

Detach the existing datastore and re-attach to the new Virtual Steelhead appliance

Run vMotion and move the datastore to a different ESX host before performing the upgrade and then bring it back afterwards

Move the existing datastore to an NFS share and move it back after the upgrade

It allows for the ability to support multiple NICs on the Interceptor

It allows the Interceptor appliance to communicate with Steelhead appliances and other Interceptor appliances via more than one In-path interface

It allows the Interceptor appliance to communicate via Multicast to In-path interfaces on the Steelhead appliances

It allows the Interceptor appliance to be managed by In-path interfaces as well as the Primary interface

The Interceptor appliance uses round robin, for each TCP connection, regardless of source or destination IP address, and is equally load-balanced between a group of Steelhead appliances

The Interceptor appliance uses round robin, for each TCP connection, depending on source IP address, and is equally load-balanced between a group of Steelhead appliances

The Interceptor appliance uses hash assignment, for each TCP connection depending the hash value calculated from source and destination IP address, and is directed to a particular Steelhead appliance in the local cluster

The Interceptor appliance can dynamically determine and direct traffic for optimization to the least-loaded Steelhead appliances based on Steelhead appliance resource usage

The Interceptor appliance uses peer affinity, a Steelhead appliance in the local cluster that has been previously paired with a destination IP address is preferred

The Interceptor appliance uses peer affinity, a Steelhead appliance in the local cluster that has been previously paired with a remote Steelhead appliance is preferred

All Steelhead appliances in the network

Peer-neighbor Steelhead appliances as targets in one Load Balancing rule

Peer-neighbor Steelhead appliances not assigned as targets in any Load Balancing rule

Peer-neighbor Steelhead appliances assigned to all current Load Balancing rules

Replication traffic uses 16 KB blocks and causes fragmentation in the datastore

User traffic may contain sensitive traffic and should not be mixed with other traffic

Replication traffic may cause admission control therefore affecting user traffic

The traffic pattern between the two types of traffic is generally very different and therefore the datastore may wrap more quickly affecting performance

Locked secure vault

Firewalled status

Network interface error

Temperature

Memory paging

Enhanced auto-discovery

Simplified Routing

no in-path peering manual enable

in-path rule pass rulenum start

in-path peering rule pass rulenum 1

Nortel VPN

Cisco VPN client

Check Point

OpenVPN

Riverbed VPN client

Physical in-path and WCCP

Physical/virtual in-path and server-side out-of-path

Physical/virtual in-path and PBR

A and B

A, B, and C

EF21

0x48

0x58

0xb8

18

For each load-balancing rule, including the default rule.

For each load-balancing rule, excluding the default rule.

Only for the default rule.

For each load-balancing rule and in-path rule

For each load-balancing rule, in-path rule, including the default rule.

They require no routing changes

They require the use of WCCP or PBR for traffic redirection

They hide the original client IP address from the server

They require the use of a fixed-target rule on the client-side Steelhead appliance

They require the use of either physical in-path or virtual in-path on the client-side Steelhead appliance

Use the largest Steelhead appliance model

Enter the “in-path loopguard enable” command

Use more than one Steelhead appliance

Limit the number of TCP connections to be optimized

Put SERVER1 in a different subnet from SH11

4,665,000 bytes

9,330,000 bytes

3,110 bytes

6,220 bytes

2,325,000 bytes

show bootvar

show images

show info

show bootpar

show system

show version

The Steelhead appliance is only configured for transparent mode for SMB signing and MAPI encryption.

Windows 7 is not supported.

The client-side Steelhead appliance is not joined to the domain.

The server-side Steelhead appliance is not joined to the domain.

The Steelhead appliance only supports NTLM.

Intercept on outbound interface only

Multicast support

Able to redirect any TCP/UDP traffic

Uses UDP port 2048 for control messages

Multi-router support

The connection was forwarded to another Steelhead.

This connection was pass through.

Connection forwarding is working.

This connection was never established.

From the GUI, under Connections, select the connection and click on the Reset button

From the GUI, under Connections, select the connection and click on the Drop button

From the CLI: tcp connection send reset local-only local-addr 192.168.5.10:9999 remote-addr 192.168.5.90:80

From the CLI: tcp connection send reset remote-only local-addr 192.168.5.10 local-port 7800 remote-addr 192.168.5.90 remote-port 80

From CLI: tcp reset user 192.168.5.10

8

32

64

128

256

1, 2

2, 3

4, 5

3, 4, 5

1, 2, 3, 4, 5

> Show Con

Show Configuration

> show configuration all

# show configuration full

(config) # show con

in-path inpath0_0 enable

in-path oop enable

ip virtual enable

in-path virtual enable

in-path wccp_pbr enable

Hybrid mode

Virtual In-path mode

WCCP or Interceptor mode

Out-of-path mode

In-path mode

The SCC can be used to create all configuration for the Interceptors and its associated SteelHeads, as long as all the devices are in the same SCC group.

The SCC can create in-path rules policies the same as a SteelHead, as long as that is the only page enabled for the Interceptor.

The SCC can be used to configure the cluster of registered Interceptors and SteelHeads. Then, in-path rules and load balancing rules can be pushed to the interceptors.

The SCC can be used to create cluster policies, for the Interceptor to SteelHead connections only and not in-path or load balancing rules.

The SCC can only monitor the health, backup the configuration and upgrade Interceptors. Policies are only for SteelHeads. Interceptors and SteelHead Mobile are not supported.

There are two Interceptor appliances: 172.16.19.111 and 172.16.19.112 in parallel mode, and one Steelhed appliance. 172.16.10.101.

There are two Interceptor appliances: 172.16.19.111 and 172.16.19.112 in failover mode, and one Steelhead appliance. 172.16.10.101.

This scenario should work appropriately and the devices are configured correctly.

This scenario will only work if you add one more Steelhead appliance.

To keep similarly sized SteelHead models peering with each other.

To ensure load is distributed evenly throughout the cluster.

To maximize the benefits of SDR by maintaining SteelHead peering relationships.

To ensure asymmetrically routed connections are optimized.

To make sure cluster SteelHeads remain connected to the same Interceptor.

A branch warning optimized connection

A branch mode optimized connection

An unlicensed connection

A pass-through connection

A normal optimized connection

It is not a problem, but part of the regular operation

The management process crashed

The optimization process crashed

The management process received permission to connect to a Granite Core device

The sport process received permission to connect to a Granite Core device

Passive key derivation

SSL proxy support and SNI (Server name indication)

SSL advanced mode

Early start/late finish

An alternate unencrypted port must be open on the server, and a copy of the server ID file must be imported to the server side SteelHead.

An alternate unencrypted port must be open on the server, and a proxy server ID file must be created on the server-side SteelHead.

An encrypted port must be open on the server, and a proxy server ID file must be created on the server-side SteelHead.

An encrypted port must be open on the server, and a copy of the server ID file must be imported to the server-side SteelHead.

This Steelhead appliance did not intercept the SYN packet for this TCP connection.

This Steelhead appliance did not intercept the SYN+ packet for this TCP connection.

This connection is not being optimized.

This connection will be optimized after the TCP handshake.

All traffic has the LAN and WAN interface index.

All traffic has the WAN interface index.

All traffic has the LAN interface index.

All traffic has the primary interface index.

High CPU Utilization

Paging alarm

Admission control on connections

Admission control on memory

Admission control on system

The Steelhead appliance is receiving only HTTP traffic from the router.

The Steelhead appliance will not receive HTTP traffic from the router.

There is no need to use access-lists on the router to select HTTP traffic.

The Steelhead appliance is only receiving traffic on port TCP 1741.

Virtual Box

Hyper-V

KVM

VMware Fusion

ESXi

5 ms

10 ms

15 ms

20 ms

The Cloud optimization stops working after 5 minutes

The Cloud optimization continues to work with the last information received from the Portal

The SteelHead will try HTTP (port 80) to contact the Portal once it sees no response using 443

The Cloud optimization Service cannot redirect traffic because DNS resolution is performed through Primary interface

Read-Only

Read/Write

Write-Only

Deny

Accept

You are required to supply login credentials to every Steelhead appliance

You will automatically be logged into to every Steelhead appliance

All users will use the same user name and password

It is not possible to use TACACS+ or RADIUS

Fixed-target rule is needed on the client-side Steelhead appliance

Change the WCCP to use Redirect Out instead of Redirect In

Remove Redirect-IN from the LAN at the Branch Office

Add Redirect-IN on the WAN at the HQ

Remove fixed-target rule from the server-side Steelhead appliance

View Logs

Current Connections

Alarm Status

Interface Statistics

Monitored Ports

Networking, Optimization, Software, System

Networking, Optimization, Rules, System

Networking, Optimization, Security, System

Networking, Acceleration, Security, System

Fixed-target rule

Enable RIP/OSPF on the routers

Enable Simplified Routing

Enable QoS

Enable RIP/OSPF on the Steelhead appliances

Email

RADIUS

SNMP traps

Syslog