FreeQAs
 Request Exam  Contact
  • Home
  • View All Exams
  • New QA's
  • Upload
PRACTICE EXAMS:
  • Oracle
  • Fortinet
  • Juniper
  • Microsoft
  • Cisco
  • Citrix
  • CompTIA
  • VMware
  • ISC
  • SAP
  • EMC
  • PMI
  • HP
  • Salesforce
  • Other
  • Oracle
    Oracle
  • Fortinet
    Fortinet
  • Juniper
    Juniper
  • Microsoft
    Microsoft
  • Cisco
    Cisco
  • Citrix
    Citrix
  • CompTIA
    CompTIA
  • VMware
    VMware
  • ISC
    ISC
  • SAP
    SAP
  • EMC
    EMC
  • PMI
    PMI
  • HP
    HP
  • Salesforce
    Salesforce
  1. Home
  2. F5 Certification
  3. F5CAB2 Exam
  4. F5.F5CAB2.v2026-07-22.q41 Dumps
  • «
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • »
Download Now

Question 6

The BIG-IP Administrator wants to provide quick failover between the F5 LTM devices that are configured as an HA pair with a single Self IP using the MAC Masquerade feature. The administrator configures MAC masquerade for traffic-group-1 using the following command:
`tmsh modify /cm traffic-group traffic-group-1 mac 02:12:34:56:00:00`
However, the Network Operations team identifies an issue with using the same MAC address across multiple VLANs. As a result, the administrator enables Per-VLAN MAC Masquerade to ensure a unique MAC address per VLAN by running:
`tmsh modify /sys db tm.macmasqaddr_per_vlan value true`
What would be the resulting MAC address on a tagged VLAN with ID 1501? (Choose one answer)

Correct Answer: D
insert code

Question 7

Refer to the exhibit.

The network team creates a new VLAN on the switches. The BIG-IP Administrator creates a new VLAN and a Self IP on the BIG-IP device, but theservers on the new VLAN are NOT reachablefrom the BIG-IP device.
Which action should the BIG-IP Administrator take to resolve this issue? (Choose one answer)

Correct Answer: C
For BIG-IP to send or receive traffic on a VLAN, that VLANmust be bound to a physical interface or a trunk. Creating a VLAN object and a Self IP alone isnot sufficientto establish data-plane connectivity.
From the exhibit:
* The VLAN (vlan_1033) exists and has a tag defined.
* A Self IP is configured and associated with the VLAN.
* However, traffic cannot reach servers on that VLAN.
This indicates aLayer 2 connectivity issue, not a Layer 3 or HA issue.
Whyassigning a physical interfacefixes the problem:
* BIG-IP VLANs do not carry traffic unless they are explicitly attached to:
* Aphysical interface(e.g., 1.1), or
* Atrunk
* Without an interface assignment, the VLAN is effectively isolated and cannot transmit or receive frames, making servers unreachable regardless of correct IP addressing.
Why the other options are incorrect:
* A. Set Port Lockdown to Allow AllPort Lockdown controls which services can be accessedon the Self IP(management-plane access), not whether BIG-IP can reach servers on that VLAN.
* B. Change Auto Last Hop to enabledAuto Last Hop affects return traffic routing for asymmetric paths. It does not fix missing Layer 2 connectivity.
* D. Create a Floating Self IP addressFloating Self IPs are used for HA failover. They do not resolve reachability issues on a single device when the VLAN itself is not connected to an interface.
Conclusion:
The servers are unreachable because the VLAN hasno physical interface assigned. To restore connectivity, the BIG-IP Administrator mustassign a physical interface (or trunk) to the VLAN, enabling Layer 2 traffic flow.
insert code

Question 8

Refer to the exhibit.

The network team creates a new VLAN on the switches. The BIG-IP Administrator creates a new VLAN and a Self IP on the BIG-IP device, but the servers on the new VLAN are NOT reachable from the BIG-IP device.
Which action should the BIG-IP Administrator take to resolve this issue? (Choose one answer)

