Slack-Con-201 Practice Questions

Slack advises informing members that they can keep working in the source workspace while data copies in the background; only a short (typically <-20 min) downtime will occur at final cut-over when everyone is signed out and moved to the new Grid workspace.

A. Claims the workspace is unavailable throughout the whole migration—Slack keeps it active until the brief cut-over window.

C. Says members must install a new desktop app—existing clients continue to work after signing back in.

D. States all message history is lost—Slack copies the entire message and file history to the Grid org.

1. Slack Help Center, “Migrate workspaces to Enterprise Grid”, section “What members can expect during migration” (2024-02-05).

2. Slack Enterprise Migration Guide, p.8 “Downtime window (<20 min) at cutover”.

In the Enterprise Grid Org Dashboard, the “Enabled members” metric is the authoritative count of every person whose account is currently active in the organisation, providing the complete number leadership is requesting.

A. “Active members (last 30 days)” omits dormant but enabled accounts.

B. “Invited members” includes people who have not joined yet.

C. “Guests” counts a subset, not the whole population.

1. Slack Admin Analytics Guide, §“People” → “Enabled members” definition.

2. Slack Help Center article #4409825535767 “Understand analytics terms”, table row “Enabled members”.

3. University of Melbourne ISYS90088 lecture “Metrics in Collaboration Platforms”, slide 19.

Understanding a client's existing and frequently used applications is crucial during the discovery phase. This knowledge allows the consultant to identify key workflows that can be integrated into Slack. By bringing essential tools and processes into the Slack environment, users can perform their daily tasks more efficiently without context switching. This integration demonstrates immediate value, streamlines work, and is a primary driver for user adoption and engagement during the launch, ensuring the platform becomes a central hub for productivity.

B: While app integrations may have costs, the primary reason for this discovery question is to understand workflows and drive adoption, not to set a budget.

C: App usage might indirectly indicate technical proficiency, but its main purpose is to map business processes to Slack's capabilities for efficiency gains.

D: Security is a vital consideration for any app integration, but the initial question about frequently used apps focuses on improving user experience and workflow.

1. Salesforce Trailhead, Slack Basics: Find and Start Conversations. This module emphasizes that "Apps and integrations bring the tools you use every day right into Slack," highlighting the importance of integrating existing tools to streamline work.

2. Slack Help Center, A guide to Slack for new users. The section "Connect your tools to Slack" states, "Bringing apps into your Slack workspace will help you centralize your work and save you from switching between different tools and windows." This directly supports the goal of increasing efficiency.

3. Slack Help Center, Add apps to your Slack workspace. This guide explains that apps "help you connect the other software and services you use to get work done with Slack," reinforcing the concept of integrating existing workflows.

The most appropriate best practice is to design the Grid structure based on how people actually work, not a rigid organizational chart. Since discovery revealed that departments are highly collaborative, creating workspaces for broad, cross-functional business units or value streams is the recommended approach. This design facilitates seamless collaboration across departmental lines, reduces the friction of working in separate, siloed workspaces, and aligns the Slack architecture with the company's collaborative culture. It provides structure without creating unnecessary barriers.

A. Following the client's org chart design: This would create digital silos that directly contradict the company's collaborative nature, hindering the very cross-functional work that needs to be supported.

B. Creating a single workspace for the entire organization: For a large company, a single workspace can become chaotic, difficult to navigate, and hard to administer, leading to information overload.

D. Creating workspaces for each department: This is the same as following the org chart and would create the silos that the best practice aims to avoid in this collaborative environment.

1. Slack Help Center. (n.d.). A guide to Slack Enterprise Grid administration. Retrieved from https://slack.com/help/articles/360001809983-A-guide-to-Slack-Enterprise-Grid-administration. (See section: "Design your org structure," which explicitly states, "Think about how people work together, not just your org chart.").

2. Slack. (n.d.). Slack Enterprise Grid: A guide for admins and owners. (This foundational guide for Enterprise Grid emphasizes designing the structure to support collaboration and business objectives, often recommending grouping by large functions or divisions rather than strict departmental lines).

Pre-approving apps on an Enterprise Grid provides two key benefits. First, it reduces the administrative burden (B) because admins vet a list of applications for security and compliance once, eliminating the need to review and respond to numerous individual requests. Second, it streamlines the process for users, allowing them to quickly add vetted, secure apps to their workflows (D) without waiting for an admin's approval. This empowers users to customize their tools and improve productivity while maintaining organizational governance and security standards.

Allows any user to install any app: This is incorrect. Users can only install apps from the pre-approved list; all other apps are still subject to review.

Prevents users from using any apps: This is the opposite of the feature's intent, which is to facilitate the safe use of approved apps.

Automatically installs apps for every user: Pre-approval makes an app available for installation; it does not automatically install it for everyone in the workspace.

1. Slack Help Center. (n.d.). Manage app approvals for your organization. Retrieved from https://slack.com/help/articles/360003122033-Manage-app-approvals-for-your-organization. (See sections: "How it works" and "Set up an app approval process").

2. Slack Help Center. (n.d.). A guide to app management for admins. Retrieved from https://slack.com/help/articles/1500003349541-A-guide-to-app-management-for-admins. (See section: "Streamline app approvals").

3. Slack Platform. (n.d.). Building an app for Enterprise Grid. Retrieved from https://api.slack.com/enterprise. (This resource discusses the administrative controls, including app management, that are central to the value of Grid).

A successful Slack rollout communication plan should focus on preparing end-users for the change. The core components to highlight are the announcement timeline, which sets expectations for when changes will occur; key messages, which explain the "why" behind the move and its benefits; and training resources, which empower users with the knowledge to use the platform effectively. This combination ensures users are informed, motivated, and prepared, which is critical for driving adoption and a smooth transition.

