Slack-Con-201 Salesforce Certified Slack Consultant Questions and Answers

The best recommendation is B . For daily Agile syncs in a remote environment, Slack should reduce repetitive manual coordination and move routine updates into the channel where the team already collaborates. A Workflow Builder template can automatically prompt team members to provide updates at the right time, standardize the format of responses, and keep progress visible to the whole team. This is more scalable and more productive than relying on a manager to ask for updates manually. Option A is directionally useful, but it lacks automation and consistency. Option C may be useful if the team already has a project-management tool that should be integrated, but the question asks for a Slack feature that improves the sync process itself. Option D keeps the team in a synchronous meeting pattern and does not solve the productivity problem as effectively as automated asynchronous updates. Workflow Builder is the strongest Slack-native answer because it supports repeatable, channel-based Agile communication.

Reference topic: Channel Strategy — Agile standups, Workflow Builder, asynchronous updates, project channels, and remote team productivity.

==========

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.

==========

The correct answer is D . In an Enterprise Grid launch, admin-related governance should be handled at the organization level wherever possible, not separately across individual workspace settings. Creating a user group for all admins through org policies and the permissions tab gives the organization a centralized, repeatable way to manage an admin audience. This supports launch readiness because admins can be addressed consistently in announcements, enablement, support workflows, and governance communications. Option A is too workspace-local and does not scale cleanly across Enterprise Grid. Option B repeats the workspace-level mistake and also mixes admins and owners without matching the stated requirement. Option C incorrectly creates a user group for owners rather than admins. Option D matches the requirement and the Enterprise Grid operating model: use org-level policy configuration to create the intended admin user group. The key principle is centralized governance for enterprise-wide admin structures.

Reference topic: Policies and Settings — org policies, permissions, admin user groups, Enterprise Grid launch configuration, and centralized governance.

==========

The correct answer is D . The question asks for the most automated archive/unarchive request process. A channel workflow is the clear automation mechanism because it gives employees a structured request path instead of relying on free-form messages or direct admin intervention. In a well-designed support channel such as #plz-admin , users can open the channel workflows, select the archive/unarchive workflow, provide the required details, and route the request to the appropriate admin or approval process. Option A uses the wrong support-channel pattern and is only a manual message. Option B creates a private dependency on a workspace admin and does not scale. Option C is also manual and the channel name is malformed as #plz admin instead of a clean hyphenated Slack channel name. Option D uses the correct channel naming convention and applies Workflow Builder to standardize intake, reduce admin back-and-forth, and make the archive/unarchive process repeatable.

Reference topic: Channel Strategy — admin request channels, Workflow Builder automation, channel archive process, support-channel naming, and scalable user request management.

The correct answer is C . A Social workspace is designed for culture-building, employee connection, special-interest communities, affinity groups, hobbies, social interaction, and informal relationship-building. The client’s stated success vision is to help employees feel more connected with peers and improve connectivity among global and remote employees. At the same time, they want to limit noise and distraction in users’ primary workspaces. A separate social workspace solves both needs: it creates a dedicated place for community and culture while keeping non-work or loosely work-related conversation out of the main operational workspace. Option A, Secondary, is too generic and does not describe the cultural purpose. Option B, External, is used for collaboration with external parties and does not fit internal employee connection. Option D, Global, is typically the primary broad workspace for all employees and would not reduce noise in the primary workspace. The correct design isolates social collaboration without suppressing it.

Reference topic: Grid Design — social workspace design, employee connection, global/remote culture, workspace noise reduction, and primary workspace focus.

==========

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 answer is B . After an Enterprise Grid migration, users may belong to different workspaces inside the same grid. A public channel is discoverable only to members who have access to the workspace where that channel exists, unless it is made available as a multi-workspace or org-wide channel. In this scenario, some users can find and join the training channel, while others cannot. That pattern strongly indicates the channel itself is public, but it lives in a workspace that not all attendees belong to. Option A is possible in isolated cases, but it would not explain a consistent split across attendees. Option C is irrelevant because Slack Connect is used for collaboration with external organizations, not internal training-channel discovery. Option D would prevent users from joining through search unless invited, but it would generally affect all attendees who were not invited. The training setup should either invite all participants or place the training channel in a workspace accessible to the full training audience.

