F5 F5CAB1 Online Practice Questions and Exam Preparation

F5 F5CAB1 Online Questions & Answers

• Question 51:

  Given that BIGIP-.iso and Hotfix-BIGIP--ENG.iso have been uploaded to /shared/ images on an F5 device, what is the appropriate tmsh command to prepare and update the BIG-IP device with the hotfix of a software version on a new volume HD1.2? (Choose one.)

  A. tmsh install /sys software hotfix Hotfix-BIGIP--ENG.iso create-volume HD1.2
  B. tmsh install /sys software BIGIP-.iso hotfix Hotfix-BIGIP--ENG.iso create-volume HD1.2
  C. tmsh create /sys software hotfix Hotfix-BIGIP--ENG.iso volume HD1.2
  D. tmsh copy /sys software hotfix Hotfix-BIGIP--ENG.iso volume HD1.2
  B. tmsh install /sys software BIGIP-.iso hotfix Hotfix-BIGIP--ENG.iso create-volume HD1.2

  ---

  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 thebase TMOS ISO Specify the HotFix ISO that 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-.iso hotfix Hotfix-BIGIP--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.

• Question 52:

  Which of the following are resource allocation (provisioning) settings for BIG-IP modules? (Choose two.)

  A. Maximum
  B. Nominal
  C. Dedicated
  D. Limited
  B. Nominal
  C. Dedicated

  ---

  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.

• Question 53:

  An F5 VE has been deployed into a VMware environment via an OVF file.

  An administrator wants to configure the management IP address so the VE can be accessed for further setup.

  Which two are valid methods for configuring the management-ip address? (Choose two.)

  A. Log into the remote console and configure the management IP by running the config executable.
  B. Log into the remote console and configure the management IP through TMSH using: create sys management-ip /
  C. Log into the remote console and configure the management IP through TMSH using: create ltm management-ip /
  D. Log into the remote console and configure the management IP by running the setup command.
  A. Log into the remote console and configure the management IP by running the config executable.
  B. Log into the remote console and configure the management IP through TMSH using: create sys management-ip /

  ---

  A newly deployed BIG-IP Virtual Edition (VE) in VMware requires initial configuration of itsmanagement- ip address so it can be accessed over the network. F5 provides several valid mechanisms during initial console access:

  A. Running the config utility

  The config script is available on new BIG-IP installations and VE deployments.

  It launches a guided text-based wizard allowing configuration of:

  Management IP

  Netmask

  Default route

  This is a standard and recommended method during first-time setup.

  B. Using TMSH with create sys management-ip

  Administrators can enter TMSH directly from the console and run:

  create sys management-ip /

  The management-ip object resides under sys , not under ltm or any other module.

  This is the correct tmsh method for defining the management interface address.

  Why the other options are incorrect:

  C. create ltm management-ip

  There is no such object under /ltm.

  LTM handles traffic objects (virtual servers, pools), not system management interfaces.

  D. Running the setup command

  The setup command is used for general system configuration butdoes not configure the management- ip .

  It is not the supported method for initial management IP assignment on VE deployments. Therefore, the valid methods are running the config utility and using the sys management-ip command within TMSH.

• Question 54:

  A BIG-IP Administrator needs to troubleshoot HTTPS access to the Configuration Utility on the management interface. Which two interfaces can be used with tcpdump to capture management-plane traffic? (Choose two.)

  A. mgmt
  B. eth0
  C. 0.0
  D. tmm
  A. mgmt
  B. eth0

  ---

  Management-plane traffic is handled by the dedicated management interface.

  On BIG-IP systems:

  mgmt is the logical management interface name eth0 is the underlying Linux interface mapped to the management port Both can be used with tcpdump to capture management traffic. Interfaces such as 0.0 or tmm capture data-plane traffic only.