Executing wafl.default_security_style ntfs will have what effect?

Executing wafl.default_security_style ntfs will have what effect?

• A. It will set the security style of all files to be ntfs.
• B. It will change the security style of all qtrees to be ntfs.
• C. It will change the security style of all existing volumes to be ntfs.
• D. It will set the security style of all newly created volumes to ntfs.

Answer: (D)

Setting wafl.default_security_style ntfs establishes the default security style for volumes you create in the future. Security style determines how permissions are handled (Unix permissions vs. Windows NTFS ACLs). By choosing ntfs, any new volume you create will start with NTFS security semantics. It does not retroactively change existing volumes, files, or qtrees—those would require separate actions if you want to modify them. So the effect is that newly created volumes will be NTFS by default.

Setting wafl.default_security_style ntfs establishes the default security style for volumes you create in the future. Security style determines how permissions are handled (Unix permissions vs. Windows NTFS ACLs). By choosing ntfs, any new volume you create will start with NTFS security semantics. It does not retroactively change existing volumes, files, or qtrees—those would require separate actions if you want to modify them. So the effect is that newly created volumes will be NTFS by default.