Given thatBIGIP-
(Choose one.)
Correct Answer:
B
When installing a BIG-IP software versionwith a HotFixon anew boot volume, F5 requires that both thebase TMOS imageand theHotFix imagebe installed together as part of the same installation workflow.
The correct process is:
Specify thebase TMOS ISO
Specify theHotFix ISOthat corresponds to that base version
Instruct the system tocreate a new boot volume
Install both images into that new volume
This is achieved with the following tmsh syntax:
tmsh install /sys software BIGIP-<version>.iso hotfix Hotfix-BIGIP-<version>-ENG.iso create-volume HD1.2 This command:
Installs the base image first
Applies the HotFix on top of the base image
Creates and installs everything onHD1.2
Leaves the currently active volume untouched for rollback
Why the other options are incorrect
* A. Installing only the hotfix
A HotFix cannot be installed by itself on a new volume. A base image must already be present.
* C. Using create instead of install
The create keyword is not valid for software installation operations.
* D. Using copy
The copy command does not install software images or hotfixes.
Which port is an exception to the Port Lockdown function of Self-IPs if a device-group synchronization cluster is configured?
Correct Answer:
B
Self-IPs implement a security feature known asPort Lockdown, which limits which services are reachable on a Self-IP.
However, certain services required for BIG-IP device-to-device communication bypass Port Lockdown to ensure cluster and HA functionality.
TCP 4353
TCP port4353is used byDevice Service Clustering (DSC)for:
Device trust establishment
Configuration synchronization
Failover communication
Because BIG-IP devices must always be able to communicate for HA functions to remain operational, port 4353 isexempt from Port Lockdown rules.
Why the other options are incorrect
* A. TCP 443
Not required for device trust or synchronization.
HTTPS access is fully controlled by Port Lockdown.
* C. UDP 53
DNS traffic is not required for synchronization and has no exemption under Port Lockdown.
A BIG-IP Administrator needs to verify the state of equipment in the data center. A BIG-IP appliance has asolid yellow indicatoron the status LED.
How should the administrator interpret this LED indicator?
Correct Answer:
C
Explanation
BIG-IP hardware platforms use chassis LEDs to indicate system health states.
Asolid yellow status LEDtypically indicates awarning condition, such as:
A non-critical hardware alert
A temperature threshold nearing limit
A minor fan or sensor irregularity
Other non-fatal environmental or system conditions
This state reflects awarning-level alarm, meaning the unit is operational but requires investigation.
Why the other options are incorrect
* A. Halted or EUD mode
This is associated with different LED patterns (usually flashing conditions or specific color codes), not a solid yellow status LED.
* B. Standby in device group
HA state is not indicated by the chassis status LED.
Standby status is alogicaldevice state, not a hardware LED state.
* D. Power supply failure
Power supply indicators use separate LEDs located on each power module (usually flashing amber/red), not the system status LED.
Thus, asolid yellow status indicatorsignifies awarning-level alarm.
A BIG-IP Administrator needs to purchase new licenses for a BIG-IP appliance.
The administrator needs to know:
Whether a module is licensed
The memory requirement for that module
Where should the administrator view this information in theSystem menu?
Correct Answer:
D
To understand:
Which modules arelicensed
Which modules areprovisioned
Theresource requirements(CPU / RAM) of each module
The administrator uses:
System » Resource Provisioning
This page displays:
All modules present in the license
Whether they are enabled or disabled
Required memory to activate each module
CPU and disk allocation information
Provisioning level options (None / Minimal / Nominal / Dedicated)
This is the exact location where BIG-IP administrators evaluate module capacity before enabling or purchasing licensing upgrades.
Why the other options are incorrect:
* A. Configuration » OVSDB
Used for network virtualization integrations, not licenses or modules.
* B. Software Management
Used for software image installation, not licensing.
* C. Configuration » Device
Displays hostname, failover settings, device properties — not module resource requirements.
Thus, module licensing and memory requirement data are found underResource Provisioning.
A BIG-IP Administrator is responsible for deploying a new software image on an F5 BIG-IP HA pair and has scheduled a one-hour maintenance window.
With a focus on minimizing service disruption, which of the following strategies is the most appropriate?
Correct Answer:
C
For BIG-IP high-availability (HA) pairs, F5's recommended upgrade workflow prioritizesservice continuity,predictable failover, andminimal downtime. The established best-practice sequence is:
Upgrade the standby unit first
Because the standby device is not passing traffic, upgrading and rebooting it does not impact production.
Boot the standby unit into the newly installed version
Once online, the administrator verifies basic health, device sync status, cluster communication, and module functionality.
Perform a controlled failover to the upgraded unit
Traffic shifts to the newly upgraded device, allowing validation of the configuration and operational behavior under real traffic loads.
Upgrade the second device (now standby)
The previously active device becomes standby after failover, allowing it to be safely upgraded and rebooted without interruption.
This phased approach ensures only one device is unavailable at a time, allowing continuous traffic flow throughout the upgrade process.
Why the Correct Answer is C
OptionCexactly matches F5's documented production-safe upgrade method:
Upgrade thestandbynode first
Reboot into new image
Failover to upgraded device
Validate
Upgrade the remaining (now-standby) device
This procedure minimizes risk and traffic disruption.
Why the other options are incorrect:
* A. Upgrade the active node first
Upgrading the active device requires removing it from service and failing over abruptly. This is not recommended and increases service disruption risk.
* B. Resetting device trust
Resetting trust is unnecessary and can disrupt configuration sync, peer communication, and cluster operation. It is not part of any standard upgrade workflow.
* D. Upgrading and rebooting both nodes simultaneously
This would causetotal outage, because both HA members would be unavailable at the same time.