Slack-Con-201 Salesforce Certified Slack Consultant Exam Topics and Questions

This topic puts you in the project lead role from first contact through go-live. The work is operational: scheduling, cleanup, client coordination, and managing the migration itself. Most candidates underestimate the pre-migration phase, where poor planning costs hours during cutover.

– Delivery frameworks and responsibilities

Slack delivery follows a defined engagement model, and you need to know who owns what at each stage. The consultant, the Slack team, and the client each carry specific responsibilities, and confusion over handoffs is where projects stall. Best practices cover scoping, timeline management, and how to structure the engagement so that dependencies are visible early. You will be asked to identify which party handles a given task or decision point, and the wrong answer usually reflects a misunderstanding of where Slack's internal support ends and partner accountability begins. Pay attention to escalation paths and when to involve Slack directly versus resolving an issue within the partner-client relationship.

– Migration planning and execution

The migration process has a clear sequence: user cleanup, scheduling, communication, cutover, and post-migration validation. Pre-migration activities are tested heavily because they determine whether the migration runs smoothly or generates support tickets for weeks afterward. User cleanup means deactivating stale accounts, reconciling email addresses, and ensuring the source data is accurate before you move it. Communication plans cover timing, frequency, and which stakeholders receive which messages. During the migration itself, you monitor status, triage issues in real time, and coordinate with both the client and Slack support when blocks occur. Questions will describe a scenario mid-migration and ask what action to take next, testing your ability to prioritize and escalate correctly.

How Delivery and Migration is tested

At seventeen percent, this topic appears in roughly one question out of every six. Items present a project scenario and ask you to choose the correct next step, identify the responsible party, or diagnose why a migration has stalled. The scenarios are specific: a client has duplicate users, a cutover window is too short, or a communication plan omits a key stakeholder group. Wrong answers often look plausible because they describe good practice in general but miss the procedural detail that matters in the scenario. Candidates lose marks by confusing pre-migration tasks with post-migration ones, by assigning a responsibility to the wrong party, or by choosing an action that skips a required step. Read the scenario carefully to identify which phase of the engagement you are in, then match your answer to the correct procedure for that phase.

Discovery sets the direction for everything that follows. You are gathering facts about the client's current state, their goals, and their constraints. The topic tests your ability to ask the right questions, synthesize what you learn, and document a vision statement and success metrics that the client will actually use.

– Research and questioning technique

Before the first conversation, you research the client's organization: industry, size, structure, and any public information about how they work. This background shapes the questions you ask. During discovery calls, you probe existing Slack experience, what is working, what is not, and what the client hopes to achieve. The quality of your questions determines the quality of the engagement. Thoughtful questions uncover unstated assumptions, surface political constraints, and reveal whether the client's goals are realistic. You also ask about security posture and policy requirements, because these constrain every downstream decision. The exam tests whether you can distinguish a good discovery question from one that is too broad, too leading, or focused on the wrong layer of the problem.

– Vision and success metrics

Discovery outputs must be concrete. The vision statement captures what success looks like in the client's own terms, and success metrics define how you will measure progress. Weak vision statements are vague or aspirational without being actionable. Weak metrics are either unmeasurable or disconnected from the client's actual goals. The exam presents scenarios where you must choose the most appropriate metric or identify a vision statement that is too abstract to guide decisions. Candidates lose marks by selecting metrics that sound impressive but cannot be tracked with the data the client has, or by confusing a project goal with a business outcome.

How Discovery is tested

At ten percent, this topic appears roughly once in every ten questions. Items describe a client context and ask which discovery question to ask next, which metric best reflects a stated goal, or why a vision statement is inadequate. The scenarios test your judgment: two questions might both be reasonable, but one is more targeted or more likely to uncover a hidden constraint. Wrong answers include questions that assume facts not in evidence, metrics that require data the client does not collect, or vision statements that duplicate the client's language without adding clarity. Candidates also lose marks by skipping the research phase and jumping straight into solution mode. The correct answer reflects a disciplined approach: gather context, ask specific questions, and document outputs that guide decisions rather than decorate slides.

