Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:

When a BIG-IP Administrator changesmodule provisioning(for example, enablingASMon a system previously provisioned only forLTM), the BIG-IP system must restart theTraffic Management Microkernel (TMM)process.

TheTMM processis responsible for:

Traffic handling

LTM, ASM, and other traffic-processing modules

Enforcing security and application policies

Provisioning changes affect how traffic modules are loaded and integrated into TMM. As a result,TMM is restarted, which causes atemporary interruption of traffic processing. This is expected behavior and is why module provisioning changes should be planned during amaintenance window.

Why the other options are incorrect:

A. bdis related to blade/platform management, not module provisioning.

C. sshdhandles SSH access and is not affected by provisioning changes.

D. httpdsupports the Configuration Utility (GUI) and does not restart due to module provisioning.

Therefore, the correct answer isB. tmm.

===========

Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:

A BIG-IPdevice group cannot be deleted if it still contains device members, even if one of those devices has already been decommissioned or is unreachable. Before deleting the device group, the administrator mustexplicitly remove the decommissioned device from the device group configuration.

Once the removed or unreachable device is deleted from the device group membership, the BIG-IP system allows the remaining administrator to successfully delete the device group.

Why the other options are incorrect:

A. Remove all members from the device groupThis is not required; the key requirement is removing thedecommissioned device, not all members.

B. Make sure all members are in syncSynchronization status does not prevent device group deletion.

D. Disable the device groupDevice groups cannot be disabled; they must be modified or deleted.

Therefore, the correct prerequisite action is toremove the decommissioned device from the device group, makingCthe correct answer.

===========

Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:Management connectivity is protected by an allowed access list for the httpd daemon. Unlike TMM data ports which use 'Port Lockdown' settings, the management port's access is controlled by a specific 'Allow' list323232. If an administrator's IP is not explicitly included in this list, the Control Plane will reject HTTPS connection attempts to the management utility33.

Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:

Theaudit log(/var/log/audit) recordsconfiguration changesmade on the BIG-IP system, including:

Whomade the change (user account)

Whatwas changed (for example, a virtual server modification)

Whenthe change occurred

Howit was performed (GUI, TMSH, or API)

Why the other options are incorrect:

/var/log/securelogs authentication events such as login successes and failures, not configuration changes.

/var/log/ltmlogs traffic-management and runtime LTM events, not administrative configuration modifications.

Therefore, the correct log file for trackingwho changed a virtual serveris/var/log/audit.

Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:

On BIG-IP systems, SSH access restrictions are configured under the/sys sshdobject. Theallowproperty defines theIP addresses or networks permitted to connect to the management interface using SSH.

Thelistcommand is used to display the current configuration settings.

Therefore, tmsh list /sys sshd allow correctly displays the configured allowed IP ranges.

Why the other options are incorrect:

A (show)displays runtime or statistical information, not configuration values.

C and Dincorrectly reference /etc/hosts.allow; BIG-IP manages SSH access through TMSH objects, not by directly listing host files in this context.

Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration documents:

On a BIG-IP system,NTP (Network Time Protocol) configurationis part of thesystem-level configuration settings. In the Configuration Utility, NTP servers are configured under theSystem configuration hierarchy.

The correct navigation path is:

System > Configuration > Device > NTP

This location allows the administrator to:

Add, modify, or remove NTP servers

Ensure accurate system time synchronization

Maintain proper time alignment required for features such asConfigSync,HA failover, logging, and certificate validation

Why the other options are incorrect:

A. System > Platformis used for hardware-related settings.

B. System > Preferencesmanages UI and user preferences.

C. System > Servicescontrols system daemons and services, not time configuration.

Therefore, the correct answer isD. System > Configuration.

===========

Comprehensive and Detailed Explanation From BIG-IP Administration Control Plane Administration do38cuments: While HA state is managed under "Device Management," the specific failover behavior of a traffic object is linked to its configuration. A Virtual Address must be associated with a "Traffic Group" (usually traffic-group-1) to fail over. This association and the resulting floating status can be verified by viewing the Virtual Server or Virtual Address list under Local Traffic > Virtual Servers.