All new Amazon EC2 Windows instances in the account must have a third-party .msi agent installed and kept up to date automatically. The environment already uses AWS Systems Manager and instances are tagged. Which combination of steps will achieve this with the least operational overhead? (Choose two.)

To deploy and maintain a third-party agent on new and existing EC2 Windows instances with the least operational overhead, you should leverage AWS Systems Manager Distributor and State Manager. First, create a Systems Manager Distributor package containing the .msi installer for the third-party agent. Distributor allows you to securely store and distribute software packages to your instances. Second, create a Systems Manager State Manager association. This association should use the AWS-ConfigureAWSPackage document, specifying your Distributor package. Target instances using the appropriate tag, ensuring new instances with this tag automatically receive the agent. Schedule this association to run daily to ensure the agent is installed on new instances and kept up-to-date on existing ones. Incorrect options: Enabling Systems Manager Inventory is useful for tracking software, but it doesn't deploy or update agents. Using AWS-RunRemoteScript is less efficient for package management than AWS-ConfigureAWSPackage, which is designed for this purpose. Creating an OpsItem and a maintenance window is for operational issues and scheduled tasks, not for continuous package deployment and updates across all instances.