A systems administrator is creating a new shared directory.

The correct answer is B. chmod g+s /shared because setting the setgid (set group ID) bit on a directory ensures that all files and subdirectories created within it inherit the group ownership of the parent directory. This is essential in shared environments where multiple users from the same group need consistent access to files.

When the g+s permission is applied to a directory, any new files created inside that directory automatically belong to the same group as the directory itself, rather than the primary group of the user who created the file. This behavior is critical for collaboration, as it prevents permission conflicts and ensures that all group members can access and modify shared files without needing manual group changes.

Option A (chmod g+w /shared) is partially helpful but insufficient. While it grants write permission to the group, it does not ensure that newly created files will inherit the correct group ownership. Option C is a duplicate of A and also incorrect for the same reason. Option D (chmod g+x /shared) allows group members to traverse the directory but does not provide write access or ensure proper group inheritance.

In Linux+, managing shared directories is an important aspect of system security and user collaboration. The combination of setgid (g+s) and proper group permissions (such as g+rwx) ensures a controlled and functional shared environment. Without setting the setgid bit, users may create files with different group ownerships, leading to access issues and administrative overhead. Therefore, chmod g+s /shared is the correct and most effective solution for maintaining consistent group collaboration.