A SaaS job must snapshot a data volume and only then run a cleanup script, every time an operator starts the job. A laptop cron that calls both steps with stored access keys was proposed. How should the steps run?
Select an answer to reveal the explanation.
Short Explanation
You do not ice a cake because a phone alarm said the pan might be ready. The snapshot and the script belong in one Automation runbook so the script starts only after the snapshot, with no keys living on a laptop. The trap is chaining a production change from a personal cron.
Full Explanation
One Automation runbook lists the work in order: create the snapshot, proceed only when that snapshot has succeeded, and then run the cleanup script under the automation role. A single execution record shows that the script did not start early. Two separate commands depend on a person noticing that the snapshot finished, so the script can run too soon or not at all. A laptop cron stores long-lived access keys, sits outside the account's change record, and does not run when the laptop is off. A dashboard widget graphs metrics and logs and does not create a snapshot or invoke the script. The runbook should stop the chain when the snapshot fails, rather than cleaning up against a snapshot that never completed. Run the document once outside production traffic and confirm the execution shows the snapshot step succeed before the script step starts. Give the automation role permission to create the snapshot and to run the script, and keep the script step from starting when the snapshot step reports failure.