An application running on Amazon ECS needs configurable limits (maximum simultaneous connections and max transactions per second) that will change over time. The developer requires that updates to these configuration values be deployed automatically with no downtime. Which solution satisfies these requirements?

The correct solution uses AWS AppConfig, which is designed for dynamic configuration management and safe deployment of application configurations. Installing the AppConfig agent on ECS tasks allows the application to retrieve updated configurations. Granting an IAM role access ensures secure communication. AppConfig's deployment strategies, like Canary10Percent20Minutes, enable gradual rollout of configuration changes, minimizing risk and ensuring no downtime. Incorrect options: Modifying application code and using CodeDeploy with an in-place deployment would require a full application redeployment, leading to downtime and not addressing dynamic configuration changes without code updates. AWS CDK is for infrastructure as code, not dynamic application configuration. Using an ECSCanary launch type is for service updates, not configuration updates within a running application. An AWS Lambda function and CloudWatch alarm could trigger updates, but it's an overly complex and less direct solution compared to AppConfig, which is purpose-built for this use case.