Choose the best explanation for why a Docker registry mirror is used in a development environment.
Think about how mirrors help when many users pull the same images repeatedly.
A Docker registry mirror caches images locally, which speeds up image downloads and reduces load on the main registry and internet bandwidth.
Given the Docker daemon configuration below, what message will appear in the daemon logs when pulling an image?
{
"registry-mirrors": ["https://mirror.example.com"]
}Check how Docker logs registry mirror usage when configured correctly.
When a registry mirror is configured correctly, Docker logs that it is using the mirror URL for image pulls.
Select the valid JSON configuration to set two registry mirrors: https://mirror1.example.com and https://mirror2.example.com.
Remember that JSON arrays require commas between items.
The correct configuration uses a JSON array with comma-separated mirror URLs as strings.
You configured a registry mirror in daemon.json, but Docker still pulls images directly from Docker Hub. What is the most likely cause?
Check network connectivity and mirror server health.
If the mirror is unreachable or returns errors, Docker ignores it and pulls directly from Docker Hub as fallback.
Arrange the steps below in the correct order to set up and confirm a Docker registry mirror is working.
Think about verifying the mirror before configuring and restarting Docker.
First verify the mirror is reachable, then configure daemon.json, restart Docker, and finally test by pulling an image and checking logs.