Slack-Con-201 Exam Preparation Material | Salesforce Certified Slack Consultant

Explanation:
The correct answer is A. A standard channel naming convention primarily improves organization and clarity for users. In Slack, channels are the structure through which work becomes visible and searchable. Without consistent names, users struggle to understand where work belongs, where to ask questions, and how to find existing channels before creating new ones. Naming conventions such as #help-, #team-, #proj-, #announcements-, or #ext- make the purpose of channels immediately recognizable.
Option B may be a secondary benefit if the naming style reflects company culture, but branding is not the main reason to standardize channel names.
Option C is partially related because better naming may reduce duplicate or unnecessary channels, but it does not technically prevent channel creation.
Option D is incorrect because naming conventions do not show membership; channel member lists and profiles do that. The primary purpose is navigational clarity: users can quickly understand channel purpose, locate relevant work, and follow a predictable collaboration structure.

Explanation:
The correct answer is D. The requirement is to automatically sign users out of desktop and mobile Slack sessions every 30 days. Slack session duration is a security control, so it belongs under org security settings rather than SSO settings. The duration is configured in hours, and 30 days equals 720 hours.
Option A uses the correct security-settings area but expresses the duration as calendar days rather than the tested configuration value.
Option B and Option C are incorrect because they place the control under SSO settings, but the requirement concerns Slack session duration for desktop and mobile instances, not SSO configuration itself. The consultant must translate the business requirement into the correct administrative setting and format: org-level security setting plus 720-hour session duration. This supports the client’s security posture by limiting persistent sessions and requiring periodic reauthentication across Slack clients.
Reference topic: Policies and Settings ― session duration, org security settings, reauthentication controls, Enterprise Grid security posture, and desktop/mobile session governance.

Explanation:
The correct answer is D. The request involves a restricted Enterprise Grid capability: creating multi-workspace channels. Since only Org Admins and Org Owners can perform the action, the support model must route requests to the correct privileged audience. A central private org-wide admin channel is the most efficient structure because it gives the right admins visibility, lets them coordinate ownership, preserves request history, and avoids exposing admin operations in a public channel.
Option A is inefficient and confuses the request type by referring to a Slack Connect channel instead of a multi-workspace channel.
Option B creates visibility but is too open; admin request coordination should not necessarily occur in a public channel.
Option C is poor governance because DMs create hidden backlogs and make it hard for other admins to track status or reassign work. A workflow-backed intake process feeding a private admin coordination channel is scalable, auditable, and aligned with permission-restricted operations.

Explanation:
The correct answer is C. In Enterprise Grid, SSO is managed at the organization level, so exceptions to the SSO requirement must be handled in org settings, not workspace settings. The client needs some members to continue logging in with a username and password, which means those members must be excluded from the SSO requirement. The answer also specifies uploading a CSV list, which is the scalable method for applying exclusions when multiple members are involved.
Option A is incorrect because it uses the workspace settings dashboard and manual entry, which does not align with Enterprise Grid org-level SSO control.
Option B is wrong because workspace admin settings are not the correct place for Enterprise Grid SSO exclusions.
Option D correctly identifies org settings but uses manual addition; the tested recommendation is to upload a CSV list for the excluded users. The important consulting principle is that identity and authentication settings on Enterprise Grid are centralized at the org level.
Reference topic: Policies and Settings ― Enterprise Grid SSO, org-level authentication controls, SSO exclusions, CSV user management, and login policy design.

Explanation:
The correct components are target audience, objective, and delivery method. A rollout communication plan must define who the communication is for, what the communication is intended to accomplish, and how it will be delivered. The target audience matters because executives, admins, champions, managers, and end users need different information at different points in the rollout. The objective clarifies the purpose of the message, such as awareness, action, training registration, policy change, launch readiness, or reinforcement. The delivery method defines how the message reaches the audience, such as Slack announcements, email, live sessions, manager cascades, or help channels.
Option A omits the objective, which is a serious gap because communication without a stated goal becomes generic broadcast messaging.
Option C omits the audience, making the communication impossible to tailor.
Option D omits the delivery method, leaving the plan incomplete. Channel setup recommendations may appear elsewhere in the launch plan, but they are not one of the core components of the communication plan itself.
Reference topic: Learning and Enablement ― rollout communication planning, audience segmentation, communication objectives, delivery methods, and change-management messaging.