NS0-157 · Question #120
Which statement is true about expanding an aggregate from 32-bit to 64-bit in place?
The correct answer is C. The expansion is triggered by adding disks to exceed 16 TB. A 32-bit aggregate is converted to 64-bit in place automatically when adding disks causes the usable capacity to exceed 16 TB, requiring no manual conversion command.
Question
Which statement is true about expanding an aggregate from 32-bit to 64-bit in place?
Options
- AAll aggregates are automatically converted from 32-bit to 64-bit with the Data ONTAP 8.1
- BThe expansion is triggered by an aggr convert command.
- CThe expansion is triggered by adding disks to exceed 16 TB.
- DThe 32-bit aggregates are degraded and must be Volume SnapMirrored to a new 64-bit
How the community answered
(47 responses)- A2% (1)
- B4% (2)
- C85% (40)
- D9% (4)
Why each option
A 32-bit aggregate is converted to 64-bit in place automatically when adding disks causes the usable capacity to exceed 16 TB, requiring no manual conversion command.
Upgrading to Data ONTAP 8.1 does not automatically convert existing 32-bit aggregates; conversion only occurs when the capacity threshold is crossed by adding disks.
There is no 'aggr convert' command in Data ONTAP; the in-place conversion is capacity-driven and automatic, not initiated by a manual command.
When disks are added to a 32-bit aggregate and the total usable capacity crosses the 16 TB threshold, Data ONTAP automatically triggers an in-place conversion to 64-bit format. This conversion is transparent to clients and does not require a separate CLI command, allowing the aggregate to grow beyond the hard 16 TB limit of the 32-bit format.
Volume SnapMirror to a new 64-bit aggregate is a data migration method, not an in-place expansion, and does not describe the automatic in-place conversion process.
Concept tested: In-place 32-bit to 64-bit aggregate conversion trigger condition
Source: https://docs.netapp.com/us-en/ontap/disks-aggregates/convert-32-bit-ontap-98-later-task.html
Topics
Community Discussion
No community discussion yet for this question.