Salesforce Slack-Con-201 - Salesforce Certified Slack Consultant

The correct answer is B . A grid design executive summary must be decision-ready, not just descriptive. The client needs a clear view of the recommended workspaces, the access level for each workspace, the benefits of the chosen model, and the key considerations or tradeoffs. Workspace recommendations define the structure of the Enterprise Grid. Access level is essential because it determines whether workspaces are Open, By Request, Invite Only, or Hidden. Benefits explain why the recommendation supports the client’s collaboration model. Key considerations make the tradeoffs visible so leadership understands operational impact, governance needs, and future scalability. Option A includes channels and benefits, but it omits access level and considerations, which are more central to grid design approval. Option C is too abstract because a model name alone does not give executives enough implementation detail. Option D is closer, but it still misses workspace access level and benefits. The executive summary should help stakeholders approve the chosen design with a complete understanding of structure, access, value, and implications.

Reference topic: Grid Design — executive summary, workspace recommendations, access model, design benefits, and implementation considerations.

==========

The correct recommendation is to identify one stakeholder for general communications and additional stakeholders for department-specific communications. The scenario describes a layered communication model: executive leadership owns broad organizational messaging, while department or director-level leaders adapt follow-up communications to the needs of their own teams. A strong Slack communication plan must mirror that operating model by defining communication owners, audiences, message responsibilities, and delivery channels. Option A may be useful in some organizations, but simply creating department announcement channels does not solve ownership and coordination. Option B is too rigid; threading can be useful for keeping questions and discussion organized depending on the channel’s purpose. Option D focuses on engagement tools, but sentiment capture is secondary to the core requirement: structured communication ownership across enterprise and department levels. Option C directly supports change management because it assigns accountability for enterprise-wide communications and localized reinforcement. This prevents message gaps, duplicate announcements, and inconsistent guidance during launch.

Reference topic: Learning and Enablement — communication planning, stakeholder ownership, change management, department-level reinforcement, and launch communications.

==========

The correct answers are A and D . The client’s constraint is that employees may not be able to attend pre-scheduled training because of competing initiatives. That immediately reduces the value of synchronous formats and increases the value of self-paced enablement. Videos let employees learn asynchronously, pause, replay, and consume material when their schedule allows. Documentation provides a durable reference that employees can search and revisit while using Slack. Together, videos and documentation create a flexible learning path that does not depend on everyone being available at the same time. Option B, a customer story, may inspire adoption but does not provide practical training coverage. Option C, live training, is exactly what the client may struggle to attend. Option E, a leadership AMA, can support launch engagement, but it is still scheduled and interactive rather than a reliable training delivery method for employees with limited availability. The consultant’s job is to adapt the learning format to the client’s capacity constraints, not force the standard delivery model.

Reference topic: Learning and Enablement — asynchronous learning design, video enablement, documentation strategy, launch constraints, and flexible training delivery.

==========

The correct answer is D . If the client needs a complete count of the number of people in the workspace, the correct org-level metric is Total membership . Full members alone would undercount the population because it excludes guests. Guests alone would obviously undercount because it captures only external or limited-access users. Members who posted is an engagement metric, not a population metric; it measures activity, not total people. Senior leadership reporting usually requires a clear rollup metric that represents the entire membership footprint, especially in Enterprise Grid where leadership may need visibility across workspaces, users, guests, and adoption trends. Total membership is the only option that reflects the complete count of people associated with the workspace. The consultant should distinguish between membership metrics and engagement metrics: membership tells how many people are present, while posting metrics tell how many are actively participating. For a complete count, total membership is the only defensible recommendation.

Reference topic: Governance Structure (Owner and Admin Roles) — org-level reporting, workspace membership metrics, admin analytics, and leadership reporting.

==========

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.

==========

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 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 B . If the identity provider supports both SSO and SCIM, both should be configured before launch. SSO provides secure authentication and allows users to access Slack through the organization’s identity system. SCIM supports automated user provisioning and deprovisioning, which is essential for launch readiness, user lifecycle management, and administrative efficiency. Option A is incomplete because SSO alone handles authentication but does not automate provisioning. Option C delays SCIM until after launch, which creates avoidable manual work and may produce onboarding inconsistencies. Option D is also incomplete because SCIM provisioning without SSO does not fully satisfy secure login and access requirements. For a first-time Slack launch, identity configuration is not optional cleanup work; it is foundational launch infrastructure. Configuring both SSO and SCIM before launch gives admins control over who gets access, reduces manual invites, supports lifecycle governance, and prevents avoidable access issues during rollout.

==========

The correct answers are A and D . To tailor Admin Essentials training properly, you must know what Workspace Owners and Admins are actually allowed to do in the client’s environment. The Policies & settings documentation identifies configured permissions, such as who can manage channels, approve apps, invite users, use Slack Connect, create private channels, or perform administrative actions. The roles and responsibilities matrix clarifies which client roles are accountable for specific operational tasks. Together, these deliverables tell you both the technical permission model and the human ownership model. Option B, the SOW, defines scope and deliverables but usually does not list detailed Slack permissions. Option C, the communications plan, governs messaging and audience outreach, not admin capabilities. Option E, Grid Orientation curriculum, is a training asset, not the source of truth for configured permissions. Admin training should never be generic; it must match the client’s policy decisions and role assignments exactly.

==========

The correct answer is to create workspaces based on how information is naturally shared. Enterprise Grid design should reflect real collaboration patterns, not simply mirror the company’s reporting structure. The discovery finding is decisive: departments frequently collaborate across boundaries, so a strict department-by-department workspace model would create unnecessary silos, increase channel fragmentation, and make cross-functional work harder. Option A is generally good design language, but it is too broad and does not directly answer the discovered business need. Option B can be useful as a simplification principle, but “minimum number” alone is not enough; the structure must map to how work actually happens. Option D is the trap answer because it follows the client’s stated assumption rather than the consultant’s discovery evidence. Slack’s Enterprise Grid model supports multiple workspaces and multi-workspace channels so organizations can structure collaboration around functional, regional, confidential, or cross-functional work patterns.

Reference topic: Grid Design — discovery-led workspace architecture, information flow, collaboration patterns, and workspace strategy.

==========