An IT operations team wants to deploy new servers while preserving a consistent, secure baseline. They created a reference build that was patched and validated before deployment. Which measure helps to keep that reference in a trustworthy state for future servers?
Intercept system changes with a scanning tool and skip scheduled updates
Activate strong host-based controls and refrain from re-imaging
Seal the template in read-only storage for future deployments
Refresh the template with new patches and confirm integrity with a hashing mechanism
Refreshing the reference with new patches ensures that newly discovered issues are addressed. Confirming its integrity with a hashing mechanism helps detect unwanted modifications. Other methods, such as relying on antivirus only, avoiding regular re-imaging, or locking the reference in read-only storage, leave the reference open to potential exposure and fail to confirm alterations effectively.
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 hashing mechanism, and why is it important for confirming integrity?
Open an interactive chat with Bash
Why is it important to regularly patch and update a reference template?
Open an interactive chat with Bash
What are the risks of using read-only storage for reference templates?