Task Definitions

Correct Answer: Volumes

Persistent storage in the context of a containerized application is typically achieved through the use of volumes. Volumes are storage units that can be mounted into containers to maintain data across restarts of containers and tasks. Therefore, in a task definition, which is used by services like AWS ECS (Elastic Container Service) to run Docker containers, the 'Volumes' field must be specified to configure persistent storage for an application container. The 'Log configuration' field is used to define log routing and storage options (like CloudWatch) for the container's standard output and standard error streams, not for persistent storage of application data. 'Environment variables' are used to pass configuration data into the container at runtime, such as API keys or database URLs, but they do not provide persistent storage capability. 'Desired count' refers to the number of instantiations of a task definition to run and maintain at any given time; this is related to the scaling and availability of the service, and it is unrelated to data persistence.

Correct Answer: environment variables

Environment variables are the correct answer because they can be used to store the database endpoint and other connection details required by the containerized application. Secrets are used for storing sensitive information, but not necessarily for database access. MountPoints, ulimits, volumes, and repositoryCredentials are not related to database access.

Correct Answer: cpu and memory

To define resource usage for a container in a task definition, you must specify both 'cpu' and 'memory' parameters. Other options like vCPU, diskSpace, bandwidth, containerSize, storage, workload, capacity, compute, and network are not valid parameters in task definitions.