Operational ProceduresQuestion 86 of 100
In change management, what is the purpose of documenting the 'scope' of a proposed change?
a.To define exactly what will and will not be affected
b.To increase the clock speed
c.To disable the firewall
d.To brighten the display
Explanation
Defining scope clarifies which systems, users, and processes the change affects and which it does not, guiding testing and communication. It has nothing to do with clock speed, firewalls, or display brightness.
Practice all 100 questions free — no signup required.
Related questions on this topic
- When lifting a heavy piece of equipment such as a large UPS or printer, which technique reduces the risk of injury?
- Which document is typically required before disposing of batteries, toner cartridges, or other chemicals to ensure proper handling?
- Which regulated data type requires special handling under privacy rules and should never be exposed carelessly during support work?
- Which environmental control helps protect data-center equipment from damage caused by static electricity and overheating?
- What is a key reason to use a change board or approval step rather than letting any technician change production systems freely?
- Which basic scripting construct repeats a block of instructions until a condition is met, and is fundamental to automation?
Last reviewed: · editorial process
PrepPass Editorial Team · Verified against CompTIA A+ Core 2 (220-1102) · How we review