220-1102 Practice Question: During a software deployment, a technician must…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  "The update fixes a vulnerability that could let attackers steal company data. A reboot is required to apply it. The risk of a breach outweighs the short downtime."

  Why this is correct

  This response effectively communicates the critical nature of the update by explaining the direct business impact: preventing data theft due to a vulnerability. It clearly states the technical requirement (reboot) and provides a strong justification by weighing the risk of a security breach against the short operational downtime. This approach demonstrates a technician's ability to translate technical issues into understandable business terms, fostering informed decision-making and cooperation from non-technical stakeholders.

• ✗

  "Just schedule the reboot for after hours and it won't affect productivity."

  Why it's wrong here

  While scheduling reboots after hours is often a best practice to minimize disruption, this response fails to convey the critical nature or urgency of the update. It does not explain *why* the update is necessary or the potential severe consequences of delaying it, such as a security breach. This approach lacks transparency and does not empower the manager to understand the importance of the task, potentially leading to a lack of prioritization or understanding of the associated risks.

• ✗

  "It's IT policy. We have to do this. Please inform your team."

  Why it's wrong here

  This response is dismissive and provides no technical or business context for the required action. Simply citing "IT policy" without explaining the underlying reason (e.g., security, compliance, system stability) can lead to resentment and a lack of cooperation from other departments. It fails to educate the manager about the importance of the update, treating them as merely an order-taker rather than a partner in maintaining system integrity and security.

• ✗

  "The update is mandatory, but you can delay it for a week if needed."

  Why it's wrong here

  Offering to delay a "mandatory" update, especially one implied to be critical (as per the question context of a security vulnerability), demonstrates poor judgment and a lack of understanding of risk management. Delaying security patches can leave systems vulnerable to exploitation for an extended period, significantly increasing the likelihood of a data breach or system compromise. This approach prioritizes convenience over critical security posture, which is unprofessional and potentially catastrophic for the organization.

Go deeper

Related to this question