An administrator has a requirement to keep an application session from timing out on port 80. What two changes can the administrator make to resolve the issue without affecting any existing services…

Creating a new firewall policy and placing it above existing ones does not inherently prevent session timeouts; the session TTL must be configured within the policy or its associated service, and policy order alone doesn't control timeout duration.

Creating a new service object for HTTP (port 80) and explicitly setting its session TTL to 'never' allows for granular control, ensuring that only sessions utilizing this specific service object will have an indefinite timeout, thereby not affecting other existing HTTP services or policies.

Setting the default TCP session TTL to 'never' using `config system-ttl` would apply to all new TCP sessions that do not have a more specific TTL configured in their firewall policy or custom service object. This change can resolve the issue for the target application and not affect existing services if those services already have explicit session TTLs defined, overriding the system default.

Setting the session TTL on an existing HTTP policy to 'maximum' would affect all applications using that policy, contradicting the requirement to only affect 'an' application session without impacting 'any existing services' more broadly.