A security specialist needs a process that runs a script each day to identify missing updates on newly provisioned servers. The script is stored in a version control system for quick updates, and the specialist wants a method that offers minimal manual steps. Which technique meets these requirements?
Run the scanning script manually during periodic patch maintenance windows
Redeploy the environment daily using containers that bundle the scanning script with an image
Configure a mechanism that activates the scanning script each time a user logs in
Implement a job scheduling process that loads the scanning script from its repository each day and runs it on production servers
Using a job scheduling process that retrieves the script each day provides a repeatable cycle with little manual intervention. The script is accessed from its repository and runs consistently to check for missing updates. Triggering scans based on user logins may not cover periods of inactivity. Manually running it as part of scheduled maintenance introduces additional manual work. Redeploying the environment daily creates unnecessary overhead compared to a simple scheduled job.
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.
What is a job scheduling process?
Open an interactive chat with Bash
What is a version control system, and why is it important for scripts?
Open an interactive chat with Bash
Why is triggering scans on user login or manual execution less effective?