Containerisation with Docker — Concept Check
Questions on Containerisation with Docker. Each microservice is packaged as a Docker image; multi-stage builds keep images small, and images are tagged with the commit SHA for traceability.
Questions in this quiz
8 questions on Containerisation with Docker — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.You are deploying a Spring Boot microservice using Docker. Which practice ensures the smallest possible image size?
- AUse a large base image
- BRun as root user
- CInclude Maven in the final image
- DUse multi-stage builds
2.A developer tags a Docker image with 'latest' for production deployment. What is a potential risk?
- AFaster deployment times
- BImage becomes immutable
- CIncreased image size
- DRollback becomes impossible
3.Your Dockerfile for a Spring Boot application uses a single-stage build. What is a likely consequence?
- ALarger image size
- BBetter cache reuse
- CFaster build times
- DImproved security
4.A Docker image is tagged with a commit SHA. What is the primary benefit of this approach?
- AImproved performance
- BTraceability to exact code
- CSimplified versioning
- DReduced image size
5.A Kubernetes deployment manifest specifies 'imagePullPolicy: IfNotPresent'. What does this mean?
- AThe image is not re-pulled if it exists on the node
- BThe image is never pulled
- CThe image is pulled only once
- DThe image is always pulled
6.In a multi-stage Dockerfile, what is the purpose of separating the build and runtime environments?
- ATo include all dependencies
- BTo run as root
- CTo keep the final image small
- DTo avoid using a JRE
7.A developer uses the 'spring-boot:build-image' Maven goal. What is a key advantage of this approach?
- ANo Dockerfile needed
- BRequires root access
- CSlower builds
- DLarger image size
8.Which practice is essential for securing a Spring Boot container in production?
- ADisable health probes
- BRun as a non-root user
- CUse 'latest' tag
- DInclude build tools