==========

The correct answer is A . After a workspace is migrated into Enterprise Grid, the existing workspace URL continues to function and directs users to the workspace now housed inside the Enterprise Grid organization. This matters because users may have bookmarks, desktop app references, saved links, browser history, integrations, or internal documentation that reference the original workspace URL. Telling users the URL will remain usable reduces confusion and prevents unnecessary support tickets after migration. Option B is wrong because after migration, the workspace is no longer operating as a separate original workspace outside the grid. Option C is wrong because the URL does not simply stop working as a normal migration outcome. Option D is wrong because Slack does not replace the workspace URL with a random new URL as part of the standard grid migration experience. Migration communications should explain login expectations, downtime, workspace availability, and continuity items such as the existing URL.

==========

The correct answer is A . By default, everyone except guests can send and accept Slack Connect direct message invitations with people outside the organization, unless the Enterprise Grid organization modifies those settings. This distinction matters because Slack Connect DMs are a lower-friction form of external collaboration than shared channels, but they still require governance. Full members are normally allowed to initiate or accept external DMs, while guests are excluded because their membership is already limited and scoped. Option B is too restrictive and describes an admin-only model that is not the default. Option C incorrectly places control with workspace-level admins and owners. Option D is too broad because it includes guests, which conflicts with the default exclusion. The consultant should explain both the default behavior and the client’s ability to tighten policy if the organization’s risk profile requires stricter external collaboration controls. For regulated or security-conscious clients, this setting should be reviewed during the policies and settings workshop.

Reference topic: Policies and Settings — Slack Connect DM permissions, default external collaboration behavior, guest restrictions, and Enterprise Grid policy review.

==========

The correct answers are A and B . Before launch, Enterprise Grid admins should make sure the essential app ecosystem is ready and governed. Installing and pre-approving a list of trusted apps gives users immediate access to approved productivity tools and reduces friction at launch. Establishing an app approval process is equally important because it defines how future app requests will be submitted, reviewed, approved, restricted, or rejected. Option C is useful as part of enablement, but the question asks which app rollout best practices should be completed before launch, and policy/process readiness comes first. Option D may apply when migrating an existing Slack environment with installed apps, but it is not the universal best answer for app rollout. Option E is valuable for ongoing app governance, but usage tracking and business-owner documentation are lifecycle practices, not the two most immediate pre-launch requirements. App launch readiness requires both approved apps and a clear approval model.

==========

The correct answer is C. Roles Admin. In Enterprise Grid governance, the role model determines who can administer users, channels, compliance, and role assignments. The question asks which role gives maximum flexibility to control non-admin member permissions. The Roles Admin is the best fit because this role is centered on role and permission management rather than a narrow operational function. Option A, Compliance Admin, is focused on compliance-related functions and is not designed for broad member-permission control. Option B, Users Admin, is related to user lifecycle and membership administration, but it does not provide the same role-governance flexibility. Option D, Channels Admin, is channel-focused and would be too limited for controlling broad non-admin member permissions. The tested concept is role-based governance on Enterprise Grid: administrative power should be delegated according to the function being controlled. Where the client needs flexibility around roles and permissions, the Roles Admin function is the logical recommendation.

The correct answer is C . Enterprise Key Management is not a casual toggle that an admin simply enables inside Slack after purchase. It is an advanced enterprise security capability that gives an organization control over encryption keys for Slack data and requires proper commercial entitlement, technical planning, and Slack-supported configuration. The client must purchase EKM as an add-on product and then coordinate configuration with Slack because key management affects encryption operations, security architecture, administrative access, and incident response procedures. Option A is wrong because EKM is not a free add-on and cannot be treated as a simple self-service feature. Option B is also wrong because EKM is not automatically included merely because the organization purchased “security tools.” It has to be entitled and implemented deliberately. The consultant’s guidance should set expectations correctly: validate licensing, engage Slack, coordinate with the client’s security and key-management teams, and implement the feature through the approved process.