Grid design determines how workspaces are structured and who has access to what. The decisions you make here affect security, collaboration, and administration for the life of the deployment. This topic tests your ability to translate discovery findings into a grid structure that fits the client's organizational model and constraints.

– Design principles and options

Grid design best practices balance simplicity against organizational boundaries. A single workspace is easier to manage, but some clients need separation by geography, business unit, or regulatory requirement. You need to understand the trade-offs: more workspaces mean more administrative overhead, but fewer workspaces can create permission or compliance problems. Discovery outputs drive the decision. If the client has strict data residency rules or business units that operate independently, a multi-workspace grid may be necessary. If collaboration across the organization is the priority and no hard boundaries exist, a single workspace is usually the better choice. The exam tests whether you can map a client's structure and constraints to a feasible grid design, and whether you can explain the implications of each option.

– Articulation and sign-off

Once you have designed options, you must present them in terms the client understands. That means explaining not just the structure but the consequences: how users will experience the grid, how admins will manage it, and what cannot be changed easily later. Clients often focus on the wrong details or misunderstand what a workspace boundary means in practice. Your job is to clarify the decision without overcomplicating it. Final sign-off requires agreement from stakeholders who may have competing priorities, so you need to facilitate that conversation and document the decision. The exam presents scenarios where a client requests a grid structure that conflicts with their stated goals or constraints, and you must identify the problem and recommend an alternative.

How Grid Design is tested

At fifteen percent, this topic appears in roughly three questions out of every twenty. Items describe a client's organizational structure, regulatory requirements, or collaboration goals, then ask which grid design is most appropriate or why a proposed design will not work. The scenarios test your ability to weigh trade-offs: a single workspace may simplify administration but fail a compliance requirement, or a multi-workspace grid may satisfy security but fragment collaboration. Wrong answers often look reasonable in isolation but ignore a stated constraint or misread the client's priority. Candidates lose marks by choosing the most complex option when a simpler one would work, or by recommending a design that solves a problem the client does not have. Read the scenario for the constraints that matter, then match your answer to the design that satisfies them without introducing unnecessary complexity.

This is the heaviest topic on the exam, covering the full range of administrative configuration decisions. You need to know who can change which settings, how to configure identity management and security controls, and how to guide clients through the choices that will govern their Slack environment for years.

– Administrative roles and permissions

Slack has multiple admin roles, each with a defined scope of permissions. Org Owners control organization-wide settings, Workspace Owners manage individual workspaces, and Workspace Admins have a narrower set of permissions within a workspace. You need to know which role can change which setting, because assigning the wrong role creates either a security gap or a bottleneck. The analytics dashboard is available to Org and Workspace Owners, and enabling stakeholders to use it requires both access and training. Settings alignment means getting org and workspace stakeholders to agree on configuration choices before they are applied, which is harder than it sounds when business units have different risk appetites or compliance requirements.

– Identity, security, and compliance

Identity management settings control how users authenticate and provision. You will guide clients through single sign-on configuration, SCIM provisioning, and session duration policies. Security settings include data retention, two-factor authentication enforcement, and controls over who can share files or create external links. Compliance capabilities cover eDiscovery, legal hold, and audit logs. The exam tests your understanding of what each setting does and when to enable it. Clients often ask for the most restrictive settings without understanding the usability cost, or they leave controls disabled because they do not realize the risk. Your job is to recommend launch configuration that balances security and user experience, and to explain the trade-offs clearly.

– Channel, Connect, and app settings

Channel management settings determine who can create channels, whether channels default to public or private, and how channel naming conventions are enforced. Slack Connect settings control external collaboration: which domains are allowed, whether invitations require approval, and what data can be shared. App approval settings determine whether users can install apps freely or whether every app requires admin review. Each of these areas has a recommended launch configuration, but the right answer depends on the client's risk tolerance and collaboration needs. The exam presents scenarios where a client's stated policy conflicts with the settings they have chosen, or where a setting will block a use case they described as critical.

