Which two components are required for committing data to a WORM volume? (Choose two.)
Which two components are required for committing data to a WORM volume? (Choose two.)
To commit data to a WORM volume, you must license SnapLock and create a SnapLock Aggregate. Licensing SnapLock is essential to enable the feature, and creating a SnapLock Aggregate is necessary because the SnapLock volume inherits the WORM characteristics from the aggregate. This setup ensures that the data written to the volume cannot be altered or deleted, meeting the WORM (Write Once, Read Many) requirements.
A&D When you see workflow snaplock, licence and aggregate come before volume https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.pow-arch-con%2FGUID-1087DB8C-6A72-4FDE-A5C2-444F0A1BFC1F.html
A&D. Above link provided also explains that the volume inherits the snaplock mode from the Snaplock Aggregate.
A and B
A and D The volume inherits the snaplock function from the Snaplock Aggregate
Sorry A and D
This question is strange and ambiguous . From the available choices, SnapLock requirements are, in order, A, D and B. But committing data to a Worm Volume means that all these requirements are already implemented. You can use a command or program to commit files to WORM manually, or use the SnapLock autocommit feature to commit files to WORM automatically. I think either the question or the choices are wrong. https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.pow-arch-con%2FGUID-F5654F20-545F-44A7-B627-181182D53AB3.html
You always need to create SnapLock Aggregate
A and C
Before creating a snaplock volume, you have to create a snaplock aggregate