Quality Assurance & Improvement Flashcards

Which Docker Swarm feature automatically replaces a failed service task on a healthy node?

Answer: Task rescheduling via the reconciliation loop

Swarm's manager continuously reconciles desired vs actual state and schedules new tasks to replace failed ones on healthy nodes automatically.

A team wants to prevent 'latest' tags from being deployed to production Swarm services. Which approach enforces this policy?

Answer: Use image pinning in stack files with explicit digest references

Referencing images by digest in stack compose files ensures exactly the tested image is deployed, preventing accidental 'latest' mutations.

What does the 'docker system prune -a' command remove, and what QA risk does it carry?

Answer: All unused images including those not linked to a container, risking removal of cached base images needed for CI builds

'-a' extends the prune to all unused images (not just dangling ones), which can delete base images cached for faster CI builds if no container references them.

Which Docker logging driver is most appropriate for a production environment that requires centralized log aggregation with structured JSON output?

Answer: fluentd

The fluentd driver forwards logs to a Fluentd aggregator in real time, enabling structured, centralized log collection suitable for production observability.

In a CI pipeline, 'docker build' exits with code 1. Which step should be taken first to diagnose the failure?

Answer: Check the build log output for the specific RUN instruction that failed

The build log identifies the exact failing RUN step and its stderr, providing the most direct path to diagnosing the failure cause.

What is the function of 'docker service rollback' compared to 'docker service update --rollback'?

Answer: 'docker service rollback' reverts to the previous service spec; '--rollback' is used to configure rollback parameters

'docker service rollback' is a dedicated command that immediately reverts the service to its previous configuration, while '--rollback' in update sets rollback policy parameters.

Which Dockerfile instruction, when used incorrectly, most commonly leads to unnecessarily large image sizes that fail image size quality gates?

Answer: RUN (installing packages without cleaning up cache in the same layer)

Each RUN creates a new layer; installing packages and cleaning up in separate RUN instructions leaves the package cache committed in an intermediate layer, bloating the image.