The best recommendation is B . For daily Agile syncs in a remote environment, Slack should reduce repetitive manual coordination and move routine updates into the channel where the team already collaborates. A Workflow Builder template can automatically prompt team members to provide updates at the right time, standardize the format of responses, and keep progress visible to the whole team. This is more scalable and more productive than relying on a manager to ask for updates manually. Option A is directionally useful, but it lacks automation and consistency. Option C may be useful if the team already has a project-management tool that should be integrated, but the question asks for a Slack feature that improves the sync process itself. Option D keeps the team in a synchronous meeting pattern and does not solve the productivity problem as effectively as automated asynchronous updates. Workflow Builder is the strongest Slack-native answer because it supports repeatable, channel-based Agile communication.

Reference topic: Channel Strategy — Agile standups, Workflow Builder, asynchronous updates, project channels, and remote team productivity.

==========

The correct answer is A . Admin enablement must be tailored to the actual roles, permissions, and governance model configured for the client. If Workspace Admins do not have permission to approve app requests, then app approval content cannot be delivered as if those admins can perform that task. The proper consultant action is to consult with the learning lead and decide whether app approvals should be covered conceptually, excluded, or redirected to the correct audience such as Org Owners or Org Admins. Option B is weak because it delivers generic content that does not match the client’s configured permissions and may create confusion. Option C is too aggressive because the training audience should not be changed without validating the learning plan and stakeholder expectations. Option D is outside the enablement role; the consultant should not push a configuration change merely to match standard training material. The curriculum must follow the client’s operating model, not the other way around.

Reference topic: Learning and Enablement — role-based admin training, permission-aware curriculum design, stakeholder alignment, and Admin Essentials customization.

==========

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 recommendation is Monthly . Guest and channel cleanup is an operational governance activity, not a one-time launch task. Slack environments evolve quickly: projects end, external partners change, guest access expires, channels become inactive, and sensitive collaboration spaces may no longer require the same membership. A monthly cleanup cadence is frequent enough to reduce access risk and channel clutter without creating excessive administrative burden. Option A is weak because ad hoc cleanup is reactive and usually happens only after a problem occurs. Option B may be too frequent for most organizations and can create unnecessary admin overhead unless the environment is unusually high-risk. Option D is not frequent enough; annual reviews allow stale guest access and unused channels to accumulate for too long. The point of guest and channel cleanup is to keep collaboration intentional, secure, and manageable. This cadence should be owned through the governance structure and executed by the appropriate admin or owner roles.

Reference topic: Governance Structure (Owner and Admin Roles) — operational governance cadence, guest lifecycle management, channel cleanup, and administrative accountability.

==========

The correct answer is that eDiscovery applications require read access, while DLP applications require both read and write access. The difference comes from the purpose of each control. eDiscovery tools are used by legal, compliance, or security teams to retrieve and preserve Slack data for review, investigation, audit, or litigation support. Their core function is to access content for discovery, so read access is sufficient. DLP tools are different because they inspect content for sensitive information and may need to act on policy violations. That action can include flagging, quarantining, deleting, redacting, or otherwise enforcing rules on messages or files. Because of this enforcement role, DLP integrations require broader read and write capability. Option A is too broad because eDiscovery does not require write access. Option B incorrectly says eDiscovery needs create access. Option C understates DLP’s access by describing create and update rather than the broader read/write requirement.

Reference topic: Policies and Settings — Enterprise Grid security integrations, eDiscovery access model, DLP enforcement, compliance applications, and data protection controls.

==========

The correct answer is C . Slack channel strategy should reflect how work actually happens, and organic channel creation is a core part of that model. Channels are most effective when teams create them around real projects, decisions, customers, functions, incidents, communities, or workflows instead of waiting for admins to centrally manufacture every collaboration space. Option A is too loose because “customize their own channels” without strategy can lead to inconsistency and channel sprawl. Option B is too restrictive; forcing admins to create all project channels slows collaboration and turns Slack into a ticket-driven workspace instead of a dynamic work platform. Option D has some value because standard channels and prefixes can model good behavior, but it does not answer the broader question of whether users should be allowed to create channels. The best practice is not uncontrolled chaos or admin-only creation; it is user-driven, authentic channel creation supported by clear naming conventions, channel purpose guidance, and governance.

Reference topic: Channel Strategy — organic channel creation, channel governance, naming conventions, user empowerment, and scalable collaboration design.

==========

The correct recommendation is to add the custom profile field directly from the org admin dashboard and publish the change. The requirement is simple: all members should be able to add their favorite dessert in their Slack profile. This is not an identity-provider-driven attribute and does not require SCIM provisioning. SCIM-managed fields are appropriate for controlled identity attributes such as title, department, manager, or other directory-owned values that should be synchronized from the identity provider. “Favorite Dessert” is a user profile enrichment field, not a controlled identity field. Option A is incorrect because updating from SCIM would make the field dependent on an external identity source. Option B is incorrect because “update from API” is not the right administrative setup for this ordinary profile field use case. Option C starts in the wrong place because the field does not need to originate in the IDP. Option D correctly uses Slack profile configuration at the org level and publishes the field so it becomes available to members.

Reference topic: Policies and Settings — profile configuration, custom profile fields, SCIM-managed fields, and org-level profile governance.

==========

The correct answer is A . The attendee has a broad, self-paced learning need and does not have a specific issue or admin-level objective. The Slack Help Center is the best recommendation because it provides official, searchable, user-friendly learning material across Slack basics, messages, channels, notifications, huddles, files, search, accessibility, workflows, and workspace usage. Option B is not appropriate because the help desk should be used for support issues, access problems, or organization-specific troubleshooting, not general open-ended learning. Option C is too advanced and misaligned because the Slack Admin Certification Prep Course is for administrative and certification readiness, not basic end-user exploration. Option D is also inefficient because Slack Admins should not become the default route for general self-paced learning questions. The correct enablement model teaches users where to find official resources so they can continue learning independently after training. This scales better and prevents unnecessary support load on admins and IT teams.

Reference topic: Learning and Enablement — self-paced learning, Slack Help Center, end-user resources, scalable support behavior, and post-training enablement.

==========

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 best answer is B because it captures both major discovery themes: stronger external partnerships and stronger internal culture through cross-functional collaboration. A good Slack vision statement should be concise, outcome-oriented, and aligned to the client’s stated business goals. “Build deeper connections” maps directly to the client’s desire to improve employee culture and external partnership strength, while “single global collaboration platform” aligns to the Enterprise Grid purchase and cross-functional operating model. Option A is generic vendor-language and does not reflect the client’s specific goals. Option C focuses heavily on external communication security and business scale, but it misses the employee culture and cross-functional collaboration requirement. Option D introduces an unsupported metric, “expedite sales cycle time by 50%,” which was not stated in discovery; a consultant should not invent quantified outcomes unless the client has validated them. The correct vision statement must synthesize discovery inputs without overreaching.

Reference topic: Discovery — vision statement development, business-outcome alignment, external collaboration goals, culture goals, and Enterprise Grid value framing.

==========