Free Salesforce Slack-Con-201 Practice Exam with Questions & Answers

The correct answer is A. #help. The purpose of a channel prefix is to create predictable navigation and signal the function of the channel before users even open it. In this scenario, the client has scattered employee questions across many channels, which weakens searchability and makes issue triage inefficient. A #help prefix clearly tells users that the channel is intended for questions, support, troubleshooting, and service requests. For example, the organization can later scale this pattern into channels such as #help-it, #help-hr, #help-security, or #help-slack. Option B, #security, identifies a department or subject area, but it does not clearly indicate a general help or question-intake function. Option C, #hello, sounds social and does not support triage. Option D, #search-first, promotes a behavior but is not a clean support-channel prefix. The consultant should recommend a naming convention that reinforces channel purpose, reduces duplicate questions, and supports a searchable support model.

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.

==========

The correct answer is B . A major reason for moving to Enterprise Grid is to centralize governance across multiple workspaces. Enterprise Grid allows an organization to manage policies, security controls, identity settings, app governance, and administrative structures at the organization level instead of managing each workspace independently. This becomes important when a company has several Slack workspaces and wants consistent controls, standardized access, centralized compliance, and a unified operating model. Option A is incorrect because Slack Connect is not exclusive to Enterprise Grid; it can be used on paid Slack plans, so it is not the strongest reason for a grid migration. Option C is also not specific to Enterprise Grid because workflows and app integrations are available outside Grid. Option D describes a type of migration scenario, but it is not the core business reason a client would pursue Enterprise Grid. The exam is testing whether the consultant understands the strategic value of Grid: enterprise-scale governance and centralized administration across workspaces.

Reference topic: Delivery and Migration — Enterprise Grid migration rationale, centralized policies, shared settings, multi-workspace governance, and enterprise administration.

==========

The correct answer is A . Multi-workspace channels are specifically designed to support collaboration across workspaces without changing the overall grid design. The client has already agreed to four workspaces: Sales, Marketing, Finance, and Social. The concern is cross-functional work between Sales and Marketing, not the entire architecture. A multi-workspace channel allows the relevant Sales and Marketing users to collaborate on joint initiatives while still keeping the Sales and Marketing workspaces distinct. Option B is poor design because the Social workspace should not become a dumping ground for business operations; that would create noise and weaken the social workspace’s purpose. Option C violates the requirement to maintain the final grid design because it adds a fifth workspace. Option D is weak because DMs hide project context, reduce transparency, and do not scale for cross-functional initiatives. Multi-workspace channels solve the exact problem: shared project collaboration across workspace boundaries while preserving the agreed workspace model.

==========

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.

==========

The correct answer is that eDiscovery applications require read access, while DLP applications require both read and write access. The difference comes from the purpose of each control. eDiscovery tools are used by legal, compliance, or security teams to retrieve and preserve Slack data for review, investigation, audit, or litigation support. Their core function is to access content for discovery, so read access is sufficient. DLP tools are different because they inspect content for sensitive information and may need to act on policy violations. That action can include flagging, quarantining, deleting, redacting, or otherwise enforcing rules on messages or files. Because of this enforcement role, DLP integrations require broader read and write capability. Option A is too broad because eDiscovery does not require write access. Option B incorrectly says eDiscovery needs create access. Option C understates DLP’s access by describing create and update rather than the broader read/write requirement.

Reference topic: Policies and Settings — Enterprise Grid security integrations, eDiscovery access model, DLP enforcement, compliance applications, and data protection controls.

==========

The correct answer is A. Approval policies for apps and external collaboration are governance and policy decisions, so the right stakeholders are the people responsible for Slack policies and settings. This may include Org Owners, Org Admins, security, compliance, legal, IT, or collaboration platform owners depending on the client’s operating model. Option B is too narrow because the head of IT may not own Slack-specific policy decisions, especially in a mature Slack environment where security, compliance, or collaboration governance may share responsibility. Option C is misaligned because communication and learning stakeholders are important for rollout messaging and enablement, not app approval or Slack Connect policy decisions. Option D is also insufficient because superusers understand usage patterns but usually do not own enterprise policy decisions. The consultant should identify decision-makers by responsibility, not title alone. Asking who owns policies and settings ensures the correct people attend the discussion and prevents policy decisions from being made by stakeholders without proper authority.

The correct answer is D . For a security-conscious financial services firm, Slack 101 training must be shaped by the client’s actual policies and settings. Introductory training should not teach generic Slack behavior that conflicts with configured rules around channel creation, message retention, external sharing, app approvals, guest access, Slack Connect, file uploads, retention, or notification controls. Option A, Block Kit, is irrelevant for a basic end-user training session because Block Kit is used for app interface design, not normal Slack 101 usage. Option B and Option C are important for enterprise security architecture, but end users generally do not need deep training on the specific eDiscovery or DLP applications. What they do need is practical guidance on what they can and cannot do in Slack based on the organization’s configured controls. The learning plan must reflect the client’s compliance posture so users understand approved collaboration behavior from day one.

Reference topic: Learning and Enablement — Slack 101 customization, regulated-industry training, policies and settings alignment, secure collaboration behavior, and end-user readiness.

==========

The correct answer is D . The client’s discovery inputs point to three separate collaboration needs. First, heavy cross-functional collaboration and a desire to reduce communication barriers require a general global workspace where internal employees can collaborate broadly. Second, working with many external partners creates a need for an external workspace or external-collaboration structure where partner-facing work can be governed and organized. Third, reducing barriers and supporting connection across the organization commonly benefits from a social workspace, where employees can build culture and community without cluttering the primary work environment. Option A addresses global and external work but omits the social/cultural collaboration layer. Option B includes social but fails to provide a dedicated external-collaboration design. Option C is too simplistic; putting all collaboration into one global workspace can increase noise and blur governance boundaries, especially with external partners. Option D gives the cleanest basic grid pattern: broad internal collaboration, structured external collaboration, and dedicated social connection.

Reference topic: Grid Design — basic Enterprise Grid model, global workspace, external workspace, social workspace, cross-functional collaboration, and partner collaboration design.

==========

The activity that would not be included is Grid design . The client is on a Slack Business+ plan, not Enterprise Grid. Grid design applies when designing an Enterprise organization that may contain multiple workspaces, workspace access levels, multi-workspace channels, and centralized org-level administration. A Business+ engagement can still require discovery, governance recommendations, and channel strategy because the customer has more than 200 employees, works with external partners, and wants organized collaboration. However, it does not require an Enterprise Grid architecture unless the client is moving to an Enterprise plan. Option A is required because the consultant still needs to understand business goals, user groups, external collaboration, and pain points. Option B is still relevant because policies and admin responsibilities matter on Business+. Option D is central because channel naming, channel purpose, external collaboration, and social/community channels are directly tied to the client’s vision. Slack’s Enterprise documentation distinguishes Enterprise organization capabilities such as multiple workspaces and multi-workspace channels from standard workspace administration.

Reference topic: Grid Design — plan eligibility, Enterprise Grid architecture, and when grid design is in scope.

==========