Assume a client's traffic is being processed only by a NAT; no SNAT or virtual server processing takes place. Also assume that the NAT definition specifies a NAT address and an origin address while all other settings are left at their defaults. If the origin server were to initiate traffic via the BIG-IP, What changes, if any, would take place when the BIG-IP processes such packets?

• A.The source address would be changed to the NAT address and destination address would be left unchanged.
• B.The source address would not change, but the destination address would be changed to the NAT address.
• C.The BIG-IP would drop the request since the traffic didn't arrive destined to the NAT address.
• D.The source address would not change, but the destination address would be changed to a self-IP of the BIG-IP.

Comment: *

Name: *

Email: *

Verification: *

Which log file should the BIG-IP Administrator check to determine if a specific user tried to log in to the 8IG-IP Configuration by utility?

• A./var/log/pam/tally/log
• B./var/log/trn
• C./ver/log/secure
• D./var/log/http.d

Comment: *

Name: *

Email: *

Verification: *

A BIG-IP has two load balancing virtual servers at 150.150.10.10:80 and 150.150.10.10:443. The port 80 virtual server has SNAT automap configured. There is also a SNAT configured at 150.150.10.11 set for a source address range of 200.200.1.0 / 255.255.255.0. All other settings are at their default states. If a client with the IP address 200.200.1.1 sends a request to https://150.150.10.10, What is the source IP address when the associated packet is sent to the pool member?

• A.Floating self IP address on VLAN where the packet leaves the system
• B.150.150.10.11
• C.Floating self IP address on VLAN where the packet arrives on the system
• D.200.200.1.1

Comment: *

Name: *

Email: *

Verification: *

How is persistence configured.

• A.Persistence is a global setting; once enabled, loadElbalancing choices are superceded by the persistence method that is specified.
• B.Persistence is a profile type; an appropriate profile is created and associated with virtual server.
• C.Persistence is an option for each pool member. When a pool is defined, each member's definition includes the option for persistence.
• D.Persistence is an option within each pool's definition.

Comment: *

Name: *

Email: *

Verification: *

When can a single virtual server be associated with multiple profiles?

• A.Often. Profiles work on different layers and combining profiles is common.
• B.Never. Each virtual server has a maximum of one profile.
• C.Rarely. One combination, using both the TCP and HTTP profile does occur, but it is the exception.
• D.Unlimited. Profiles can work together in any combination to ensure that all traffic types are supported in a given virtual server.

Comment: *

Name: *

Email: *

Verification: *