Slack-Con-201 Exam Questions & Answers

The correct answers are C and E. An AMA channel needs two things at the same time: participation and structure. A workflow for question submission gives employees an easy, consistent way to participate without flooding the channel with scattered posts. It can capture questions in a standard format and route them to moderators for review, sequencing, or grouping. Restricting posting permissions to session moderators keeps the channel clean and prevents uncontrolled side discussions, duplicate questions, or fragmented threads. Together, these practices preserve engagement while maintaining order. Option A can be useful for lightweight feedback, but emoji reactions do not provide a structured way to ask questions. Option B is wrong because deleting answered questions destroys useful context and reduces transparency. Option D encourages participation but sacrifices organization; open posting permissions are exactly what can make a large AMA channel noisy and hard to follow. The strongest design separates question intake from moderated publishing.

Reference topic: Learning and Enablement --- AMA channel design, Workflow Builder, moderated engagement, posting permissions, and organized launch communications.

==========

The correct access level is By Request. The legal workspace should be discoverable to all members of the Enterprise organization, but access should require approval because the workspace contains confidential legal conversations. ''By Request'' fits that exact requirement: members can see that the workspace exists and request to join, while the appropriate workspace owners or admins can approve only legal team members or authorized users. Option A, Open, is too permissive because any eligible member could join without approval. Option C, Hidden, is too restrictive because the client specifically wants all org members to see that the workspace exists. Option D, Invite Only, allows controlled membership but removes the self-service request mechanism and is not as aligned with the requirement that the workspace be visible. The consultant should always map workspace access level to sensitivity and discoverability. Confidential-but-visible workspaces generally fit the By Request model.

Reference topic: Grid Design --- workspace access levels, confidential workspace design, discoverability, approval-based access, and Enterprise Grid workspace governance.

==========

The correct answer is an automated welcome bot message that prompts the new employee to complete an introduction workflow, which is then automatically shared with the team. The client wants a warm onboarding experience where employees share fun and useful information with coworkers, and the key word is automated. Option A satisfies both requirements: it initiates the experience through Slack automatically and uses a workflow to collect and distribute the introduction consistently. Option B relies on managers to prompt the employee, which introduces inconsistency and is not fully automated. Option C depends on a manual manager message and asks the employee to post in a company-wide welcome channel, which may be too broad and less targeted than sharing with the employee's team. Option D provides a private welcome but fails to include the employee-sharing component the client requested. Workflow-based onboarding is stronger because it standardizes the experience, reduces manager workload, and makes the new hire's introduction visible in the right collaboration context.

Reference topic: Learning and Enablement --- onboarding workflows, automated welcome experiences, Workflow Builder use cases, new-hire enablement, and launch adoption.

The best answer is to host three sessions throughout the launch week to accommodate the company's geographic spread. A live enablement plan must match the employee population, launch timing, and working time zones. Since the customer has users in San Francisco, New York, and London, one fixed session time creates an avoidable accessibility problem. Option C supports a tailored training experience because each regional audience can attend during reasonable working hours and ask questions relevant to their local usage patterns. Option A creates an uneven experience by training only one group before launch and delaying the others. Option B repeats the same session weekly but does not address regional time-zone needs. Option D trains before users can experience the live Slack environment, which can reduce relevance and retention. The Slack Consultant exam outline includes Learning and Enablement as a core domain, and the official prep trailmix separates enablement as a dedicated consultant workshop area.

Reference topic: Learning and Enablement --- launch training, global user readiness, live training design, and adoption planning.

==========

The correct recommendation is to enable domain claiming. In an Enterprise Grid environment, domain claiming is the administrative control that links company-owned email domains to the Enterprise organization and prevents employees from creating unsanctioned Slack workspaces with those domains. This is a policy and governance control, not a communication-only problem. Option A may help route future workspace requests, but it does not prevent independent workspace creation. Option B is weak because user communication is advisory, not enforceable. Option C is not the correct Slack control and would create unnecessary user-management risk. Domain claiming is specifically designed to make the Enterprise org's approved workspaces easier to find, allow eligible users to join the org, and prevent unmanaged workspace sprawl outside the organization. Slack's official documentation explicitly lists preventing unsanctioned workspace creation as a reason to claim domains for an Enterprise organization.

Reference topic: Policies and Settings --- Enterprise Grid domain governance, workspace creation control, and domain claiming.

==========