Reference topic: Policies and Settings — Enterprise Key Management, advanced security add-ons, encryption governance, Slack-supported configuration, and enterprise security planning.

==========

The correct answer is B . Betalog needs a default announcement channel available to all members across a three-workspace Enterprise Grid. The practical sequence is to create the channel in one workspace, make it org-wide by adding the other two workspaces, and then configure it as a default channel in org settings. Option A incorrectly starts by creating the channel directly in org settings, which is not the clean workflow being tested. Option C has the same problem and also compresses separate steps into an inaccurate admin path. Option D correctly describes creating a channel and making it org-wide, but it incorrectly says to make it default in workspace settings. For an org-wide default channel, the default-channel control must be handled at the organization level. This recommendation supports consistent enterprise-wide announcements, ensures broad membership coverage, and avoids fragmented announcement channels across separate workspaces.

The correct answer is B . The requirement points directly to asynchronous, easy-to-understand, regularly scheduled learning content. A #slack-tips channel is the best fit because it allows the client to post small, digestible enablement content over time, reaching employees where they already work. This supports continuous reinforcement rather than a one-time training event. Option A provides more live instruction, but the user explicitly needs asynchronous learning, not another scheduled class. Option C creates a static long-form asset, but a one-hour video is not ideal for ongoing, bite-sized learning and will likely have lower engagement. Option D, an internal Champions Network, is valuable for advocacy and peer support, but it does not directly satisfy the request for regularly scheduled learning content. A tips channel can include short posts, Help Center links, mini use cases, workflow examples, and reminders about best practices. It also creates a searchable internal knowledge stream that employees can revisit at their own pace.

Reference topic: Learning and Enablement — asynchronous enablement, continuous learning, Slack tips channel, reinforcement strategy, and scalable adoption support.

==========

The correct answers are C, D, and E . Grid migration preparation requires identity cleanup and collaboration-boundary planning before the workspace is moved into Enterprise Grid. Addressing duplicate usernames helps reduce ambiguity and improves post-migration clarity for users and admins. Ensuring user emails match SSO is more critical because user identity matching depends heavily on email alignment between Slack and the identity provider; mismatches can produce duplicate accounts or login problems. Disconnecting Slack Connect channels is also part of migration preparation when external channel relationships cannot simply be carried forward unchanged or require re-establishment under the Enterprise Grid governance model. Option A, accepting the migration invitation, occurs as part of the migration execution flow, but it is not one of the core preparation cleanup actions being tested. Option B is wrong because guests do not need to be removed wholesale; guest strategy should be reviewed and handled deliberately. Option F is also wrong because apps should be reviewed and governed, not automatically removed from all migrating workspaces.

Reference topic: Delivery and Migration — grid migration readiness, identity cleanup, SSO alignment, duplicate user prevention, and Slack Connect migration preparation.

==========

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 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 best course of action is a structured support path: self-service first, escalation second. A mature Slack support process should give users clear internal resources for common access issues, such as SSO instructions, password guidance, supported device requirements, or known troubleshooting steps. If the user cannot resolve the issue through documented resources, the next step is a service ticket so the IT or Slack admin team can handle the problem through a trackable support workflow. Option A is too narrow and assumes the issue is local connectivity or password-related. Option B skips self-service and increases ticket volume unnecessarily. Option C relies on a channel and a phone call, which may be useful in some urgent cases but is not the best general process for access issues because access problems often require identity-provider or admin intervention. Slack’s help ecosystem emphasizes searchable help resources and structured admin support, and the consultant’s role is to design support processes that scale beyond launch.

Reference topic: Learning and Enablement — user support model, self-service resources, escalation paths, and adoption operations.

==========

The correct answer is C . Slack channel strategy should reflect how work actually happens, and organic channel creation is a core part of that model. Channels are most effective when teams create them around real projects, decisions, customers, functions, incidents, communities, or workflows instead of waiting for admins to centrally manufacture every collaboration space. Option A is too loose because “customize their own channels” without strategy can lead to inconsistency and channel sprawl. Option B is too restrictive; forcing admins to create all project channels slows collaboration and turns Slack into a ticket-driven workspace instead of a dynamic work platform. Option D has some value because standard channels and prefixes can model good behavior, but it does not answer the broader question of whether users should be allowed to create channels. The best practice is not uncontrolled chaos or admin-only creation; it is user-driven, authentic channel creation supported by clear naming conventions, channel purpose guidance, and governance.

