When providing your client with an executive summary of their selected grid design, which three key pieces of information should you include?
Answer : A, B, E
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.
You are a Slack Consultant helping a client on Enterprise Grid set up Slack Connect channels that will be used to collaborate with an external partner.
By default, who within your client's organization has the appropriate permissions to approve Slack Connect channel requests to work with the external partner?
Answer : B
The correct answer is B. On Enterprise Grid, Slack Connect governance is handled at the organization level unless the organization changes the default permissions. Approving requests to collaborate with external organizations is not merely a workspace-local activity because Slack Connect affects external collaboration, data exposure, compliance boundaries, and organization-wide security posture. Org Owners and Org Admins are the appropriate default roles because they have the administrative authority to manage external collaboration settings and approve cross-organization channel relationships. Option A is too narrow because Org Owners also have approval authority. Option C is also too narrow because Org Admins participate in this administrative control. Option D is incorrect because Workspace Admins and Workspace Owners operate at the workspace level and do not, by default, own the enterprise-wide approval boundary for Slack Connect channel requests. The tested principle is that external collaboration on Enterprise Grid must be governed through centralized org-level roles unless the policy is intentionally modified.
Reference topic: Policies and Settings --- Slack Connect permissions, Enterprise Grid external collaboration controls, Org Owner/Admin authority, and approval governance.
==========
Question 3
You are a Slack consultant helping a client on Enterprise Grid set up Slack Connect channels that will be used to collaborate with external partners.
Unless modified from the default settings, who can send and accept invitations to direct message (DM) people outside the client's organization on Enterprise Grid?
Answer : A
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.
Your client wants to add an additional layer of security for their data in Slack. They enquired about Slack's Enterprise Key Management (EKM) product.
What guidance can you provide on how to proceed with enabling EKM?
Answer : C
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.
==========
Question 5
Your client is considering pre-approving certain apps for their Enterprise Grid, and asks you to describe the benefits of using pre-approved apps.
Which two benefits would you share about pre-approving apps?
Answer : B, D
The correct answers are B and D. Pre-approving apps is an app governance mechanism that reduces administrative friction while maintaining control. When app approval is enabled, users may need approval before installing apps; however, apps that are already approved can be installed and used without creating a new approval request. That directly reduces the request queue for Slack admins and gives employees faster access to approved productivity tools. Option B is correct because the approval workload decreases when commonly needed apps are already approved. Option D is correct because pre-approved apps can be installed without submitting a separate app request. Option A describes support or troubleshooting behavior, not an app approval benefit. Option C describes Workflow Builder capabilities, not the result of pre-approving apps. Option E invents a ''walkthrough wizard'' concept that is not the control being tested. Slack's official app approval documentation states that owners can pre-approve or restrict apps, and members can install apps approved by a Workspace Owner.
Reference topic: Policies and Settings --- app approval, app governance, pre-approved apps, and admin workload reduction.
==========
Question 6
What information learned during discovery will be most helpful when creating a grid design recommendation?
Answer : B
The correct answer is B. Grid design should be based on how work and information naturally flow across the organization. The consultant needs to understand whether teams collaborate mostly by function, geography, department, business unit, external partnership, confidentiality level, project type, or cross-functional initiative. That discovery input directly informs whether the client needs one global workspace, multiple functional workspaces, a social workspace, an external workspace, restricted workspaces, or multi-workspace channels. Option A is useful for app and integration planning, but app usage does not define the core workspace architecture. Option C may matter if the client has active or expected acquisitions, but it is too narrow to be the most generally helpful grid-design input. Option D can provide insight into collaboration culture and security posture, but public/private channel ratios alone do not explain how information should be structured across workspaces. The strongest grid design recommendation is evidence-based and aligned to real information-sharing patterns.
==========
Question 7
Your client wants to create an IT Support help channel and asks you to advise on the best option using Slack channel naming settings and best practices.
Which channel name do you select?
Answer : D
The correct channel name is #help-it. Slack channel naming best practices favor names that are lowercase, simple, predictable, searchable, and aligned to a clear naming convention. A help channel should use a recognizable prefix such as help- followed by the function or team receiving the request. This makes the channel easy for users to find and reinforces consistent channel taxonomy across the workspace or Enterprise Grid. Option A uses an underscore, which is less aligned with common Slack naming conventions where hyphens are typically used for readability. Option B includes an exclamation mark, which is not appropriate for clean channel naming and creates unnecessary noise. Option C uses uppercase letters, which conflicts with the best-practice preference for lowercase, readable channel names. Option D is concise, descriptive, and scalable because the same pattern can be extended to other support channels such as #help-hr, #help-finance, or #help-security.
All Official Question Types