A cloud provider is using OpenStack Neutron to manage networking. They want to integrate F5 BIG-IP as a load balancer service. The integration requires the BIG-IP to be aware of Neutron's network topology. What is the best way to achieve this?

Use the BIG-IP's CLI to manually configure networks.

Use the BIG-IP's iControl REST API to query Neutron.

Use the Neutron LBaaS API to manage the BIG-IP.

Use SNMP to discover network topology.

A service provider is using an OpenFlow-based SDN controller to manage a network that includes F5 BIG-IP appliances. The BIG-IP is used for L4-L7 services. The provider wants to ensure that the BIG-IP can continue to operate if the SDN controller fails. What is the best design consideration?

Use the BIG-IP as an OpenFlow switch to maintain flow tables.

Ensure that the BIG-IP is not dependent on the OpenFlow controller for its forwarding decisions.

Deploy a redundant pair of OpenFlow controllers.

Configure the OpenFlow switches to use a reactive mode to handle new flows.

A network engineer is troubleshooting a deployment where F5 BIG-IP is connected to an OpenFlow-enabled switch. The BIG-IP is configured as a load balancer for a web application. The engineer notices that new connections to the application fail, but existing connections continue to work. What is the most likely cause?

The BIG-IP's SNAT is misconfigured.

The OpenFlow switch is blocking all traffic to the BIG-IP.

The BIG-IP's virtual server is down.

The OpenFlow switch has no flow entry for the new connections and cannot contact the controller.

How do REST APIs impose constraints on F5 configuration in SDN environments?

F5 devices must be configured exclusively through the CLI.

F5 devices must support REST APIs for programmatic configuration.

F5 devices cannot be configured programmatically.

F5 devices must use proprietary APIs only.

A security team is implementing micro-segmentation with NSX and wants to use F5 BIG-IP for L7 inspection. They have a requirement that all traffic between application tiers must be inspected by the BIG-IP. However, they also want to minimize the performance impact of the inspection. What is the best approach?

Disable micro-segmentation to allow the BIG-IP to inspect all traffic.

Use the BIG-IP's virtual server as the default gateway for all workloads.

Use NSX service chaining to redirect traffic to the BIG-IP, and configure the BIG-IP to only inspect traffic that matches specific L7 signatures.

Deploy the BIG-IP in inline mode on every host.

F5Certified Solution Expert, Cloud

Domain 2Objective 4

2.04 Recognize the Constraints Imposed by Various SDN Technologies on F5 Components 402 Practice Questions (Page 3)

Part of the Section 2 : CLOUD INFRASTRUCTURE DESIGN domain, which makes up ~27% of our current practice bank. F5 does not publish an official question count, but from its 105-minute exam (~40–70 total, ~11–19 in this domain), expect 1–2 from this objective — we provide 25 practice questions to prepare you well beyond it. (estimate)

25questions here

5free pages

8concepts

Questions 11–15

11application · medium
A cloud provider is using OpenStack Neutron to manage networking. They want to integrate F5 BIG-IP as a load balancer service. The integration requires the BIG-IP to be aware of Neutron's network topology. What is the best way to achieve this?
Select an answer first
12expert · hard
A service provider is using an OpenFlow-based SDN controller to manage a network that includes F5 BIG-IP appliances. The BIG-IP is used for L4-L7 services. The provider wants to ensure that the BIG-IP can continue to operate if the SDN controller fails. What is the best design consideration?
Select an answer first
13application · medium
A network engineer is troubleshooting a deployment where F5 BIG-IP is connected to an OpenFlow-enabled switch. The BIG-IP is configured as a load balancer for a web application. The engineer notices that new connections to the application fail, but existing connections continue to work. What is the most likely cause?
Select an answer first
14foundation · easy
How do REST APIs impose constraints on F5 configuration in SDN environments?
Select an answer first
15expert · hard
A security team is implementing micro-segmentation with NSX and wants to use F5 BIG-IP for L7 inspection. They have a requirement that all traffic between application tiers must be inspected by the BIG-IP. However, they also want to minimize the performance impact of the inspection. What is the best approach?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to 402

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. “402” is a trademark of its owner, used for identification only.

2.04 Recognize the Constraints Imposed by Various SDN Technologies on F5 Components 402 Practice Questions (Page 3)

Questions 11–15

A cloud provider is using OpenStack Neutron to manage networking. They want to integrate F5 BIG-IP as a load balancer service. The integration requires the BIG-IP to be aware of Neutron's network topology. What is the best way to achieve this?

A service provider is using an OpenFlow-based SDN controller to manage a network that includes F5 BIG-IP appliances. The BIG-IP is used for L4-L7 services. The provider wants to ensure that the BIG-IP can continue to operate if the SDN controller fails. What is the best design consideration?

How do REST APIs impose constraints on F5 configuration in SDN environments?

Keep studying — Section 2 : CLOUD INFRASTRUCTURE DESIGN