Which configuration of tasks and Availability Zones meets these requirements?

Explanations:

With only one task per Availability Zone, if one zone becomes unavailable, the application cannot handle the required load of 100 requests per second.

While deploying two tasks per Availability Zone provides some redundancy, it does not meet the required load capacity of 100 requests per second (2 tasks * 60 requests per second = 120 requests per second, which is enough, but redundancy during updates might not be sufficient).

One task per Availability Zone is insufficient to handle the full request load of 100 requests per second. Additionally, a rolling update with 50% minimum healthy tasks cannot guarantee availability during node failures.

Deploying two tasks in each of three Availability Zones ensures enough capacity (3 zones * 2 tasks = 6 tasks, providing 360 requests per second), while also providing redundancy and high availability during rolling updates.