Correct Answer: C
For BIG-IP to send or receive traffic on a VLAN, that VLAN must be bound to a physical interface or a trunk. Creating a VLAN object and a Self IP alone is not sufficient to establish data-plane connectivity.
From the exhibit:
* The VLAN (vlan_1033) exists and has a tag defined.
* A Self IP is configured and associated with the VLAN.
* However, traffic cannot reach servers on that VLAN.
This indicates a Layer 2 connectivity issue, not a Layer 3 or HA issue.
Why assigning a physical interface fixes the problem:
* BIG-IP VLANs do not carry traffic unless they are explicitly attached to:
* A physical interface (e.g., 1.1), or
* A trunk
* Without an interface assignment, the VLAN is effectively isolated and cannot transmit or receive frames, making servers unreachable regardless of correct IP addressing.
Why the other options are incorrect:
* A. Set Port Lockdown to Allow AllPort Lockdown controls which services can be accessed on the Self IP (management-plane access), not whether BIG-IP can reach servers on that VLAN.
* B. Change Auto Last Hop to enabledAuto Last Hop affects return traffic routing for asymmetric paths. It does not fix missing Layer 2 connectivity.
* D. Create a Floating Self IP addressFloating Self IPs are used for HA failover. They do not resolve reachability issues on a single device when the VLAN itself is not connected to an interface.
Conclusion:
The servers are unreachable because the VLAN has no physical interface assigned. To restore connectivity, the BIG-IP Administrator must assign a physical interface (or trunk) to the VLAN, enabling Layer 2 traffic flow.
insert code

Question 9

Which three iRule events are likely to be seen in iRules designed to select a pool for load balancing? (Choose three.)

Correct Answer: A,C,E
12
In the BIG-IP system, pool selection must occur on the client-side of the connection, before the system attempts to connect to a pool 3member. The events listed 4are the primary entry points for making these decisions:
* CLIENT_ACCEPTED (E): This is a Layer 4 event triggered when the BIG-IP accepts a TCP connection. It is the earliest point where a pool can be assigned based on the client's source IP address or the destination port.
* CLIENT_DATA (A): This event is triggered when the system receives a "chunk" of data on the client- side. It is often used for non-HTTP protocols (like custom TCP protocols) to inspect the payload and select a pool based on its contents.
* HTTP_REQUEST (C): This is a Layer 7 event. It occurs once the BIG-IP has fully parsed the HTTP headers. This is the most common event for pool selection, allowing the administrator to route traffic based on the URI, Host header, or cookies.
Events like SERVER_SELECTED or SERVER_CONNECTED occur after the load balancing decision has already been made, and HTTP_RESPONSE or SERVER_DATA occur after the server has already started communicating back, making them too late for initial pool selection.
insert code

Question 10

What is the result when a BIG-IP Administrator manually disables a pool member? (Choose one answer)

Correct Answer: A
Comprehensive and Detailed Explanation From BIG-IP Administration Data Plane Concepts documents:
In BIG-IP LTM, a pool member state directly affects how traffic is handled at the data plane level. When a pool member is manually disabled, BIG-IP changes the member's availability state to disabled, which has specific and predictable traffic-handling consequences.
According to BIG-IP Administration Data Plane Concepts:
A disabled pool member:
Does not accept new connections
Continues to process existing non-persistent connections until they naturally close Is removed from load-balancing decisions, including persistence lookups Most importantly for this question:
Persistent connections
(such as those created using source-address persistence, cookie persistence, or SSL persistence) are not honored for a disabled pool member BIG-IP will not send new persistent traffic to a disabled member, even if persistence records exist Therefore, when a pool member is manually disabled, it stops processing persistent connections, while allowing existing non-persistent flows to drain gracefully.
Why the Other Options Are Incorrect:
B - Persistent connections are not honored for a disabled pool member
C - Existing connections are not immediately terminated when a pool member is disabled D - Only the disabled pool member stops accepting new connections, not all pool members Key Data Plane Concept Reinforced:
Manually disabling a pool member is a graceful administrative action that prevents new and persistent traffic from reaching the member while allowing existing connections to complete, which is critical for maintenance and troubleshooting scenarios.
insert code
  • «
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • »
[×]

Download PDF File

Enter your email address to download F5.F5CAB2.v2026-07-22.q41 Dumps

Email:

FreeQAs

Our website provides the Largest and the most Latest vendors Certification Exam materials around the world.

Using dumps we provide to Pass the Exam, we has the Valid Dumps with passing guranteed just which you need.

  • DMCA
  • About
  • Contact Us
  • Privacy Policy
  • Terms & Conditions
©2026 FreeQAs

www.freeqas.com materials do not contain actual questions and answers from Cisco's certification exams.