An administrator has a BIG-IP with management IP 192.168.1.10/24. The management network has a gateway at 192.168.1.1. The administrator wants to manage the device from a workstation on the 172.16.5.0/24 network. The workstation can ping the management gateway but cannot reach the BIG-IP management interface. What is the most likely cause?

The management IP is on a different subnet than the gateway.

The workstation's firewall is blocking HTTPS traffic.

The BIG-IP has no default management route configured.

The BIG-IP management interface is administratively down.

A BIG-IP has a management IP of 10.1.1.10/24 and a self-IP of 192.168.1.10/24 on the internal VLAN. The management network has a default gateway at 10.1.1.1. An administrator on the 192.168.1.0/24 network tries to SSH to the management IP 10.1.1.10. The connection fails. What is the most likely reason?

The BIG-IP does not have a route to the 192.168.1.0/24 network via the management interface.

The self-IP is on a different subnet than the management IP.

The SSH service is not enabled on the management interface.

The management interface is on the same subnet as the self-IP.

A security team requires that only the IT administration subnet (10.99.0.0/24) be allowed to access the BIG-IP management interface over SSH. The BIG-IP management IP is 10.99.0.10/24. Which configuration should the administrator apply to enforce this restriction?

Disable the SSH service and use only HTTPS.

Create an IP allow-list on the management interface that permits only 10.99.0.0/24.

Configure a firewall rule on the self-IP to block port 22.

Change the SSH port to a non-standard port.

An administrator is troubleshooting why HTTPS access to the BIG-IP management interface is failing from a remote site. The administrator can ping the management IP from the remote site. Which command should be used to verify that the HTTPS service is listening on the management interface?

Run 'traceroute' from the remote workstation to the BIG-IP.

Run 'tmsh show sys service' to list all services.

Run 'netstat -an' on the BIG-IP and look for port 443 in the LISTEN state.

Run 'ping' from the BIG-IP to the remote workstation.

F5Certified Administrator, BIG-IP

Domain 2Objective 3

Show Remote Connectivity to the BIG-IP Management Interface F5CAB1 Practice Questions (Page 2)

Part of the Identify management connectivity configurations domain, which makes up ~19% of our current practice bank. F5 does not publish an official question count, but from its 30-minute exam (~10–20 total, ~2–4 in this domain), expect 1–1 from this objective — we provide 16 practice questions to prepare you well beyond it. (estimate)

16questions here

4free pages

5concepts

Questions 6–10

6application · medium
An administrator has a BIG-IP with management IP 192.168.1.10/24. The management network has a gateway at 192.168.1.1. The administrator wants to manage the device from a workstation on the 172.16.5.0/24 network. The workstation can ping the management gateway but cannot reach the BIG-IP management interface. What is the most likely cause?
Select an answer first
7application · medium
A BIG-IP has a management IP of 10.1.1.10/24 and a self-IP of 192.168.1.10/24 on the internal VLAN. The management network has a default gateway at 10.1.1.1. An administrator on the 192.168.1.0/24 network tries to SSH to the management IP 10.1.1.10. The connection fails. What is the most likely reason?
Select an answer first
8application · medium
A security team requires that only the IT administration subnet (10.99.0.0/24) be allowed to access the BIG-IP management interface over SSH. The BIG-IP management IP is 10.99.0.10/24. Which configuration should the administrator apply to enforce this restriction?
Select an answer first
9application · medium
An administrator is troubleshooting why HTTPS access to the BIG-IP management interface is failing from a remote site. The administrator can ping the management IP from the remote site. Which command should be used to verify that the HTTPS service is listening on the management interface?
Select an answer first
10foundation · medium
Which command is used to test network connectivity to the BIG-IP management interface?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to F5CAB1

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by F5. “F5CAB1” is a trademark of its owner, used for identification only.

Show Remote Connectivity to the BIG-IP Management Interface F5CAB1 Practice Questions (Page 2)

Questions 6–10

A security team requires that only the IT administration subnet (10.99.0.0/24) be allowed to access the BIG-IP management interface over SSH. The BIG-IP management IP is 10.99.0.10/24. Which configuration should the administrator apply to enforce this restriction?

An administrator is troubleshooting why HTTPS access to the BIG-IP management interface is failing from a remote site. The administrator can ping the management IP from the remote site. Which command should be used to verify that the HTTPS service is listening on the management interface?

Which command is used to test network connectivity to the BIG-IP management interface?

Keep studying — Identify management connectivity configurations