F5-CA Changed F5CAB2 Questions

In BIG-IP LTM,health monitorsare used to determine the availability of pool members and directly influence traffic flow decisions in the data plane.

Key characteristics of thedefault HTTP monitoraccording to BIG-IP Administration Data Plane Concepts:

Sends an HTTP request (typically GET /)

Expects an HTTP response code of200 OK

Any responseother than 200is treated as amonitor failure

A failed monitor causes the pool member to be markedoffline (down)

In this scenario:

Two pool members return404 Not Found

A 404 response indicates that the requested object was not found

This doesnotmeet the success criteria of the default HTTP monitor

These two members are therefore markedoffline

One pool member returns200 OK

This matches the expected response

The member is markedonline

Resulting Pool Member Availability:

2 members: Offline

1 member: Online

Why the Other Options Are Incorrect:

B– 404 responses are not considered healthy by the default HTTP monitor

C– At least one member responds with the expected 200 OK

D– Members returning 404 responses fail the monitor and cannot be marked online

Key Data Plane Concept Reinforced:

BIG-IP health monitors makebinary availability decisionsbased strictly on configured success criteria. For HTTP monitors, response codes matter—404 is a failure, even if the service is technically reachable.

===========

4647

Virtual Servers have a setting calledVLAN and Tunnel Trafficwhich defines where the BIG-IP "listens" for new connections.4849

Ingress Logic:A virtual server is an entry point. It must be enab50led on the VLAN where theClientresides. If a client is on the "51Internal" VLAN, the Virtual Server must be enabled there to receive the traffic.

Egress Logic:The BIG-IP system uses theTMM Routing TableandSelf-IPsto reach pool members. It doesnotneed the Virtual Server to be "enabled" on the destination VLAN (External) to send traffic there.

Default Behavior:By default, Virtual Servers are enabled on "All VLANs." However, if restricted for security, the administrator must ensure the Virtual Server is active on the client-facing (ingress) VLAN.

In a large-scale BIG-IP environment with hundreds of virtual servers, theNetwork Mapis the most effective tool for visualizing and auditing the relationships between various ADC objects.

The Network Map Functionality:The Network Map provides a hierarchical view of the local traffic objects. It allows an administrator to see the status and dependencies of Virtual Servers, Pools, Pool Members, and associatediRulesall in one screen.

Search and Filter:By navigating toLocal Traffic > Network Map, the administrator can use theAdvanced Filter. This feature allows for searching specifically for an iRule name or a string within an iRule definition. Once the filter is applied, the system displays only the Virtual Servers that are associated with that specific iRule.

Efficiency:While the "Virtual Server List" (Option D) can be customized to show columns for iRules, it is often cumbersome to scroll through hundreds of entries. The "iRules List" (Option B) displays the scripts themselves but does not provide a reverse-lookup list of all associated virtual servers in a single view as efficiently as the Network Map.

Summary of Relationships:The Network Map is specifically designed to answer the question, "What is this object connected to?" making it the primary administrative interface for impact analysis during configuration changes.

The primary distinction between Activ41e and Standby units revolves around which unit is currently processing traffic.

Traffic Objects (C & E):The unit in the43Activestate is the only one that answers ARP requests forVirtual Server addressesandFloating Self-IPs. The Standby unit remains "quiet" for these addresses to avoid IP conflicts on the network.

Monitors (A - False):Boththe Active and Standby units perform health monitors on pool members by default. This ensures that the Standby unit is ready to take over with an up-to-date view of the pool's health.

Failover (B - False):A failover trigger (like a VLAN fail-safe) causes the Active unit to go Standby and the Standby unit to go Active; it affects both.

Management (D - False):Configuration changes can technically be made on either unit (though it is best practice to make them on the Active unit) and then synchronized to the peer.