.
Within the pool definition
Within the node definition
Within the virtual server definition
Within the pool member definition
No SSL certificates are required on the BIG-IP
The BIG-IP's SSL certificates must only exist
The BIG-IP's SSL certificates must be issued from a certificate authority
The BIG-IP's SSL certificates must be created within the company hosting the BIG-IPs
Synching should not be performed
The first system to be updated will assume the Active role
This is not possible since both systems are updated simultaneously
The older system will issue SNMP traps indicating a communication error with the partner
The source address would not change, but the destination address would be translated to the origin address
The destination address would not change, but the source address would be translated to the origin address
The source address would not change, but the destination address would be translated to the NAT's address
The destination address would not change, but the source address would be translated to the NAT's address
A virtual server that has both ClientSSL and ServerSSL profiles can still support cookie persistence
Decrypting traffic at the BIG-IP allows the use of iRules for traffic management, but increases the load on the pool member
When any virtual server uses a ClientSSL profile, all SSL traffic sent to the BIG-IP is decrypted before it is forwarded to servers
If a virtual server has both a ClientSSL and ServerSSL profile, the pool members have less SSL processing than if the virtual server had only a ClientSSL profile
All changes to TEST1 are propagated to TEST2
Some of the changes to TEST1 may propagate to TEST2
Changes to TEST1 cannot affect TEST2 once TEST2 is saved
When TEST1 is changed, the administrator is prompted and can choose whether to propagate changes to TEST2
If the destination of the traffic does not match a virtual server, the traffic will be discarded
If the destination of the traffic does not match a virtual server, the traffic will be forwarded based on routing tables
If the destination of the traffic matches a virtual server, the traffic will be processed per the virtual servers definition
If the destination of the traffic matches a virtual server, the traffic will be forwarded, but it cannot be load-balanced since no SNAT has been configured
The connection request is not processed
The connection request is sent to an apology server
The connection request is load-balanced to an available pool member
The connection request is refused and the client is sent a "server not available" message
As long as network communication is not lost, no change will occur
Nothing. Fail-over due to loss of voltage will not occur if the voltage is lost for less than ten seconds
When the cable is disconnected, both systems will become active. When the voltage is restored, unit two will revert to standby mode
When the cable is disconnected, both systems will become active. When the voltage is restored, both systems will maintain active mode
All open connections are lost.
All open connections are maintained.
When persistence mirroring is enabled, open connections are maintained even if a fail-over occurs.
Long-lived connections such as Telnet and FTP are maintained, but short-lived connections such as HTTP are lost.
All open connections are lost, but new connections are initiated by the newly active BIG-IP, resulting in minimal client downtime.
The SNAT must be enabled for all VLANs.
The SNAT must be enabled for the VLANs where desired packets leave the BIG-IP.
The SNAT must be enabled for the VLANs where desired packets arrive on the BIG-IP.
The SNAT must be enabled for the VLANs where desired packets arrive and leave the BIG-IP.
CLI access to the serial console port
SSH access to the management port
SSH access to any of the switch ports
HTTP access to the management port
HTTP access to any of the switch ports
HTTPS access to the management port
HTTPS access to any of the switch ports
Never. Each virtual server has a maximum of one profile.
Often. Profiles work on different layers and combining profiles is common.
Rarely. One combination, using both the TCP and HTTP profile does occur, but it is the exception.
Unlimited. Profiles can work together in any combination to ensure that all traffic types are supported in a given virtual server.
The active device will take the action specified for the failure.
The standby device also detects the failure and assumes the active role.
The active device will wait for all connections to terminate and then fail-over.
The standby device will begin processing virtual servers that have failed, but the active device will continue servicing the functional virtual servers.
Pool1
Pool2
None. The request will be dropped.
Unknown. The pool cannot be determined from the information provided.
Ratio values
Priority values
Health monitors
Connection limits
Load-balancing mode
The active system will note the failure in the HA table.
The active system will reboot and the standby system will go into active mode.
The active system will fail-over and the standby system will go into active mode.
The active system will restart the traffic management module to eliminate the possibility that BIG-IP is the cause for the network failure.
The process should always be run from the standby system
The process should always be run from the system with the latest configuration.
The two /config/bigip.conf configuration files are synchronized (made identical) each time the process is run.
Multiple files, including /config/bigip.conf and /config/bigip_base.conf, are synchronized (made identical) each time the process is run.
Licenses only have to be reactivated for RMAs - no other situations.
Licenses generally have to be reactivated during system software upgrades.
Licenses only have to be reactivated when new features are added (IPv6, Routing Modules, etc) - no other situations.
Never. Licenses are permanent for the platform regardless the version of software installed.
TCP
HTTP
HTTPS
ServerSSL
Pool1
Pool2
None. The request will be dropped.
Unknown. The pool cannot be determined from the information provided.
Rule(s)
Pool(s)
Monitor(s)
Node address(es)
Load-balancing method(s)
Specify the desired MAC address for each VLAN for which you want this feature enabled.
Specify the desired MAC address for each self-IP address for which you want this feature enabled.
Specify the desired MAC address for each VLAN on the active system and synchronize the systems.
Specify the desired MAC address for each floating self-IP address for which you want this feature enabled.
The member has no monitor assigned to it.
The member has a monitor assigned to it and the most recent monitor was successful.
The member has a monitor assigned to it and the monitor did not succeed during the most recent timeout period.
The member's node has a monitor assigned to it and the monitor did not succeed during the most recent timeout period.
Persistence is an option within each pool's definition.
Persistence is a profile type; an appropriate profile is created and associated with virtual server.
Persistence is a global setting; once enabled, load-balancing choices are superceded by the persistence method that is specified.
Persistence is an option for each pool member. When a pool is defined, each member's definition includes the option for persistence.
Wait!
Here's an interesting quiz for you.