A user has written a playbook that calls three other playbooks, one after the other. The user notices that the second playbook starts executing before the first one completes. What is the cause of this behavior?
Hmm, I'm pretty sure the answer is D. The join configuration on the second playbook is likely not set up correctly to wait for the first one to complete.
Ellen
10 days agoBuddy
14 days agoMozelle
15 days agoKayleigh
20 days ago