EX188 Container Operations And Lifecycle Practice Test 2 — 15 Questions

Question 1

A container named db_cache has stopped unexpectedly. An administrator wants to see the standard output logs generated by this container prior to its exit. Which command should be used?

Accepted Answer

podman logs db_cache. The `podman logs` command retrieves the standard output (stdout) and standard error (stderr) logs from a container, whether it is running or has stopped. Since the container `db_cache` has exited, `podman logs db_cache` will display the logs generated prior to its exit. This is the standard and correct way to access container logs in Podman.

Answer

podman inspect --logs db_cache

Answer

podman output db_cache

Answer

podman history db_cache

Question 2

An administrator needs to inspect low-level configuration, network settings, and state details of a running container named redis_cache in JSON format. Which command provides this?

Accepted Answer

podman inspect redis_cache. `podman inspect` is the canonical command for retrieving low-level metadata about a container, image, volume, or network. It outputs a comprehensive JSON document containing configuration, state, network settings, mounts, environment variables, and more. Since the question explicitly asks for JSON-format low-level details, `podman inspect redis_cache` is the correct choice.

Answer

podman show redis_cache

Answer

podman details redis_cache

Answer

podman query --json redis_cache

Question 3

A container named app_server is running and consuming excessive CPU. An administrator needs to gracefully stop this container with a 30-second timeout before forcing termination. Which command accomplishes this?

Accepted Answer

podman stop --time 30 app_server. `podman stop --time 30 app_server` is correct because `--time` (or `-t`) sets the number of seconds Podman waits after sending SIGTERM before escalating to SIGKILL. This is exactly the graceful-stop-with-30-second-timeout behavior required. The container's main process gets SIGTERM, and only if it does not exit within 30 seconds does Podman force-kill it.

Answer

podman kill --signal SIGTERM --timeout 30 app_server

Answer

podman halt -s 30 app_server

Answer

podman terminate --grace-period=30 app_server

Question 4

An administrator has created a systemd service file named container-web.service using podman generate systemd. Where should this file be placed for a rootless user to manage it as a user-level service?

Accepted Answer

~/.config/systemd/user/. For rootless Podman containers, systemd user services must reside in the user's systemd configuration directory, which is ~/.config/systemd/user/. This allows the user to manage the service with systemctl --user commands without requiring root privileges. Placing the unit file here ensures it is loaded when the user's systemd instance starts, typically at login.

Answer

~/.local/share/podman/systemd/

Answer

/etc/systemd/system/

Answer

/var/lib/containers/systemd/

Question 5

An administrator is troubleshooting a container that fails its health check repeatedly. The container definition needs a health check that runs curl -f http://localhost/ || exit 1 every 30s, with a 5s timeout and 3 retries, starting after a 10s grace period. Which flag combination implements this correctly in podman run?

Accepted Answer

podman run --health-cmd="curl -f http://localhost/ || exit 1" --health-interval=30s --health-timeout=5s --health-retries=3 --health-start-period=10s webapp. The correct flag combination uses Podman's health check flags: --health-cmd for the command, --health-interval for the period, --health-timeout for the timeout, --health-retries for retry count, and --health-start-period for the initial grace period. Option C matches all required parameters exactly, including the '|| exit 1' failure semantics. Podman's health check system mirrors Docker's HEALTHCHECK instruction and uses these specific flag names.

Answer

podman run --healthcheck="curl -f http://localhost/" --interval=30 --timeout=5 --retries=3 webapp

Answer

podman run --health-probe="curl -f http://localhost/" --health-delay=10s webapp

Answer

podman run --check-command="curl -f http://localhost/" --check-period=30s webapp

Question 6

An administrator needs to list all containers, including both running and stopped ones, on the system. Which command should be used?

Accepted Answer

podman ps -a. The podman ps command lists containers, and the -a (or --all) flag includes both running and stopped containers. Without -a, podman ps shows only running containers. This mirrors the Docker CLI behavior and is the standard way to view all container states.

Answer

podman status --all

Answer

podman list --all

Answer

podman containers show

Question 7

An administrator wants to monitor resource usage (CPU, memory, block I/O, network I/O) of all running containers in real-time. Which command provides this functionality?

Accepted Answer

podman stats. podman stats displays real-time resource usage statistics (CPU, memory, block I/O, network I/O, and PIDs) for running containers, similar to docker stats. It continuously refreshes and can be filtered to specific containers. This is the direct command for live resource monitoring.

