Which of the following would be used to enforce and schedule critical updates with supervisory approval and include backup plans in case of failure?
Which of the following would be used to enforce and schedule critical updates with supervisory approval and include backup plans in case of failure?
Change management is a structured approach for making changes to an organization's IT infrastructure, designed to minimize the risk of disruptions and ensure changes are implemented in a controlled and effective manner. It involves enforcing and scheduling critical updates, requiring supervisory approval to ensure that the changes are appropriate and safe. Additionally, change management includes having backup plans in case of failure, ensuring that the organization can roll back to a previous state if the update causes issues. This process helps maintain system stability and business continuity.
"Enforce and schedule critical updates" > this is a massive change to an organization, so the organization is forcing the IT team to schedule the change to let everyone know about the change "Supervisory approval" > someone or a group of people has to approve the change before it can be implemented throughout the organization "Include backup plans in case of failure" > if the change fails, then the IT team has backups to restore data. This was all covered in the CompTIA A+.
Business continuity plan is for after an emergency. I would go for E
This is exactly my logic because the business continuity plan is only for an emergency - what to do, whom to contact, how to proceed but it is not for "enforcing and scheduling critical updates" and that's why the answer is E.
You need backups for business continuity so that you can fall-back on the backups in case of emergency.
it says "in case of a failure" that sounds like an emergency to me
Yes? That's right. It is meant to confuse people with knowledge and test on english language usage and how many times you can read the question. The answer is clearly change management. Read the question again. "Back-up in case of failure", that is done when a change management fails. Normally we call it Rollback, but here they misused the backup to trip people. The intent of the certification industry is not to test knowledge but make more money for themselves.
its E, enforce updates with supervisory approval - Change management, Also, there is always a backup/ roll back plan.
It's E: Change Mangement. As it need supervisor approval, it's a either a normal or emergency change. Standard changes are pre-approved. https://wiki.en.it-processmaps.com/index.php/Change_Management "Emergency Changes: Changes that must be implemented immediately, for example to resolve a Major Incident. Normal Changes: All other Changes that are not Standard Changes or Emergency Changes. Normal Changes are often further categorized as Major, Significant or Minor, depending on the level of risk involved. Organizations should define these types of Changes and the required Change Authorities in their Change Policy. For example, Major Changes may require a full review by the CAB (Change Advisory Board), while Significant Changes may be approved by the Change Manager. If a Non-Standard Change is needed, the party requiring the Change will typically submit a Request for Change (RFC) to Change Management. Change Management will then record, analyze and approve (or reject) the Change. Emergency Changes are assessed and approved by the ECAB (Emergency Change Advisory Board), a core group of CAB members that is available on short notice to respond to emergencies. "
- A. Business continuity plan: A plan that outlines how an organization will continue to operate during and after a disaster or other disruptive event. - B. Onboarding and offboarding policies: Procedures that define the steps required to onboard new employees and remove departing employees from an organization. - C. Acceptable use policy: Guidelines that define the acceptable uses of an organization's IT resources by employees and other authorized users. - D. System life cycle: A process that defines the stages that a system goes through from its initial development to its eventual retirement. - E. Change management: A structured approach for making changes to an organization's IT infrastructure, designed to minimize the risk of disruptions and ensure changes are implemented in a controlled and effective manner.
E. Change management would be used to enforce and schedule critical updates with supervisory approval and include backup plans in case of failure.
I saw this in my CompTIA book last night it is Change Management. ps here is a link to a video about change management. https://www.professormesser.com/free-a-plus-training/220-1102/220-1102-video/change-management-220-1102/
Change management details backup plans. Source: ITIL.
The answer is E because change management policies include disaster recovery in case a rollback is needed, I can see why people might say it is A, but it's not talking about a natural disaster causing this critical update to fail.
Answer is correct but reasoning could be different. Change management include back-ups for rollback in case changes fail. Disaster recovery also requires backups. The question does not have to mention natural disaster (disaster recovery is not just about natural disasters) because this is also not mentioning reason for the change. And disaster is not causing a change request to fail but other factors. I consider the whole sentence and argument used in the above comment to be not correct.
Change management can help ensure that your network keeps running in good health. It can also ensure that your documentation reflects the true and current state of the objects it is describing. This is very important for many aspects of your operations, including security responses and troubleshooting operations. Change management documentation often includes the following: ■■ A documented reason for a change ■■ The actual change request ■■ The approval process ■■ The required maintenance window ■■ The change notification process
change management
Updates are always necessary, especially the critical ones for any changing situation. A business continuity plans cover issues involving full failures & not specifically for critical updates.
Poorly worded question but I would tend to go for Change Management here
GPT selects (E) Change management: " Change management is a structured process that organizations use to manage and control changes to their environments, systems, and processes. In this scenario, using change management ensures that critical updates are planned, approved by supervisory personnel, scheduled in a controlled manner, and include backup plans to address potential failures. This approach helps minimize risks associated with updates and changes while maintaining business continuity. Options (A) Business continuity plan focuses on strategies to ensure that essential functions continue during and after a disaster or disruptive event. (B) Onboarding and offboarding policies relate to employee hiring and departure procedures. (C) Acceptable use policy outlines guidelines for using organization resources. (D) System life cycle deals with the phases of a system's existence from inception to retirement. While these options are important in their own contexts, they are not directly related to scheduling and managing critical updates with supervisory approval as described in the scenario."
Sounds like A to me. Business continuity may be defined as "the capability of an organization to continue the delivery of products or services at pre-defined acceptable levels following a disruptive incident". A failure is a pretty disruptive incident
They have it correct. When are talking about backup plans they are talking about backup plans if the change/patch fails. Most places would call this a backout plan but they are calling it a backup plan.
A is my answer