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 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 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 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 best recommendation is to collaborate through multi-workspace channels. The scenario requires long-term collaboration across departments that sit in different workspaces, including finance and legal, while keeping the acquisition private. Multi-workspace channels are designed for this Enterprise Grid pattern because they allow a channel to exist across selected workspaces without forcing every participant into a new workspace or duplicating conversations across separate channels. The channel can be private, tightly scoped, and available only to the required participants from each relevant workspace. Option A creates a separate hidden workspace, but that is heavier than necessary and can isolate work from the departments’ existing collaboration context. Option C introduces public channels for acquisition work, which is inappropriate because the acquisition is confidential. Option D puts everything in a global workspace, which risks over-centralizing sensitive work and may not align with the departments’ existing workspaces. Multi-workspace channels preserve confidentiality while supporting cross-functional collaboration in place.

Reference topic: Grid Design — multi-workspace channels, confidential cross-functional collaboration, private channel design, and Enterprise Grid workspace architecture.

==========

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 answers are A, B, and E . A grid design executive summary should communicate the selected structural model in a way executives and project stakeholders can understand and approve. The first essential element is the recommended workspace structure and access level because that defines who can discover, request, join, or be invited to each workspace. Slack’s Enterprise organization documentation defines access levels such as Open, By Request, Invite Only, and Hidden, making access design a core part of grid architecture. Channel recommendations are also required because channels are where work happens; grid design is incomplete without guidance on how collaboration will be organized inside and across workspaces. Finally, the summary must include grid design benefits and considerations so the client understands the tradeoffs of the selected model. Training recommendations, user analytics, KPIs, and admin processes are important in the broader project, but they belong in enablement, success measurement, and governance deliverables rather than the core executive summary of the grid design.

Reference topic: Grid Design — workspace recommendations, access model, channel strategy alignment, benefits, and design considerations.