Answer

podman monitor resources

Answer

podman top

Answer

podman system df

Question 8

An administrator wants to immediately stop and remove a running container named temp_test in a single command. Which command should be used?

Accepted Answer

podman rm -f temp_test. The podman rm -f command force-removes a running container by sending SIGKILL to its processes and then deleting the container in a single operation. The -f (or --force) flag is what allows removal of a running container without a prior podman stop. This is the canonical one-step command for the scenario described.

Answer

podman kill --remove temp_test

Answer

podman delete --force temp_test

Answer

podman stop --rm temp_test

Question 9

An administrator needs to view the processes running inside a specific container named worker_node, along with custom ps options like -ef to see full command arguments. Which command accomplishes this?

Accepted Answer

podman top worker_node -ef. podman top runs a ps-like command inside the container's PID namespace and accepts custom ps arguments, so 'podman top worker_node -ef' shows all processes with full command lines. This is the purpose-built command for inspecting in-container processes with tailored output.

Answer

podman ps --processes worker_node

Answer

podman exec worker_node ps -ef

Answer

podman inspect --processes worker_node

Question 10

An administrator is using Podman Quadlets to manage containers via systemd. Where must the Quadlet .container configuration file be placed for system-wide root containers?

Accepted Answer

/etc/containers/systemd/. For system-wide root containers managed by Quadlets, the .container file must be placed in /etc/containers/systemd/. This directory is monitored by the podman-system-generator, which converts Quadlet files into systemd unit files at boot or on daemon-reload.

Answer

/etc/systemd/system/containers/

Answer

/var/lib/containers/systemd/quadlets/

Answer

/etc/systemd/system/

Question 11

An administrator needs to restart a running container named app_v1 so that configuration changes take effect. Which command performs a container restart?

Accepted Answer

podman restart app_v1. The 'podman restart' command stops and then starts the specified container in a single operation, which re-reads the container's configuration and applies any changes that require a fresh process. It is the direct equivalent of 'docker restart' and is the correct verb for restarting a running container by name.

Answer

podman reload app_v1

Answer

podman cycle app_v1

Answer

podman refresh app_v1

Question 12

An administrator needs to attach to the terminal of a currently running container named backend_app to view its active console output interactively. Which command should be used?

Accepted Answer

podman attach backend_app. `podman attach` connects the current terminal's STDIN/STDOUT/STDERR to a running container's main process (PID 1), letting the administrator view live console output and interact with it. This is the direct equivalent of `docker attach` and is the correct tool for viewing an active console interactively.

Answer

podman console backend_app

Answer

podman connect backend_app

Answer

podman join backend_app

Question 13

An administrator needs to pause all processes inside a running container named db_master without stopping it. Which command accomplishes this?

Accepted Answer

podman pause db_master. The `podman pause` command sends the SIGSTOP signal to all processes inside the specified container, freezing their execution without terminating the container or its processes. This allows the container to be resumed later with `podman unpause`, which sends SIGCONT. Unlike stopping, the container's state and memory are preserved.

Answer

podman suspend db_master

Answer

podman freeze db_master

Answer

podman hold db_master

Question 14

An administrator wants to run a one-off command (/bin/sh) interactively inside an existing running container named legacy_app. Which command should be used?

Accepted Answer

podman exec -it legacy_app /bin/sh. podman exec -it legacy_app /bin/sh runs a new process inside the already-running container with an interactive TTY, which is exactly what is needed for a one-off interactive shell. The -i keeps stdin open and -t allocates a pseudo-TTY.

Answer

podman run -it legacy_app /bin/sh

Answer

podman enter legacy_app /bin/sh

Answer

podman attach legacy_app --shell=/bin/sh

Question 15

An administrator is troubleshooting container exit codes. A container exited with code 137. What does this specific exit code typically signify in container engines?

Accepted Answer

The container was terminated forcefully by SIGKILL (often due to Out-Of-Memory).. Exit code 137 is calculated as 128 + 9, where 9 is the signal number for SIGKILL. This means the container's main process was forcibly terminated with SIGKILL, most commonly because the kernel OOM killer invoked it when the container exceeded its memory cgroup limit, or because an administrator ran `podman kill`.

Answer

The container executed an invalid system call blocked by seccomp.

Answer

The container encountered an application-level syntax error.

Answer

The container startup script had a permission denied error.