# Free Salesforce Slack Consultant Practice Questions

*Last updated September 2026 · https://www.certifyforce.com/salesforce-slack-consultant-practice-exam/free-questions*

18 free Slack Consultant practice questions from the Certifyforce bank of 300 reviewed questions, spread across the 7 official exam sections in proportion to their weight. Each has the correct answer, an explanation, and the official documentation it was verified against.

## Delivery and Migration (17%)

### Question 1

Ursa Major Solar's migration into its Enterprise organization (Enterprise Grid or Enterprise+ plan) is scheduled for Saturday, and the consultant holds a go/no-go meeting with the client on Wednesday to revisit the migration checklist. Which items should the consultant confirm before giving a go? Choose 2 answers.

- A. SSO is set up on the org, and migrating members' emails match what SSO sends.
- B. Every migrating member has been preprovisioned into the org through SCIM.
- C. The workspace's custom profile fields have been recreated in the org already.
- D. Duplicate accounts are addressed and role conflicts between users are resolved.
- E. Every Slack Connect channel has been converted to an internal channel for now.

**Correct answers:** A. SSO is set up on the org, and migrating members' emails match what SSO sends.; D. Duplicate accounts are addressed and role conflicts between users are resolved.

**Explanation:** Trailhead's go/no-go meeting revisits the migration checklist with special attention to a fully configured grid, SSO set up on the org, user emails matching SSO, duplicates addressed, role conflicts resolved and the migration invitation accepted. Preprovisioning members is discouraged because it lengthens the migration through profile matching. Recreating custom profile fields is not a readiness item and can add conflicts. Slack Connect channels are supported in grid migrations, so converting them is unnecessary.

