Adding comments to GPOs is considered a best practice to ensure future administrators understand why it was created, what its purpose is and what its settings are.

Adding comments to GPOs is considered a best practice to ensure future administrators understand why it was created, what its purpose is and what its settings are.

• A. TRUE
• B. FALSE
• C. Not applicable
• D. Unknown

Answer: (A)

Documenting GPOs with descriptive comments helps future administrators understand why the policy was created, what it’s meant to accomplish, and why its specific settings were chosen. This clarity supports maintainability, faster troubleshooting, and better change control, because someone reviewing the GPO later can quickly grasp its intent, scope, and any dependencies. In practice, you add a description or notes to the GPO’s metadata in the management console, covering purpose, target scope, and any special considerations. Without context, future admins may guess or misinterpret the GPO, increasing the risk of unintended changes, so adding comments is widely regarded as best practice.

Documenting GPOs with descriptive comments helps future administrators understand why the policy was created, what it’s meant to accomplish, and why its specific settings were chosen. This clarity supports maintainability, faster troubleshooting, and better change control, because someone reviewing the GPO later can quickly grasp its intent, scope, and any dependencies. In practice, you add a description or notes to the GPO’s metadata in the management console, covering purpose, target scope, and any special considerations. Without context, future admins may guess or misinterpret the GPO, increasing the risk of unintended changes, so adding comments is widely regarded as best practice.