Containers · Compose interview questions

1. A.a group of services managed together under one Compose configuration
2. B.a mechanism to selectively enable groups of services for different scenarios
3. C.an ordering directive that controls service start order without guaranteeing readiness
4. D.a docker-compose.yml defining multi-container applications declaratively

Answer + AI explanation with Pro

1. A.Override file
2. B.Compose file
3. C.Project
4. D.Compose network

Answer + AI explanation with Pro

1. A.Compose file — a default bridge network letting services reach each other by service name
2. B.Compose file — a Compose-defined probe used to mark a service healthy before dependents start
3. C.Compose file — a docker-compose.yml defining multi-container applications declaratively
4. D.Compose file — a mechanism to selectively enable groups of services for different scenarios

Answer + AI explanation with Pro

1. A.a default bridge network letting services reach each other by service name
2. B.a group of services managed together under one Compose configuration
3. C.a container definition in Compose describing image, ports, and configuration
4. D.an ordering directive that controls service start order without guaranteeing readiness

Answer + AI explanation with Pro

1. A.Service
2. B.Healthcheck
3. C.depends_on
4. D.Compose file

Answer + AI explanation with Pro

1. A.Service — a mechanism to selectively enable groups of services for different scenarios
2. B.Service — a container definition in Compose describing image, ports, and configuration
3. C.Service — a docker-compose.override.yml merged automatically to adjust settings per environment
4. D.Service — a group of services managed together under one Compose configuration

Answer + AI explanation with Pro

1. A.a mechanism to selectively enable groups of services for different scenarios
2. B.a Compose-defined probe used to mark a service healthy before dependents start
3. C.a group of services managed together under one Compose configuration
4. D.a docker-compose.override.yml merged automatically to adjust settings per environment

Answer + AI explanation with Pro

1. A.Project
2. B.Profiles
3. C.Healthcheck
4. D.depends_on

Answer + AI explanation with Pro

1. A.Project — a Compose-defined probe used to mark a service healthy before dependents start
2. B.Project — a group of services managed together under one Compose configuration
3. C.Project — a container definition in Compose describing image, ports, and configuration
4. D.Project — a docker-compose.yml defining multi-container applications declaratively

Answer + AI explanation with Pro

1. A.a default bridge network letting services reach each other by service name
2. B.a docker-compose.override.yml merged automatically to adjust settings per environment
3. C.an ordering directive that controls service start order without guaranteeing readiness
4. D.a mechanism to selectively enable groups of services for different scenarios

Answer + AI explanation with Pro

1. A.Compose network
2. B.Service
3. C.depends_on
4. D.Override file

Answer + AI explanation with Pro

1. A.Compose network — a group of services managed together under one Compose configuration
2. B.Compose network — an ordering directive that controls service start order without guaranteeing readiness
3. C.Compose network — a container definition in Compose describing image, ports, and configuration
4. D.Compose network — a default bridge network letting services reach each other by service name

Answer + AI explanation with Pro

1. A.a Compose-defined probe used to mark a service healthy before dependents start
2. B.an ordering directive that controls service start order without guaranteeing readiness
3. C.a container definition in Compose describing image, ports, and configuration
4. D.a docker-compose.override.yml merged automatically to adjust settings per environment

Answer + AI explanation with Pro

1. A.Override file
2. B.Compose network
3. C.Healthcheck
4. D.depends_on

Answer + AI explanation with Pro

1. A.depends_on — a docker-compose.override.yml merged automatically to adjust settings per environment
2. B.depends_on — a docker-compose.yml defining multi-container applications declaratively
3. C.depends_on — an ordering directive that controls service start order without guaranteeing readiness
4. D.depends_on — a group of services managed together under one Compose configuration

Answer + AI explanation with Pro

1. A.a Compose-defined probe used to mark a service healthy before dependents start
2. B.a docker-compose.yml defining multi-container applications declaratively
3. C.a container definition in Compose describing image, ports, and configuration
4. D.an ordering directive that controls service start order without guaranteeing readiness

Answer + AI explanation with Pro

1. A.Service
2. B.Healthcheck
3. C.depends_on
4. D.Project

Answer + AI explanation with Pro

1. A.Healthcheck — a Compose-defined probe used to mark a service healthy before dependents start
2. B.Healthcheck — a docker-compose.yml defining multi-container applications declaratively
3. C.Healthcheck — a group of services managed together under one Compose configuration
4. D.Healthcheck — a default bridge network letting services reach each other by service name

Answer + AI explanation with Pro

1. A.a container definition in Compose describing image, ports, and configuration
2. B.a mechanism to selectively enable groups of services for different scenarios
3. C.a docker-compose.override.yml merged automatically to adjust settings per environment
4. D.a default bridge network letting services reach each other by service name

Answer + AI explanation with Pro

1. A.Override file
2. B.Profiles
3. C.depends_on
4. D.Project

Answer + AI explanation with Pro

1. A.Profiles — an ordering directive that controls service start order without guaranteeing readiness
2. B.Profiles — a mechanism to selectively enable groups of services for different scenarios
3. C.Profiles — a container definition in Compose describing image, ports, and configuration
4. D.Profiles — a docker-compose.yml defining multi-container applications declaratively

Answer + AI explanation with Pro

1. A.a default bridge network letting services reach each other by service name
2. B.a container definition in Compose describing image, ports, and configuration
3. C.a docker-compose.override.yml merged automatically to adjust settings per environment
4. D.a mechanism to selectively enable groups of services for different scenarios

Answer + AI explanation with Pro

1. A.Service
2. B.Project
3. C.Override file
4. D.Compose network

Answer + AI explanation with Pro

1. A.Override file — a default bridge network letting services reach each other by service name
2. B.Override file — a group of services managed together under one Compose configuration
3. C.Override file — a docker-compose.override.yml merged automatically to adjust settings per environment
4. D.Override file — a mechanism to selectively enable groups of services for different scenarios

Answer + AI explanation with Pro

1. A.create and start all services in the background
2. B.run a shell in the running web service container
3. C.list the containers for the current Compose project
4. D.build or rebuild the images for the services

Answer + AI explanation with Pro

1. A.docker compose logs -f
2. B.docker compose down
3. C.docker compose up -d
4. D.docker compose ps

Answer + AI explanation with Pro

1. A.docker compose up -d — follow aggregated logs from all services
2. B.docker compose up -d — list the containers for the current Compose project
3. C.docker compose up -d — create and start all services in the background
4. D.docker compose up -d — run a shell in the running web service container

Answer + AI explanation with Pro

1. A.create and start all services in the background
2. B.list the containers for the current Compose project
3. C.run a shell in the running web service container
4. D.stop and remove containers, networks created by up

Answer + AI explanation with Pro

1. A.docker compose logs -f
2. B.docker compose exec web sh
3. C.docker compose ps
4. D.docker compose down

Answer + AI explanation with Pro

1. A.docker compose down — run a shell in the running web service container
2. B.docker compose down — follow aggregated logs from all services
3. C.docker compose down — list the containers for the current Compose project
4. D.docker compose down — stop and remove containers, networks created by up

Answer + AI explanation with Pro