How Policies and Settings is tested

At twenty-two percent, this is the single largest topic. Expect roughly one question in every five to come from this domain. Items describe a client requirement or constraint and ask which setting to enable, which role is needed to make a change, or why a proposed configuration will not work. The scenarios are specific: a client needs to enforce two-factor authentication for a subset of users, or they want external collaboration with one partner but not others. Wrong answers often reflect a partial understanding of a setting, such as enabling a control that applies organization-wide when the client needed workspace-level granularity. Candidates lose marks by confusing admin roles, by recommending a setting that blocks a stated use case, or by missing the compliance requirement buried in the scenario. Read carefully to identify the constraint that matters, then match your answer to the setting or role that satisfies it without overreach.

Channels are the organizing principle of Slack, and this topic tests your ability to teach clients how to use them effectively. You will explain channel basics, help clients design a naming convention, introduce use cases, and show how workflows automate repetitive tasks within channels.

– Channel fundamentals and naming conventions

Channel basics cover the distinction between public and private channels, when to use each, and how to structure channels around projects, teams, or topics. Best practices emphasize transparency and discoverability: default to public channels unless there is a reason for privacy. Naming conventions matter because they make channels searchable and signal what belongs in each one. A good convention is short, consistent, and reflects how the organization thinks about its work. Clients often resist naming conventions because they seem bureaucratic, but without one the channel list becomes unmanageable within weeks. The exam tests whether you can explain why a naming convention matters and help a client design one that fits their structure.

– Use cases and workflows

Slack use cases demonstrate how channels replace email, meetings, or other tools. Common use cases include project coordination, incident response, and cross-functional collaboration. Introducing use cases means showing the client a concrete example and walking them through how it would work in their environment. Workflows automate routine tasks: onboarding workflows welcome new users and guide them through setup, standup workflows collect status updates without a meeting. The exam tests your ability to match a use case or workflow to a client's stated goal. Candidates lose marks by recommending a workflow that requires integrations the client does not have, or by choosing a use case that does not align with the client's collaboration model.

How Channel Strategy is tested

At ten percent, this topic appears roughly once in every ten questions. Items describe a client's work patterns or goals and ask which channel structure, naming convention, use case, or workflow is most appropriate. The scenarios test your judgment: a client says they want to reduce email, and you must choose the use case that addresses the root cause rather than the symptom. Wrong answers include naming conventions that are too complex to sustain, use cases that duplicate existing tools without adding value, or workflows that automate the wrong part of a process. Candidates also lose marks by recommending a private channel when a public one would serve the goal better, or by missing the organizational context that makes one naming scheme more natural than another. The correct answer reflects an understanding of how the client works, not just what Slack can do.

Governance determines who makes decisions, who handles support requests, and how administrative work gets done once the consultant leaves. This topic tests your ability to help clients identify their governance team, assign roles, and design the processes that will keep Slack running smoothly.

– Governance team and role assignment

The governance team includes Org Owners, Workspace Owners, and any other stakeholders with decision-making authority over Slack. Identifying the team means understanding the client's organizational structure and finding the people who have both the authority and the capacity to manage Slack long-term. Role assignment follows from there: who needs Org Owner permissions, who manages individual workspaces, and who handles day-to-day admin tasks. The exam tests whether you can map a client's structure to the correct set of roles and identify when a proposed assignment creates a gap or a conflict.

– Admin support model and request flows

The admin support model defines how users get help, how requests are triaged, and who approves changes. Common models include a central IT team, distributed admins within business units, or a hybrid approach. You facilitate discussions to help the client choose a model that fits their culture and capacity. Request flows cover how a user asks for a new channel, how an app approval request moves through the system, and how incidents are escalated. The exam presents scenarios where a proposed support model will not scale or where a request flow has a bottleneck, and you must identify the problem.

– Admin processes and workflows in Slack

