We primarily use it to create WAFs and wide IP (virtual server) configurations. Additionally, we leverage Global Server Load Balancing (GSLB) when we need to define access policies or create web application firewalls (WAFs). In those scenarios, F5 is our go-to solution.

Let's say we have servers in the DMZ or back-end that shouldn't communicate directly with the outside world or receive unwanted traffic. F5 comes in with virtual IPs to act as a middleman. Daily traffic gets routed according to our policies, like round robin. With four servers, F5 sends queries one by one to each, checking if they're healthy and ready to serve clients. That's a typical use case.

Additionally, if we need to inspect or modify packets (e.g., for SSL decryption), we can install tools on F5 to handle that offloading and send the traffic onward transparently to the back-end. These are some of the key features I use regularly.

And if we need to modify packets on the fly, like the certificates within the traffic, we can install them on the F5, perform traffic manipulation and offloading, and then send the traffic decrypted or encrypted to the backend in plain text. These are all capabilities we're quite familiar with.

The primary use cases of F5 BIG-IP Access Policy Manager are straightforward for what we wanted to do. 

I use F5 BIG-IP APM to connect to my company's private network and access the tools that I need.

We use F5 BIG-IP APM to control and monitor device access based on MAC addresses.

We use the product for load balancing. We use it to read, understand, and direct traffic.

I primarily used the solution for portal access.

It was scalable.

The solution is stable and reliable. 

Our primary use case for this solution is remote access VPN and VPI integration with VMware, and we deploy the solution on-premises.

Due to COVID-19, almost all of our customers are buying the virtual edition now. Our customers use this solution for connecting people from home to the office. APM is security encrypted and allows them to create an SSO (through a third-party) so they can access just about anything they could from their office computer, under normal circumstances. Everything is in one portal, including your SAS application and on-premise application.

The use case depends entirely on the client's specific requirements. We configure the APM accordingly. For instance, in some scenarios, we've used F5 for VPN purposes. In others, we've deployed F5 BIG-IP primarily as a load balancer.

The choice depends on the enterprise's needs. They might want application load balancing, network traffic load balancing, or something else entirely. It's often used for VPN-like functionality.

We primarily use the solution for access management.