Where do you configure GTM client persistence? Case Study Title (Case Study):

A DNS listener object handles reception of incoming DNS queries on a specific IP and port but does not contain persistence configuration.

Wide IP is the correct location because the Wide IP object is the entity responsible for resolving DNS queries to specific pools and virtual servers, making it the logical place to enforce persistence policies. Persistence at the Wide IP level ensures that a client querying the same FQDN is returned the same IP address across multiple DNS requests. The persistence type, TTL, and mask are all configured within the Wide IP settings.

A load balancing method defines the algorithm for selecting pool members and does not include client persistence settings.

A DNS pool groups virtual servers together for selection but persistence is not configured at the pool level - it is configured at the Wide IP level above it.

Virtual server objects are LTM constructs for Layer 4-7 traffic; they are not the location for GTM DNS-level persistence configuration.