Technical migration plan, user provisioning scripts, and API integration specs: These are part of the technical implementation plan, not the user-facing communication strategy.

Security policies, data retention rules, and compliance reports: These are crucial for governance and administration but are not the primary components of a rollout communication plan for end-users.

Budget allocation, license procurement, and vendor contracts: These are project management and procurement tasks, not elements of a user communication plan.

1. Slack. (n.d.). Slack Rollout Guide. Retrieved from https://slack.com/resources/slack-for-admins/slack-rollout-guide. This official guide outlines key steps, including "Draft your internal communications" and "Train your company," which directly correspond to key messages and training resources.

2. Slack. (n.d.). Your guide to launching Slack. Retrieved from https://slack.com/resources/slack-for-it/your-guide-to-launching-slack. The guide emphasizes a phased approach (pre-launch, launch, post-launch), which is managed by a timeline, and stresses the importance of communicating benefits and providing training.

Enterprise Grid requires unique usernames org-wide; when the same username exists with different emails, rename one account in its source workspace to a unique username before running the migration.

A. Deleting an account would orphan its messages and violate data-retention policies.

B. Slack cannot automatically merge two distinct email identities.

D. Ignoring the warning will make the migration fail because duplicate usernames are blocked.

1. Slack Help Center, “Understand the pre-migration report”, subsection “Duplicated and illegal usernames” (2024-02-20).

2. Slack Enterprise Grid Migration Guide, p.11 “Rename one of the duplicate users so that all usernames are unique before launch”.

Before launching apps on an Enterprise Grid, establishing a strong governance framework is critical. The two most important pre-launch best practices are establishing a formal app approval process and curating an initial list of approved apps. Establishing an approval process (B) ensures that all future app requests are vetted for security, compliance, and business value. Pre-approving and installing a core list of applications (A) provides immediate value to employees upon launch and sets a standard for the types of tools the organization endorses, streamlining initial adoption in a controlled manner.

C. Enable employees on how to use and request apps.

This is a crucial step, but it typically occurs during or immediately after launch as part of the communication and training plan, not entirely before.

D. Perform a one-time audit of existing apps and processes.

While a valuable exercise for understanding the current state, it's a preliminary data-gathering step rather than a core practice for the new rollout itself, which is covered by establishing new processes (B).

E. Track usage of apps and document the business owner for each app.

Tracking usage is a post-launch activity. It is impossible to track the usage of apps before they have been rolled out to employees.

1. Slack Help Center, "Guide to app management in Slack."

Reference for Answer B: In the section "Step 1: Establish an app approval process," the guide explicitly states, "Before your members start using apps in Slack, we recommend that Org Owners and Admins establish an app approval process." This confirms it as a pre-launch requirement.

Reference for Answer A: The section "Step 2: Curate a list of apps for your workspace" advises, "To help your members get started, you can pre-approve a list of apps for any workspace in your org." This supports providing a pre-vetted list before a general rollout.

2. Slack Help Center, "Manage app approvals on Enterprise Grid."

Reference for Answer B: The overview section of this document details the setup of app approval policies. The entire premise is that this administrative framework must be configured before users begin requesting and installing apps to maintain organizational control. It notes, "On the Enterprise Grid plan, Org Owners can set an org-level app approval policy..." This setup is a foundational, pre-launch task.

An announcement-only channel is the ideal solution. By restricting posting permissions to specific individuals, such as team leads or internal communications staff, the client can ensure that only official updates are shared. This prevents important messages from being buried in conversational noise, directly addressing the concern that employees might miss the updates. Employees can still read all messages and use threads to ask questions, but the main channel remains clear and focused on key information, reducing the need for emails and meetings.

A. A private channel limits visibility to only invited members, which is not suitable for company-wide updates.

C. A public channel allows anyone to post, which would lead to the conversational noise the client wants to avoid.

D. A multi-workspace channel (shared channel) is for connecting with external organizations, not for internal announcements.

1. Slack Help Center. (n.d.). Create a channel. Retrieved from https://slack.com/help/articles/201402297-Create-a-channel. See section: "Create announcement-only channels".

2. Slack Help Center. (n.d.). Set channel posting permissions. Retrieved from https://slack.com/help/articles/360017932493-Set-channel-posting-permissions. This document details how to restrict who can post in a channel, the core feature of an announcement-only channel.

To prevent users from creating new, unmanaged Slack workspaces with a company email address, the organization's administrators must claim their email domain(s). This feature, available on the Enterprise Grid plan, centralizes administration by redirecting any new workspace sign-ups using a claimed domain into the official Grid organization. This ensures all company-related Slack activity occurs within the managed, secure environment, preventing data fragmentation and shadow IT. This is a direct, preventative technical control that solves the client's problem.

A. Relying on user communication/policy: This is not a technical preventative measure and is easily ignored by users, making it an unreliable solution for governance.

B. Implementing Single Sign-On (SSO): SSO controls authentication and access to the existing Grid, but it does not prevent a user from creating a new, separate workspace.

C. Deactivating users reactively: This is a reactive measure taken after the policy violation has already occurred, rather than preventing it from happening in the first place.

1. Slack Help Center. (n.d.). Claim domains for your organization. Retrieved from https://slack.com/help/articles/221019907-Claim-domains-for-your-organization. (See section: "How domain claiming works").

2. Slack Help Center. (n.d.). A guide to Slack Enterprise Grid administration. Retrieved from https://slack.com/help/articles/360001809983-A-guide-to-Slack-Enterprise-Grid-administration. (See section: "Set up your org: Claim your domain").