Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

CompTIA Exam XK0-005 Topic 4 Question 33 Discussion

Actual exam question for CompTIA's XK0-005 exam
Question #: 33
Topic #: 4
[All XK0-005 Questions]

A Linux administrator has defined a systemd script docker-repository.mount to mount a volume for use by the Docker service. The administrator wants to ensure that the Docker service does not start until the volume is mounted. Which of the following configurations needs to be added to the Docker service definition to best accomplish this task?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Dannette
25 days ago
I'm just picturing the administrator trying to start the Docker service, but it keeps failing because the volume isn't mounted yet. Talk about a mount-uous task!
upvoted 0 times
...
Josue
26 days ago
Wait, should we be using 'Wants' instead of 'Requires'? That way the Docker service will still start even if the mount fails, but it'll try to use the mounted volume if it's available.
upvoted 0 times
Willard
3 days ago
B) ExecStart=/usr/bin/mount -a
upvoted 0 times
...
Malinda
9 days ago
A) After=docker-repository.mount
upvoted 0 times
...
...
Carmelina
28 days ago
D seems like the way to go. The 'RequiresMountsFor' directive tells systemd to wait for the specific mount unit to be active before starting the Docker service.
upvoted 0 times
...
Rasheeda
30 days ago
I'm pretty sure the answer is A. The 'After' directive ensures that the Docker service starts after the mount unit is active.
upvoted 0 times
Keneth
6 days ago
Yes, 'After' directive will make sure the Docker service starts after the volume is mounted.
upvoted 0 times
...
Gayla
10 days ago
I think you're right, option A is the correct one.
upvoted 0 times
...
...
Shalon
1 months ago
Option C makes the most sense to me. The 'Requires' directive ensures that the Docker service won't start until the docker-repository.mount unit is active.
upvoted 0 times
Nguyet
2 days ago
B) ExecStart=/usr/bin/mount -a
upvoted 0 times
...
Lazaro
12 days ago
A) After=docker-repository.mount
upvoted 0 times
...
...
Vernell
2 months ago
I'm not sure, but I think option A) After=docker-repository.mount could also work. It specifies that the Docker service should start after the specified mount unit is active.
upvoted 0 times
...
Goldie
2 months ago
I agree with Laura. Adding Requires=docker-repository.mount to the Docker service definition will make sure that the service waits for the volume to be mounted before starting.
upvoted 0 times
...
Laura
2 months ago
I think the answer is C) Requires=docker-repository.mount because it ensures that the Docker service will only start if the specified volume is mounted.
upvoted 0 times
...
Jesse
2 months ago
I'm not sure, but I think option A) After=docker-repository.mount could also work. It specifies that the Docker service should start after the specified mount unit is active.
upvoted 0 times
...
Bernardine
2 months ago
I agree with Claudio. Adding Requires=docker-repository.mount to the Docker service definition will make sure that the service waits for the volume to be mounted before starting.
upvoted 0 times
...
Claudio
2 months ago
I think the answer is C) Requires=docker-repository.mount because it ensures that the Docker service will only start if the specified volume is mounted.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77