**Sources:** [Executing Migration: Key Steps and Troubleshooting Tips](https://trailhead.salesforce.com/content/learn/modules/migration-to-slack-enterprise/execute-migration)

### Question 2

Ursa Major Solar's Workspace Admin is alarmed that the Duplicated and Illegal Usernames section of the premigration report lists dozens of entries. On review, each entry is two different people, with different email addresses, who happen to use the same username. What should the consultant tell the admin?

- A. Each pair will be merged into one account at migration, so one person in every pair must change email first.
- B. These users must be deactivated before migration, then reinvited to the organization once it is complete.
- C. No action is needed; they are false positives, and one handle in each pair gets extra digits appended.
- D. Slack will cancel the scheduled migration unless every flagged username is unique across the whole org.

**Correct answer:** C. No action is needed; they are false positives, and one handle in each pair gets extra digits appended.

**Explanation:** Two different users with different emails sharing a username is a false positive: there is no duplication risk, and one username is appended with extra digits at migration so the handles stay unique. Accounts merge on matching email, not on matching username, so these pairs are not merged and nobody needs to change email. Deactivating and reinviting users is unnecessary and would disrupt them. A shared username does not cancel a migration; the true-positive case to act on is the same person using different emails.

**Sources:** [Effective Premigration Cleanup for Smooth Migrations](https://trailhead.salesforce.com/content/learn/modules/migration-to-slack-enterprise/perform-pre-migration-clean-up-activities)

### Question 3

Northern Trail Outfitters just signed for the Enterprise+ plan and will migrate three existing workspaces into the new organization. The client wants the org to start with settings close to those of its best-governed workspace. What should the consultant recommend?

- A. Migrate the workspace with the preferred settings first, because only one migrated workspace's settings can be copied to the org.
- B. Migrate all three workspaces on the same day so Slack can blend their settings into one combined org configuration automatically.
- C. Set up the org as brand new with default settings, because migrating workspaces never copies any settings into the organization.
- D. Migrate the largest workspace first, because Slack always copies the settings of the workspace with the most members into the org.

**Correct answer:** A. Migrate the workspace with the preferred settings first, because only one migrated workspace's settings can be copied to the org.

**Explanation:** When setting up a new Enterprise organization, migrating an existing workspace can apply a close copy of its settings to the org, but only one migrated workspace's settings can be copied, so the guidance is to migrate the workspace with the preferred settings first and then migrate the others. Slack does not blend settings from several workspaces. Starting from scratch is an option, but it does not apply a workspace's settings, so it fails the client's goal. Slack does not choose settings based on workspace size.

**Sources:** [Enterprise organization launch guide](https://slack.com/help/articles/115005481226-Enterprise-organization-launch-guide)

## Discovery (10%)

### Question 4

A consultant is running security and policy discovery with Universal Containers to understand its current controls and desired future state for Slack. Which two questions should the consultant ask? Choose 2 answers.

- A. Are there populations that need more restrictive permissions or access than normal employees?
- B. Will single sign-on be required for everyone, and should guests sign in through it as well?
- C. Which prefixes should teams use in channel names for projects, teams, and social topics?
- D. Who will facilitate the end-user training sessions in each region during the launch?
- E. How many workspaces will each department need once the org is fully migrated?

**Correct answers:** A. Are there populations that need more restrictive permissions or access than normal employees?; B. Will single sign-on be required for everyone, and should guests sign in through it as well?

**Explanation:** Trailhead's example policies and settings discovery questions include whether some populations need more restrictive permissions than normal employees and whether SSO will be required for everyone, including guests. Channel name prefixes are a channel strategy topic. Training facilitators belong to the learning plan. Workspace counts are grid design decisions that draw on discovery but are not security and policy questions.

**Sources:** [Understanding Slack Management and Policy Recommendations](https://trailhead.salesforce.com/content/learn/modules/discovery-conversations-for-slack-implementations/explore-slack-management-and-settings-requirements), [Maximize Access & Security in Slack](https://trailhead.salesforce.com/content/learn/modules/identity-management-in-slack/explore-access-and-security-controls)

### Question 5

Bloomington Caregivers' leadership has written three draft statements and asks the consultant which one should become the Slack vision statement shared with all employees. Which draft should the consultant recommend?

- A. "We will launch Slack to every site by March, migrate all teams by June, and retire our old chat tool by September."
- B. "Slack will use SSO, two-factor authentication, and approved apps only, and channels will follow our naming convention."
- C. "With Slack, we will connect our sites in one transparent place so caregivers chase fewer updates and spend more time with patients."
- D. "Our goal is that 90 percent of employees send at least one Slack message per day within the first quarter after launch."

**Correct answer:** C. "With Slack, we will connect our sites in one transparent place so caregivers chase fewer updates and spend more time with patients."

**Explanation:** A vision statement explains "Why Slack?": how Slack benefits employees, which business goals it helps achieve, and what behaviors to encourage, and it helps employees see the long-term end state and what is in it for them. A launch and migration timeline is a project plan, not a vision. A list of security and naming rules describes policies and settings decisions. A daily-message target is a success metric that should support the vision, not replace it.

**Sources:** [Create a Vision Statement and Define Success Metrics](https://trailhead.salesforce.com/content/learn/modules/discovery-conversations-for-slack-implementations/create-a-vision-statement-and-success-metrics), [Translate Goals into Metrics](https://trailhead.salesforce.com/content/learn/modules/slack-analytics/translate-goals-into-slack-metrics)

## Grid Design (15%)

### Question 6

Cumulus Financial's Enterprise organization (Enterprise Grid or Enterprise+ plan) has five workspaces, and each has its own #announcements channel. Communications staff post the same message five times, and some employees miss updates. What should the consultant recommend?

- A. Build a workflow that copies every post from one #announcements channel into the other four.
- B. Create a dedicated announcements workspace and require every employee to join it as members.
- C. Create a Slack Connect channel that links the five #announcements channels into one channel.
- D. Replace them with one org-wide channel that is set as a default channel for all members.

**Correct answer:** D. Replace them with one org-wide channel that is set as a default channel for all members.

**Explanation:** Any multi-workspace channel can be made org-wide so it is accessible from every workspace, and it can be made a default channel for all members, which Trailhead recommends for company-wide announcements to avoid redundant, disconnected announcement channels. Copying posts with a workflow keeps the duplication and fragmentation. A separate workspace for announcements adds context switching and admin overhead for something a channel can handle. Slack Connect is for collaboration with external organizations, not for linking channels within one org.

**Sources:** [Strategies for Effective Workspace Design in Slack](https://trailhead.salesforce.com/content/learn/modules/slack-workspace-design/consider-alternatives-for-workspace-design), [Manage a workspace in an Enterprise organization](https://slack.com/help/articles/115005225987-Manage-a-workspace-in-an-Enterprise-organization)

### Question 7

Stakeholders at Ursa Major Solar find it hard to picture how their daily work would look in each of the three grid design options the consultant drafted. What should the consultant do?

- A. Fill in example channels on each option so stakeholders can see how their work would come together in Slack.
- B. Build each option as a live workspace in production and let stakeholders try them for a few weeks before choosing.
- C. Skip ahead to the channel strategy session and finish channel names before stakeholders review the grid options.
- D. Reduce the three options to a single option, since the stakeholders are clearly struggling to compare the choices.

**Correct answer:** A. Fill in example channels on each option so stakeholders can see how their work would come together in Slack.

**Explanation:** Trailhead's quick tip is to fill in example channels on the client's grid design options to help them visualize how their work comes together in Slack. Building every option in production creates workspaces that may need to be removed and confuses members. Channel strategy follows the grid design decision rather than replacing it. Removing options takes away the comparison the workshop is designed to support.

**Sources:** [Essential Grid Design Models for Effective Workspaces](https://trailhead.salesforce.com/content/learn/modules/designing-a-slack-enterprise-grid/compare-grid-design-models)

### Question 8

A consultant is reviewing discovery findings from a recently merged technology company. Which two findings point toward giving each original company its own workspace in the grid design? Choose 2 answers.

- A. The two companies use different app approval and app management processes that must stay in place for now.
- B. Employees of the acquired company feel disconnected from the larger company and want to be part of its culture.
- C. Both companies rely on the same Google Calendar, Jira and Zoom integrations and want them to work for everyone.
- D. Work streams will stay separate while the company audits redundancies and builds its integration plan.
- E. The larger company relies heavily on email for vendor communications and wants to reduce that volume over time.

**Correct answers:** A. The two companies use different app approval and app management processes that must stay in place for now.; D. Work streams will stay separate while the company audits redundancies and builds its integration plan.

**Explanation:** Different app approval processes that must be preserved and work streams that will remain separate both justify separate workspaces, because each company needs its own settings and employees can still spend most of their time in their own workspace. The culture finding points toward a shared global or social workspace and org-wide channels, not toward separation. Shared integrations point toward preapproving apps and installing them at the org level so all employees can use them. The email finding points toward an approach for external collaboration with Slack Connect.

**Sources:** [Explore Effective Grid Design Solutions for Business Needs](https://trailhead.salesforce.com/content/learn/modules/designing-a-slack-enterprise-grid/create-grid-design-options), [Conduct an Effective Grid Design Workshop for Clients](https://trailhead.salesforce.com/content/learn/modules/validating-slack-enterprise-grid-designs-with-the-client/run-a-grid-design-workshop)

## Policies and Settings (22%)

### Question 9

Universal Containers (Enterprise organization, Enterprise+ plan) wants only Org Admins and the internal communications team to create new multi-workspace channels and to change which workspaces a channel is shared with. What should the consultant recommend?

- A. Have each Workspace Owner remove the Create public channels permission for members on their own workspace's Account types page.
- B. Have an Org Owner or Org Admin edit the Create new multi-workspace channels permission in the org's Roles & permissions page.
- C. Set posting permissions on every multi-workspace channel so that only the communications team can post in or share the channel.
- D. Require Slack Connect approval for every channel so the communications team reviews each request before a channel is shared.

**Correct answer:** B. Have an Org Owner or Org Admin edit the Create new multi-workspace channels permission in the org's Roles & permissions page.

**Explanation:** Org Owners and Org Admins decide who can manage multi-workspace channels by editing the Create new multi-workspace channels permission in the org Roles & permissions page, which also controls who can change which workspaces a channel is shared with. Removing Create public channels at workspace level blocks ordinary channel creation and does not govern sharing across workspaces. Posting permissions decide who can post in a channel, not who can share it with workspaces. Slack Connect approval governs channels shared with external organizations, not channels shared between workspaces inside the org.

**Sources:** [Manage multi-workspace channels](https://slack.com/help/articles/115004485887-Manage-multi-workspace-channels-on-Enterprise-Grid)

### Question 10

Cloud Kicks runs an Enterprise organization (Enterprise Grid or Enterprise+ plan). In the settings workshop, stakeholders can't agree on one message editing window: Engineering wants members to edit messages at any time, while the Trading workspace wants editing turned off. They agree that each Workspace Owner should decide for their own workspace. What should the consultant recommend to the Org Owner?

- A. Set an org policy that allows editing at any time, and ask the Trading Workspace Owner to override it to Never.
- B. Leave the message editing org policy unset, so Workspace Owners and Admins choose the window in each workspace.
- C. Set an org policy of Never for every workspace, because Slack requires one editing window across an Enterprise org.
- D. Create a second organization for Trading, because editing rules can't differ between workspaces in one org.

**Correct answer:** B. Leave the message editing org policy unset, so Workspace Owners and Admins choose the window in each workspace.

**Explanation:** Workspace Owners and Admins can choose when to allow message editing only if an org policy hasn't been set; once Org Owners or Org Admins set the policy, it applies to every workspace in the org. Leaving the org policy unset is therefore how stakeholders let each workspace decide. Setting an org policy and expecting Trading to override it fails, because a workspace can't change a setting the org policy controls. Slack does not require one editing window per org, so forcing Never everywhere or creating a second organization ignores what the stakeholders agreed.

**Sources:** [Manage permissions for message editing and deletion](https://slack.com/help/articles/115004868646-Manage-permissions-for-message-editing-and-deletion), [Understanding Slack Policies and Settings for Teams](https://trailhead.salesforce.com/content/learn/modules/org-and-workspace-settings-in-slack-quick-look/learn-about-policies-and-settings-in-slack)

### Question 11

A consultant is coaching the Workspace Owner of Get Cloudy Consulting, which uses the Business+ plan, on interpreting the analytics dashboard. Which two statements should the consultant share? Choose 2 answers.

- A. The Channels tab includes private channel data for owners and admins who manage private channels.
- B. On the Business+ plan, the channel-level data in the Channels tab is available only for public channels.
- C. Daily active people counts only the people who posted at least one message on that day.
- D. Messages sent on the Overview tab includes messages posted by apps and bots in the workspace.
- E. Member-level data is best used to understand the whole team's usage, not to evaluate individuals.

**Correct answers:** B. On the Business+ plan, the channel-level data in the Channels tab is available only for public channels.; E. Member-level data is best used to understand the whole team's usage, not to evaluate individuals.

**Explanation:** On the Pro and Business+ plans, Channels tab data is available only for public channels, and Slack advises that activity data is best used to understand the whole team's use of Slack, not to evaluate an individual's performance. Private channel analytics are available only on Enterprise plans to owners and admins with permission to manage private channels. Daily active people counts people who read or sent a message, so readers count too. Messages sent on the Overview tab does not include messages sent by apps or bots.

**Sources:** [Understand the data in your Slack analytics dashboard](https://slack.com/help/articles/360057638533-Understand-the-data-in-your-Slack-analytics-dashboard), [View your Slack analytics dashboard](https://slack.com/help/articles/218407447-View-your-Slack-analytics-dashboard)

### Question 12

Northern Trail Outfitters has found employees creating their own outside Slack workspaces with their company email addresses. NTO runs an Enterprise organization (Enterprise Grid or Enterprise+ plan) and wants to stop members from joining external workspaces with the nto.com domain. What should the consultant recommend?

- A. Require SSO for all members so the nto.com email address can be used only to sign in to NTO's organization.
- B. Set every workspace in the org to Hidden so employees can't invite their company addresses to other workspaces.
- C. Turn on mandatory two-factor authentication so unsanctioned workspaces can't accept nto.com sign-ins.
- D. Have an Org Owner claim and verify nto.com with a DNS TXT record and restrict joining external workspaces.

**Correct answer:** D. Have an Org Owner claim and verify nto.com with a DNS TXT record and restrict joining external workspaces.

**Explanation:** On Enterprise plans, an Org Owner can claim and verify a domain through a DNS TXT record and apply the restriction on joining external workspaces, so other workspaces can't send invitations to addresses on that domain. Requiring SSO controls how members sign in to NTO's org, not whether outside workspaces accept nto.com invitations. Hidden is a workspace access setting inside NTO's org and has no effect on external workspaces. Mandatory 2FA strengthens sign-in but does not block anyone from joining other workspaces.

**Sources:** [Claim and verify email domains](https://slack.com/help/articles/5513043606547-Claim-and-verify-email-domains)

## Channel Strategy (10%)

### Question 13

Cumulus Financial has an Enterprise organization (Enterprise Grid or Enterprise+ plan) with five workspaces. Risk analysts in three of them need one shared place to work on a new regulatory project, and the client suggests creating a sixth workspace for it. What should the consultant recommend?

- A. Create a Slack Connect channel between the three workspaces so each team keeps its own copy of the project
- B. Create an org-wide channel so the project is visible to members of all five workspaces in the organization
- C. Create a new workspace for the project and invite the analysts from the three workspaces into it as members
- D. Create a multi-workspace channel and share it with only the three workspaces whose analysts need access

**Correct answer:** D. Create a multi-workspace channel and share it with only the three workspaces whose analysts need access

**Explanation:** Multi-workspace channels span selected workspaces so users from different workspaces can collaborate in one channel, which avoids adding a new workspace for a single project. Slack Connect is for working with people outside the organization, not between workspaces in the same org. An org-wide channel is present in every workspace, which is broader than the three workspaces that need it. A new workspace adds administrative overhead and splits work away from where the analysts already collaborate.

**Sources:** [Understand Channel Types and Settings for Effective Collaboration](https://trailhead.salesforce.com/content/learn/modules/slack-channel-strategy-basics/explore-channel-types)

### Question 14

Cumulus Financial's security team is hesitant to allow Workflow Builder in its Enterprise organization (Enterprise Grid or Enterprise+ plan). Which three admin controls can the consultant describe to address their concerns? Choose 3 answers.

- A. Restrict access to Workflow Builder to certain members instead of everyone
- B. Manage which connector steps members can add to the workflows they build
- C. Decide whether external people can use workflows in Slack Connect channels
- D. Require Slack Support to review each new workflow before it can be published
- E. Allow workflows to run only in private channels, never in public channels

**Correct answers:** A. Restrict access to Workflow Builder to certain members instead of everyone; B. Manage which connector steps members can add to the workflows they build; C. Decide whether external people can use workflows in Slack Connect channels

**Explanation:** Admins can restrict Workflow Builder access to certain members, manage which connector and custom steps can be added to workflows, and decide whether external organizations can use workflows in Slack Connect conversations. Slack Support does not review customers' workflows before publication; publishing is controlled by the client's own admin settings. No setting limits workflows to private channels only.

**Sources:** [Understanding Workflow Automation in Slack](https://trailhead.salesforce.com/content/learn/modules/business-process-automation-with-slacks-workflow-builder/identify-potential-workflows), [Manage Workflow Builder access and features](https://slack.com/help/articles/360035822734-Manage-Workflow-Builder-access-and-features)

## Governance Structure (Owner and Admin Roles) (8%)

### Question 15

Universal Containers keeps the default Slack Connect setting that requires admin approval, and wants a workflow form in #plz-slack-connect to replace email requests. Beyond urgency, approving manager and channel name, which two details should the form collect? Choose 2 answers.

- A. The Slack domain URL of the external organization
- B. The name and email of an admin at the external organization
- C. The external organization's Slack plan and paid seat count
- D. Whether each external member should be a single- or multi-channel guest
- E. The message retention policy the external organization has configured

**Correct answers:** A. The Slack domain URL of the external organization; B. The name and email of an admin at the external organization

**Explanation:** Slack's recommended Slack Connect request form collects urgency, approving manager, external organization name, workspace name, the external organization's Slack domain URL, the name and email of an admin at the external organization, the requested channel name and its purpose. The external organization's plan and seat count are not needed to set up a shared channel. Guest account types apply to guests added to your own workspace, not to members of another organization in Slack Connect. The external retention policy is not part of the standard request details.

**Sources:** [Trailhead: Manage Common Admin Requests](https://trailhead.salesforce.com/content/learn/modules/slack-admin-process-governance/manage-common-admin-requests)

## Learning and Enablement (18%)

### Question 16

After AW Computing's Workspace Owner enables SAML SSO on the Business+ plan, users signing in see: 'The SAML Response does not contain the correct Audience.' What should the consultant tell the Workspace Owner to fix?

- A. Replace the certificate on Slack's SSO page with the signing certificate currently sent by the identity provider.
- B. Change the Reply URL in the identity provider so that it points to the workspace's /sso/saml destination URL.
- C. Make the Service Provider Issuer in Slack match the Audience, also called the SP Entity ID, in the IdP settings.
- D. Enable signing of assertions in the identity provider, or clear the Assertions Signed box on Slack's SSO page.

**Correct answer:** C. Make the Service Provider Issuer in Slack match the Audience, also called the SP Entity ID, in the IdP settings.

**Explanation:** Slack's SAML troubleshooting table maps the Audience error to a mismatch between the Service Provider Issuer in Slack and the Audience (SP Entity ID or Relying Party Identifier) in the IdP; Slack supports https://slack.com and the workspace URL. Updating the certificate fixes a failed signature validation, not an audience mismatch. The Reply or ACS URL is the fix for an incorrect Destination error. Signing assertions addresses the error saying the assertion is not signed.

**Sources:** [Troubleshoot SAML authorization errors](https://slack.com/help/articles/360037402653-Troubleshoot-SAML-authorization-errors-Troubleshoot-SAML-authorization-errors)

### Question 17

AW Computing runs an Enterprise organization (Enterprise Grid or Enterprise+ plan). A small central team will be Org Admins, and each of six business units will have its own Workspace Admins. The consultant is designing the admin curriculum. What should the consultant recommend?

- A. One combined admin course for everyone, so all admins learn the same org-level policy settings in the same session.
- B. Train the Org Admins only and ask them to cascade the content to each workspace admin team on their own schedule later.
- C. Train the Workspace Admins only, because the Org Admins will learn org-level policy settings from the Slack Help Center.
- D. Segment the curriculum by role, with org-wide policies for Org Admins and workspace-level tasks for each Workspace Admin team.

**Correct answer:** D. Segment the curriculum by role, with org-wide policies for Org Admins and workspace-level tasks for each Workspace Admin team.

**Explanation:** A training plan is a matrix of who needs training and what they need to learn, and training works best when it focuses on each audience's role and day-to-day scenarios. In an Enterprise Grid org, org-level admins manage org-wide policies and settings while workspace admins manage their own workspaces, so their scenarios differ and the curriculum should be segmented. A single combined course spends workspace admins' time on settings they cannot manage. Cascading through the Org Admins removes the structured, hands-on training each group needs. Sending Org Admins to self-serve help leaves the most powerful role without tailored training.

**Sources:** [Trailhead: Develop a Training Plan](https://trailhead.salesforce.com/content/learn/modules/user-training-and-motivation/develop-a-training-plan), [Trailhead: Prepare for your Salesforce Slack Administrator Certification](https://trailhead.salesforce.com/content/learn/trails/prepare-for-your-salesforce-slack-administrator-certification), [Slack Help Center: Types of roles in Slack](https://slack.com/help/articles/360018112273-Types-of-roles-in-Slack)

### Question 18

AW Computing has 20 departments and only enough consulting hours for the initial training sessions. The client wants employees in each department to host follow-up trainings and give peer support. How should the consultant help the Workspace Owner choose those people?

- A. Choose each department's most senior manager, because their authority is enough to make teammates attend the follow-up training sessions.
- B. Choose only the Workspace Admins, because they hold the admin permissions that hosting follow-up training sessions in Slack requires.
- C. Export the Members list with the Days active column to find super-users, then build a champions network from them in each department.
- D. Choose the members who created the most channels during the pilot, because channel creation is the best measure of Slack expertise.

**Correct answer:** C. Export the Members list with the Days active column to find super-users, then build a champions network from them in each department.

**Explanation:** Slack suggests using the Days active column in the analytics Members export to identify super-users and then building an internal champions network from them; champions can host trainings, give peer-to-peer support and build momentum from within teams. Seniority alone does not mean someone uses Slack well or wants to teach it. Hosting a training session needs no admin permissions, and limiting champions to admins overloads a small group. Channel creation is a narrow signal compared with sustained daily activity.

**Sources:** [5 steps to support your team's adoption of Slack](https://slack.com/resources/slack-for-admins/5-steps-to-support-your-teams-adoption-of-slack)

## Related pages

- [Salesforce Slack Consultant practice exam](https://www.certifyforce.com/salesforce-slack-consultant-practice-exam)
- [Practice exam packs](https://www.certifyforce.com/practice-exams)
- [Official Slack Consultant exam guide](https://help.salesforce.com/s/articleView?id=005298991&language=en_US&type=1)