Which solutions will update the Elastic Beanstalk environment with the new application version after the developer completes the changes?
(Choose two.)
Package the application code into a .zip file. Use the AWS Management Console to upload the zip file and deploy the packaged application.
Package the application code into a .tar file. Use the AWS Management Console to create a new application version from the .tar file. Update the environment by using the AWS CLI.
Package the application code into a .tar file. Use the AWS Management Console to upload the .tar file and deploy the packaged application.
Package the application code into a .zip file. Use the AWS CLI to create a new application version from the .zip file and to update the environment.
Package the application code into a .zip file. Use the AWS Management Console to create a new application version from the .zip file. Rebuild the environment by using the AWS CLI.
Explanations:
The application code can be packaged into a .zip file and uploaded via the AWS Management Console to deploy the new application version.
AWS CLI is mentioned but there is no direct method in the console to update the environment using a .tar file. Using a .tar file for deployment is less common.
The AWS Management Console can upload the .tar file, but it cannot automatically deploy or update the environment from there.
The application code can be packaged into a .zip file, and using AWS CLI to create a new application version and update the environment is a valid approach.
While the .zip file can be uploaded and a new application version can be created, rebuilding the environment via CLI is not required for updates.
I scheme that the answer is:
Package the application code into a .zip file. Use the AWS Management Console to upload the zip file and deploy the packaged application.