An engineering team has introduced short-lived processes in a new deployment, but some failed tasks have left behind unused cloud items. Which approach helps ensure these items are properly removed once processing finishes?
Reuse the same secret for multiple short-lived tasks to minimize authentication overhead
Rely on manual scripts to clear out failed processes and associated cloud items
Use an automated pipeline that handles both creation and removal of short-lived items
Allow the short-lived tasks to run for a longer period in order to collect more logs
Automating the lifecycle of short-lived items through a pipeline ensures that any unused elements left by failed tasks are removed. Manual or delayed cleanup can lead to lingering items, while reusing the same credentials or extending the process duration can create unnecessary risks and complexity. Managing the lifecycle programmatically keeps the environment clean and helps minimize potential attack surfaces. Storing credentials in environment variables without an automated cleanup process does not address the root issue of leftovers.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why is automation preferred over manual scripts for managing cloud resources?
Open an interactive chat with Bash
What is the risk of reusing secrets for multiple short-lived tasks?
Open an interactive chat with Bash
How does automating the lifecycle of short-lived items minimize attack surfaces?