Standard, Normal, and Emergency Changes for A+
Short answer
- Standard: low-risk, pre-approved, routine. Proceed per checklist. - Normal: planned, goes through normal review and approval. - Emergency: urgent, expedited approval or verbal approval, followed by post-facto documentation and review. Technicians must identify the type and apply the correct process: e.g., do not apply emergency handling to routine maintenance.
Why it appears on the exam
- Classify short scenarios into one of the three change types. - Identify the correct next step when presented with a 'standard' change request.
Key concepts
Concept 1
Required terms
standard change: A pre-authorized, low-risk, repeatable change with known procedures that does not require individual approval each time. normal change: A planned change that requires submission, review, and approval through normal change-control processes. emergency change: An expedited change performed to address an immediate critical issue, often following an emergency approval path and subject to later review.
Example
Standard: weekly antivirus signature update applied via automated job.
Concept 2
How Standard, Normal, and Emergency Changes works
- Standard: low-risk, pre-approved, routine. Proceed per checklist. - Normal: planned, goes through normal review and approval. - Emergency: urgent, expedited approval or verbal approval, followed by post-facto documentation and review. Technicians must identify the type and apply the correct process: e.g., do not apply emergency handling to routine maintenance.
Example
Normal: scheduled OS version upgrade requiring approvals and maintenance window.
Concept 3
Common confusion
Learners mix 'normal' with 'low risk'. Emphasize that 'normal' means 'follows the normal approval path', not a risk rating.
Example
Emergency: immediate kernel patch to stop an ongoing attack.
Concept 4
Core 2 (220-1202) question cues
Classify short scenarios into one of the three change types; Identify the correct next step when presented with a 'standard' change request.
Example
Standard: weekly antivirus signature update applied via automated job.
Sample questions
Select an answer to reveal the explanation. For tracked practice and weak-area review, use the Cultiv8 app.
Q1.A technician is troubleshooting this situation: Standard: weekly antivirus signature update applied via automated job. What should they identify?
Q2.A support ticket includes this clue: Normal: scheduled OS version upgrade requiring approvals and maintenance window. Which concept is being tested?
Q3.An A+ support scenario describes this situation: Emergency: immediate kernel patch to stop an ongoing attack. Which answer fits best?
Practice this lesson in Cultiv8
The app adds tracked practice, targeted remediation, saved session history, and future readiness scoring.
Continue in Cultiv8