Timing, Affected Systems, and Risk Analysis for A+
Short answer
Key considerations: - Avoid scheduling during business-critical hours unless change must occur then. - Use maintenance windows and respect change-freeze periods (e.g., end-of-quarter financial processing). - Identify all affected systems and the user impact (partial outage, degraded performance, full outage). - Perform a simple risk analysis: list likely failure modes, estimate likelihood and impact, and confirm mitigations (rollback, redundancy, notification).
Why it appears on the exam
- Given a scenario with dependencies, identify which systems must be included in the scope and which maintenance window is appropriate. - Choose the correct mitigation for a medium-impact, medium-likelihood risk.
Key concepts
Concept 1
Required terms
timing: Choosing the appropriate date and time for a change considering business hours, maintenance windows, and change freezes. affected systems: The specific servers, applications, services, or user groups that will experience change-related impact. risk analysis: A brief evaluation of potential negative outcomes, their likelihood, and mitigation steps prior to executing a change.
Example
Schedule backups and patching for 02:00-04:00 in a timezone where business hours are 09:00-17:00 and users are offline.
Concept 2
How Timing, Affected Systems, and Risk Analysis works
Key considerations: - Avoid scheduling during business-critical hours unless change must occur then. - Use maintenance windows and respect change-freeze periods (e.g., end-of-quarter financial processing). - Identify all affected systems and the user impact (partial outage, degraded performance, full outage). - Perform a simple risk analysis: list likely failure modes, estimate likelihood and impact, and confirm mitigations (rollback, redundancy, notification).
Example
Decline a proposed change during fiscal year-end close due to a declared change freeze.
Concept 3
Common confusion
Learners often underestimate indirect impacts (shared storage, authentication services). Teach to check dependencies beyond the immediate target.
Example
Schedule backups and patching for 02:00-04:00 in a timezone where business hours are 09:00-17:00 and users are offline.
Concept 4
Core 2 (220-1202) question cues
Given a scenario with dependencies, identify which systems must be included in the scope and which maintenance window is appropriate; Choose the correct mitigation for a medium-impact, medium-likelihood risk.
Example
Decline a proposed change during fiscal year-end close due to a declared change freeze.
Sample questions
Select an answer to reveal the explanation. For tracked practice and review of what you missed, use the Cultiv8 app.
Q1.A technician is troubleshooting this situation: Schedule backups and patching for 02:00-04:00 in a timezone where business hours are 09:00-17:00 and users are offline. What should they identify?
Q2.A support ticket includes this clue: Decline a proposed change during fiscal year-end close due to a declared change freeze. Which concept is being tested?
Q3.An A+ support scenario describes this situation: A brief evaluation of potential negative outcomes, their likelihood, and mitigation steps prior to executing a change. Which answer fits best?
Practice this lesson in Cultiv8
The app adds guided practice, review of what you missed, and saved progress.
Continue in Cultiv8