N10-009 Question 192
Single answerAsset inventory: Hardware, Software, Licensing, Warranty supportA network administrator is preparing for a scheduled replacement of several aging access switches at a branch office. During planning, the administrator discovers that one switch is still under manufacturer warranty, two switches are running different firmware versions than what is documented, and a management server is using more monitoring software installations than were originally purchased. The administrator needs to reduce project risk, avoid compliance issues, and ensure accurate support escalation if problems occur during the change window. Which action should the administrator take FIRST?
- A
Update the asset inventory to verify hardware serial numbers, installed software/firmware versions, license counts, and warranty/support status before the replacement
- B
Begin replacing the switches immediately and correct the inventory records after the maintenance window to avoid delays
- C
Open a warranty replacement case for every switch scheduled for removal so spare hardware is available if needed
- D
Standardize firmware on all switches during the maintenance window without checking software licensing or support entitlements
Show answer and explanation
Correct answer: A
Explanation
In real-world network operations, accurate asset inventory is a prerequisite for safe change management. Before replacing infrastructure, administrators should validate hardware details such as model and serial number, software and firmware versions, licensing status, and warranty/support entitlement. These records support several operational needs: confirming what equipment is actually deployed, identifying unsupported or undocumented software versions, ensuring software use does not exceed purchased licenses, and enabling fast vendor escalation using correct serial and contract information. This aligns with standard IT asset management and configuration management best practices, where current inventory data is used to support maintenance planning, lifecycle decisions, compliance checks, and vendor support interactions. In this scenario, updating and validating the asset inventory first is the best action because it addresses all four focus areas: hardware, software, licensing, and warranty support.
- A. Correct.
This is correct because a complete asset inventory review is the foundational step before making infrastructure changes. Verifying serial numbers confirms the exact hardware in scope, documenting installed firmware/software versions exposes configuration drift, checking license counts addresses potential compliance problems, and confirming warranty/support status ensures the administrator knows what vendor assistance or replacement options are available during the change. This directly reduces operational and support risk.
- B. Incorrect.
This is incorrect because proceeding with replacement before validating the inventory increases the chance of using incorrect hardware records, missing active warranties, overlooking unsupported firmware, or failing to identify software licensing overuse. A common mistake is treating documentation as an after-action task, but for change planning and incident escalation, accurate records are needed beforehand.
- C. Incorrect.
This is incorrect because warranty cases should be opened only when there is a legitimate failure or support need, according to vendor support processes. Scheduling replacement of aging equipment does not justify opening warranty claims for all devices. This option reflects a misunderstanding of warranty support as a proactive stock-refresh mechanism rather than a contractual repair/replacement service for covered issues.
- D. Incorrect.
This is incorrect because firmware standardization may be a valid later task, but doing it first and ignoring license and support validation does not address the full risk described in the scenario. It also assumes the administrator has confirmed hardware eligibility, support coverage, and approved software versions. The misconception here is focusing narrowly on technical consistency while neglecting inventory accuracy, compliance, and support readiness.