Given that BIGIP-
(Choose one.)
When installing a BIG-IP software version with a HotFix on a new boot volume, F5 requires that both the base TMOS image and the HotFix image be installed together as part of the same installation workflow.
The correct process is:
Specify the base TMOS ISO
Specify the HotFix ISO that corresponds to that base version
Instruct the system to create 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 on HD1.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 two items demonstrate the creation of a new volume for software images?
(Choose two.)
In BIG-IP, software images are installed on boot volumes (for example, HD1.1, HD1.2, HD1.3, etc.).
To install software on a new volume, the administrator must instruct the system to create a new boot location before installation.
There are two correct ways to create a new volume:
A . tmsh command (with correct syntax)
tmsh install software image /shared/images/BIGIP-<version>.iso volume HD1.5 create-volume
This syntax correctly includes:
install software image
full path to ISO (/shared/images/...)
volume name (HD1.5)
create-volume keyword
This instructs BIG-IP to create the new boot volume as part of the installation.
C . Using the GUI System > Disk Management
From the Disk Management menu, the administrator can:
Select ''New Volume''
Enter the volume identifier (e.g., HD1.5)
Apply changes
This GUI method is officially supported and explicitly creates a new boot volume before installing the software.
Why the other options are incorrect:
B . Incorrect tmsh syntax
Missing /shared/images/ path
Incorrect command structure
D . Incorrect command structure
Missing required keywords and correct command hierarchy
E . Software Management Install does NOT create volumes
This installs to an existing volume only
The GUI install dialog does not create new boot volumes
Thus, only Option A and Option C properly create a new software volume.
A BIG-IP Administrator needs to install a HotFix on a standalone BIG-IP device.
The device currently has HD1.1 as the Active Boot Location.
The administrator has already reactivated the license and created a UCS archive.
In which sequence should the administrator perform the remaining steps?
When installing a software upgrade with a HotFix on BIG-IP, the correct workflow requires:
Install the base TMOS image on an unused boot volume
Install the corresponding HotFix onto that same boot volume
Activate the updated boot volume to boot into the new software
This method ensures:
The existing active system (HD1.1) is untouched
The upgrade occurs in a new, clean volume (HD1.2)
The HotFix applies properly to the same base image
The administrator can revert to HD1.1 if issues occur
Option C matches the correct F5 upgrade sequence:
1. Install base image on HD1.2
2. Install HotFix on HD1.2
3. Activate HD1.2
Why the other options are incorrect:
A . Install HotFix before base image
HotFixes must be applied after the base image; not valid.
B . Installing a HotFix on the active boot location (HD1.1)
Not recommended and does not use a clean new volume.
Also does not involve installing the base image.
D . Activating HD1.2 before installing anything
Cannot activate an empty or invalid boot volume.
Thus, Option C is the correct sequence.
Which of the following are resource allocation (provisioning) settings for BIG-IP modules?
(Choose two.)
BIG-IP module provisioning determines how CPU, memory, and disk resources are allocated to each licensed module. F5 defines a specific set of supported provisioning levels.
Valid provisioning (resource allocation) settings
Nominal
Allocates a standard, balanced amount of system resources to a module.
Intended for typical production deployments where multiple modules may be provisioned at the same time.
Dedicated
Allocates all available system resources to a single module.
Used when the BIG-IP device is dedicated to running only one module (for example, ASM-only or APM-only deployments).
No other modules can be provisioned when one is set to Dedicated.
These two options are valid and supported provisioning levels.
Why the other options are incorrect
Maximum
This is not a valid BIG-IP provisioning level.
BIG-IP does not use ''Maximum'' as a resource allocation setting.
Limited
This is also not a supported provisioning level.
BIG-IP uses levels such as None, Minimal, Nominal, and Dedicated (module-dependent), not Limited.
Which configuration file can a BIG-IP administrator use to verify the provisioned modules?
Provisioning settings define which modules are enabled and how system resources are allocated to them.
These provisioning declarations are stored in:
/config/bigip.conf
This file contains:
Full module provisioning statements
TMSH-equivalent provisioning configurations such as:
sys provision ltm { level nominal }
sys provision asm { level nominal }
It is the primary system configuration file that stores all active provisioning details.
Why the other answers are incorrect
A . /config/bigip.license
Shows licensed modules, not provisioned modules.
B . /config/bigip_base.conf
Stores base networking (VLANs, Self-IPs, routes), not provisioning.
D . config.ucs
A backup archive, not a live configuration file.
Thus, the correct file to review active module provisioning is /config/bigip.conf.
Steven Miller
6 days agoMonica Walker
25 days agoTiffany Jackson
1 month agoRonald Cooper
2 months agoAdam Bailey
2 months agoKenneth Mitchell
3 months agoRebecca Robinson
3 months agoDavid Moore
3 months agoKevin Harris
3 months agoMonica Howard
3 months agoRachel Gonzalez
3 months agoTiffany Walker
3 months agoMarya
4 months agoVon
4 months agoWhitney
4 months agoMarcos
4 months agoJosue
5 months agoKate
5 months agoPhil
5 months agoZack
6 months agoGlen
6 months agoAdela
6 months agoLuann
6 months agoStefany
7 months agoJosphine
7 months agoJeanice
7 months agoAlease
7 months agoCeola
7 months agoChuck
8 months agoLorean
8 months agoMozell
8 months agoLacey
8 months ago