C1000-038 · Question #38
Which of the following planning considerations is required when ordering the 16U reserved feature?
The correct answer is C. Order a MES for the third of fourth PCle+ I/O drawer. When ordering the 16U reserved feature on IBM Z systems, option C is correct because this feature specifically reserves rack space for future PCIe+ I/O drawer expansion - and a MES (Miscellaneous Equipment Specification) order is the required mechanism to add the third or…
Question
Which of the following planning considerations is required when ordering the 16U reserved feature?
Options
- AOrder the number of I/O cables that will be needed.
- BPlan for the number of rack-mounted disks.
- COrder a MES for the third of fourth PCle+ I/O drawer.
- DPlan for the number of power cords required.
How the community answered
(46 responses)- A9% (4)
- B2% (1)
- C76% (35)
- D13% (6)
Explanation
When ordering the 16U reserved feature on IBM Z systems, option C is correct because this feature specifically reserves rack space for future PCIe+ I/O drawer expansion - and a MES (Miscellaneous Equipment Specification) order is the required mechanism to add the third or fourth PCIe+ I/O drawer later. The 16U reserved feature is essentially a placeholder, and the MES is the formal ordering process that activates that reserved space.
Why the distractors are wrong:
- A (I/O cables) - Cable quantities are a general planning task for any I/O configuration, not a requirement specific to the 16U reserved feature.
- B (rack-mounted disks) - Disk planning is unrelated to the 16U reserved feature, which is about PCIe+ I/O drawer capacity, not storage.
- D (power cords) - Power cord planning applies broadly to all hardware installations, not as a specific requirement triggered by the 16U reserved feature.
Memory tip: Think of the "16U" as a reserved parking spot for a future PCIe+ I/O drawer - the MES is the "ticket" you must order to actually use that spot. No MES = no drawer, even though the space exists.
Topics
Community Discussion
No community discussion yet for this question.