2. Which of the following is the correct syntax to initialize a swarm with a specific advertise address?
easy
A. docker swarm create --advertise 192.168.1.10
B. docker swarm start --advertise-addr 192.168.1.10
C. docker swarm init --advertise-addr 192.168.1.10
D. docker swarm init -a 192.168.1.10
Solution
Step 1: Recall correct command syntax
The correct command to initialize swarm with advertise address is docker swarm init --advertise-addr <IP>.
Step 2: Identify incorrect options
docker swarm start and docker swarm create are invalid commands. The short flag -a is not recognized for advertise address.
Final Answer:
docker swarm init --advertise-addr 192.168.1.10 -> Option C
Quick Check:
Use --advertise-addr with init [OK]
Hint: Use full flag --advertise-addr with init [OK]
Common Mistakes:
Using 'start' or 'create' instead of 'init'
Using short flag '-a' which is invalid
Omitting --advertise-addr flag
3. What will be the output of the command docker swarm init --advertise-addr 10.0.0.5 if the node is already part of a swarm?
medium
A. Error: This node is already part of a swarm
B. Swarm initialized successfully with advertise address 10.0.0.5
C. Warning: Advertise address ignored, node already in swarm
D. Swarm initialized but advertise address not set
Solution
Step 1: Understand swarm init behavior on existing swarm node
If a node is already in a swarm, running docker swarm init again causes an error because it cannot reinitialize.
Step 2: Check output messages
The command will output an error message indicating the node is already part of a swarm, not success or warning.
Final Answer:
Error: This node is already part of a swarm -> Option A
Quick Check:
Init on existing swarm node = error [OK]
Hint: Init fails if node already in swarm [OK]
Common Mistakes:
Assuming init overwrites existing swarm
Expecting a warning instead of error
Thinking advertise address is ignored silently
4. You ran docker swarm init --advertise-addr 192.168.0.100 but other nodes cannot join the swarm. What is the most likely problem?
medium
A. The join token expired immediately after init
B. You forgot to run docker swarm join on the manager node
C. Swarm mode is not supported on this Docker version
D. The advertise address is set to an IP not reachable by other nodes
Solution
Step 1: Analyze advertise address role
The advertise address tells other nodes where to connect. If it is set to an IP unreachable by others, they cannot join.
Step 2: Evaluate other options
Join tokens are used on worker nodes, not manager. Swarm mode is supported in modern Docker versions. Join tokens do not expire immediately.
Final Answer:
The advertise address is set to an IP not reachable by other nodes -> Option D
Quick Check:
Advertise address must be reachable [OK]
Hint: Check advertise IP reachability for joining nodes [OK]
Common Mistakes:
Trying to join on manager node
Assuming join tokens expire instantly
Ignoring network connectivity issues
5. You want to initialize a swarm on a node with multiple network interfaces. Which command ensures other nodes connect via the interface with IP 172.16.5.10?
hard
A. docker swarm init --advertise-addr 172.16.5.10
B. docker swarm init --listen-addr 172.16.5.10
C. docker swarm init --advertise-addr eth1
D. docker swarm init --interface 172.16.5.10
Solution
Step 1: Identify correct flag for advertise address
The --advertise-addr flag sets the IP address other nodes use to connect to the manager.
Step 2: Eliminate incorrect options
--listen-addr sets the address the manager listens on internally, not what others connect to. Using interface name or unknown flags is invalid.
Final Answer:
docker swarm init --advertise-addr 172.16.5.10 -> Option A
Quick Check:
Use --advertise-addr with IP for multi-interface nodes [OK]
Hint: Use IP with --advertise-addr, not interface name [OK]
Common Mistakes:
Using --listen-addr instead of --advertise-addr
Passing interface name instead of IP
Using unsupported flags like --interface
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.