A Linux administrator provisioned a new web server with custom administrative permissions for certain users. The administrator receives a report that user1 is unable to restart the Apache web…

Adding user1 to the wheel group typically grants broad sudo access, which often goes against the least privilege security model if user1 only needs to manage Apache.

Adding NOPASSWD: would remove the password prompt for user1 when using sudo, but it does not grant the underlying permission to manage the Apache service if it's not already defined.

Uncommenting the wheel line in custom.conf would enable broad sudo access for members of the wheel group, which contradicts the least privilege principle if user1 only needs to manage Apache.

If `custom.conf` is a `sudoers` file for custom administrative permissions, listing `Webadmin` as a group and adding `user1` to it, along with a `sudo` rule for restarting Apache, grants the specific privilege without broad root access. This aligns with the least privilege principle by granting only the required permission.