Once the governance structure is defined, you help the client move their admin processes into Slack itself. That might mean a channel for app approval requests, a workflow for provisioning new users, or a standup for the admin team to coordinate work. The goal is to make the governance model visible and easy to follow. The exam tests your ability to identify which admin processes belong in Slack and how to structure them so they actually get used. Candidates lose marks by recommending a process that is too complex for the client's admin team to sustain, or by missing the opportunity to automate a repetitive task.

How Governance Structure (Owner and Admin Roles) is tested

At eight percent, this topic appears roughly once in every twelve questions. Items describe a client's organizational structure or a proposed governance model and ask which role assignment is correct, which support model fits best, or why a request flow will fail. The scenarios test your ability to match governance design to organizational reality: a centralized model may work for a small company but create bottlenecks in a large one, or a distributed model may make sense culturally but lack accountability. Wrong answers often look reasonable in principle but ignore a constraint in the scenario, such as a client with limited IT capacity or business units that operate independently. Candidates lose marks by assigning a role to someone without the necessary authority, by designing a support model that assumes resources the client does not have, or by recommending a process that is too heavyweight for the volume of requests. The correct answer reflects a practical understanding of how governance works in the client's environment.

Learning and enablement is the second-heaviest topic, and it covers everything from designing a curriculum to facilitating live training to troubleshooting user issues after launch. The work is instructional design and delivery, and the exam tests whether you can tailor learning to the client's context and execute it effectively.

– Experiential learning and curriculum design

Slack's learning approach is experiential: users learn by doing, in an environment that mirrors their real work. The overview explains this philosophy and sets expectations for what training will look like. Curriculum design means choosing which topics to cover, in which order, and at what depth. Admin curriculum differs from user curriculum because admins need configuration knowledge and troubleshooting skills, while users need to understand channels, search, and collaboration patterns. You create a learning plan that sequences the curriculum and allocates time for practice. The exam tests whether you can identify which topics belong in an admin curriculum versus a user curriculum, and whether a proposed learning plan is realistic given the client's constraints.

– Materials, environment, and facilitation

Learning materials support the curriculum: guides, job aids, or recorded demos. You create materials tailored to the client's use cases and vocabulary, not generic Slack documentation. The experiential learning environment is a workspace or set of channels where learners can practice without affecting production. Preparing that environment means setting up sample channels, loading realistic data, and ensuring learners have the permissions they need to try things. Facilitation is live delivery: you guide learners through exercises, answer questions, and adjust pacing based on how the group is progressing. The exam tests your ability to prepare an environment that supports the learning goals and to facilitate in a way that keeps learners engaged.

– Troubleshooting and rollout communication

Common Slack issues include login problems, notification overload, difficulty finding information, and confusion over when to use channels versus direct messages. You need to recognize these issues and know how to resolve them or guide users to the right resource. Rollout communication is the plan for announcing Slack, explaining why it matters, and driving adoption. The plan covers timing, audience segmentation, and message content. You enable the client to execute the plan, which means giving them templates, coaching them on tone, and helping them anticipate questions. The exam tests whether you can match a troubleshooting action to a described issue and whether a proposed communication plan will reach the right audiences with the right message.

How Learning and Enablement is tested

At eighteen percent, this topic appears in nearly one question out of every five. Items describe a client's learning need, a user issue, or a rollout scenario and ask which curriculum, material, troubleshooting step, or communication approach is correct. The scenarios test your ability to tailor learning to context: an admin curriculum for a technical team looks different from one for a non-technical team, and a rollout plan for a regulated industry needs more detail than one for a startup. Wrong answers include curriculum that is too generic, materials that assume knowledge the users do not have, troubleshooting steps that address the symptom but not the cause, or communication plans that miss a key stakeholder group. Candidates lose marks by choosing a learning format that does not fit the client's culture, by preparing an environment that lacks the features learners need to practice, or by recommending a communication plan that front-loads too much information. The correct answer reflects a practical understanding of how adults learn and how organizations adopt new tools.