Reference topic: Channel Strategy — organic channel creation, channel governance, naming conventions, user empowerment, and scalable collaboration design.

==========

The correct answer is B . A security-focused discovery question should expose whether the client has different risk profiles across departments, roles, data types, or user populations. Asking whether some groups need more restrictive permissions or access than typical employees directly uncovers security and governance requirements that affect workspace access levels, private channel strategy, guest access, Slack Connect rules, app approvals, retention, DLP, eDiscovery, and administrative role design. Option A is useful for collaboration mapping, but it does not directly identify security concerns. Option C belongs to support-process discovery, not security discovery. Option D is relevant to external collaboration and Slack Connect governance, but it is narrower than the broader security requirement in the question. Security discovery must identify populations that require stronger controls, such as legal, finance, HR, executives, regulated teams, contractors, or teams handling confidential data. This answer gives the consultant the clearest path to designing appropriate policies, permissions, and access boundaries.

Reference topic: Discovery — security requirements gathering, restricted access groups, permission design, and governance-driven discovery.

==========

The correct recommendation is Monthly . Guest and channel cleanup is an operational governance activity, not a one-time launch task. Slack environments evolve quickly: projects end, external partners change, guest access expires, channels become inactive, and sensitive collaboration spaces may no longer require the same membership. A monthly cleanup cadence is frequent enough to reduce access risk and channel clutter without creating excessive administrative burden. Option A is weak because ad hoc cleanup is reactive and usually happens only after a problem occurs. Option B may be too frequent for most organizations and can create unnecessary admin overhead unless the environment is unusually high-risk. Option D is not frequent enough; annual reviews allow stale guest access and unused channels to accumulate for too long. The point of guest and channel cleanup is to keep collaboration intentional, secure, and manageable. This cadence should be owned through the governance structure and executed by the appropriate admin or owner roles.

Reference topic: Governance Structure (Owner and Admin Roles) — operational governance cadence, guest lifecycle management, channel cleanup, and administrative accountability.

==========

The best answer is Quarterly . Policies and settings should be reviewed on a predictable cadence because Slack governance is not a one-time configuration task. As user behavior, app usage, external collaboration, compliance requirements, and business structure change, the client must validate whether the current settings still support the intended operating model. Quarterly is frequent enough to identify drift before it becomes operational risk, but not so frequent that the review becomes administratively noisy. Monthly reviews are usually excessive unless the organization is in an active launch or remediation phase. Ad hoc reviews are reactive and create inconsistent governance. Annual reviews are too slow for a collaboration platform where workspace, channel, app, and Slack Connect usage can change rapidly. The Salesforce Slack Consultant domain structure treats Policies and Settings as a major exam area, reinforcing that governance controls must be designed, monitored, and adjusted throughout the lifecycle of the Slack program.

Reference topic: Policies and Settings — governance cadence, settings validation, risk control, and operating model alignment.

==========

The correct answer is B . To provide hands-on practice with message threads, the activity must require participants to post a reply in a thread. An ice-breaker prompt works well because the facilitator can post one starter message and ask participants to reply in the thread with their answer. This gives learners practical experience opening a thread, replying in context, and understanding how threads keep side conversations organized without cluttering the main channel. Option A tests conceptual knowledge but does not provide actual practice using threads. Option C uses a poll, which may teach polling behavior or reactions but does not necessarily require threaded replies. Option D uses a huddle, which is an audio/video collaboration feature and does not teach message-thread behavior. Effective Slack User Essentials training should turn core features into simple interactive tasks. The music ice-breaker is low-risk, approachable, and naturally suited to practicing threaded conversation in a training channel.

Reference topic: Learning and Enablement — live training activities, hands-on thread practice, in-channel exercises, Slack User Essentials, and interactive learning design.

==========

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.

==========