Salesforce Slack-Con-201 - Salesforce Certified Slack Consultant

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 . 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 D . The scenario says users are switching between multiple workspaces and feeling overwhelmed. The most effective grid-design recommendation is to apply the 80/20 rule , where users spend most of their time in a primary workspace and only move into additional workspaces for specific, intentional needs. This reduces cognitive load, lowers context switching, and gives users a clearer home base for daily work. Option A is a good design principle, but it is broad and does not directly solve the user behavior problem of frequent workspace movement. Option B is important for scalability, but future growth planning does not immediately reduce workspace-switching friction. Option C, multi-workspace channels, can help certain cross-functional conversations span workspaces, but it is not the best overarching practice for reducing user overwhelm across the grid. The primary-workspace model gives the user a predictable operating pattern: most work happens in one main workspace, while additional workspaces are exceptions for specialized collaboration.

Reference topic: Grid Design — workspace movement reduction, 80/20 rule, primary workspace model, user experience, and Enterprise Grid usability.

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

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

==========

The correct answer is 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 A . The constraint is explicit: the SOW only includes one Admin Essentials training, but the client has twenty Workspace Admins distributed across North America, China, and Australia. A tailored video series provides reusable, asynchronous enablement that can reach all admins across time zones without exceeding scope. This is a practical learning-design response: it preserves project boundaries while still giving the admin audience role-specific training materials. Option B is poor consulting practice because offloading the training to the client’s IT team does not ensure quality, consistency, or alignment with the Slack launch plan. Option C is not enablement; 24/7 support is reactive and does not prepare admins to perform their role. Option D may be reasonable if the client wants expanded live training, but it changes scope and therefore does not meet the phrase “within the scope of the project.” The best answer is to supplement the single live Admin Essentials session with scalable admin-focused video content.

Reference topic: Learning and Enablement — admin training strategy, asynchronous enablement, time-zone coverage, SOW constraints, and scalable learning materials.

The correct answer is C. The pre-migration report specifically flags the issue under Duplicated and Illegal Usernames, so the immediate defect to resolve is the duplicated username. Because the same username exists in both migrating workspaces but the email addresses are different, Slack cannot treat the records as the same clean identity without addressing the username conflict. Changing one of the usernames removes the duplicate username condition before the migration proceeds. Option A is too destructive and could remove a legitimate user account. Option B is irrelevant because converting the user to a multi-channel guest does not resolve duplicate or illegal username status. Option D may be relevant to identity hygiene in other migration scenarios, especially when preventing duplicate users through SSO alignment, but the question’s report category is specifically username duplication. The consultant should distinguish between user identity matching and username validity. Here, the recommended remediation is to make the usernames unique so the migration report no longer flags the user under duplicated or illegal usernames.