Moving sales channels into the Global workspace and making default channels private would:
* Create confusion and friction in adoption.
* Reduce transparency and cross-functional collaboration.
Slack documentation highlights:
"Workspaces should be structured to align naturally with how teams operate. Making core channels private may limit discoverability and collaboration, which contradicts Slack's goals for connection and transparency." Options B, C, and D promote transparency and collaboration, which is the intended use of Slack across cross- functional teams.
(Reference: Slack Administration Study Guide - Change Management and Slack Adoption Strategies)
-

Slack recommends:
"Channel names should follow consistent naming conventions and use hyphens between words, e.g., help- finance for a help-related finance channel." Option A incorrectly reverses prefix order. Option B uses incorrect formatting. Option D misuses the prefix format as well.
(Reference: Slack Administration Study Guide - Channel Naming Conventions)
-

According to Slack's best practices:
"Claim your domains as soon as possible. This process is not retroactive - workspaces created before claiming domains will continue to exist independently unless manually migrated." Thus, prompt domain claiming ensures better control and prevents users from unintentionally creating ungoverned workspaces.
(Reference: Slack Administration Study Guide - Domain Management in Enterprise Grid)
-

User groups provide two major benefits according to Slack official documentation:
"User groups allow you to quickly notify an entire group of people with an @mention (e.g., @designers,
@managers)."
"They can also be configured so that new users assigned to the group are automatically added to default channels, streamlining onboarding." They do not control channel management permissions (B) or app integrations (E), nor do they affect workspace analytics permissions (C).
(Reference: Slack Administration Study Guide - Managing User Groups)
-