Slack-Con-201 Questions and Answers

The correct answer is C . In Enterprise Grid, SSO is managed at the organization level, so exceptions to the SSO requirement must be handled in org settings, not workspace settings. The client needs some members to continue logging in with a username and password, which means those members must be excluded from the SSO requirement. The answer also specifies uploading a CSV list, which is the scalable method for applying exclusions when multiple members are involved. Option A is incorrect because it uses the workspace settings dashboard and manual entry, which does not align with Enterprise Grid org-level SSO control. Option B is wrong because workspace admin settings are not the correct place for Enterprise Grid SSO exclusions. Option D correctly identifies org settings but uses manual addition; the tested recommendation is to upload a CSV list for the excluded users. The important consulting principle is that identity and authentication settings on Enterprise Grid are centralized at the org level.

Reference topic: Policies and Settings — Enterprise Grid SSO, org-level authentication controls, SSO exclusions, CSV user management, and login policy design.

==========

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 strongest answer is to run team syncs in channels using automated reminders. Slack’s project-management value comes from moving status communication into visible, searchable channels and reducing dependency on synchronous meetings. Automated reminders or scheduled messages help keep updates consistent without relying on a manager to manually chase people. This approach also improves transparency because team members can see updates in context, respond in threads, and preserve decision history in the channel. Option A keeps the process dependent on Zoom and manual reminders, which underuses Slack. Option C introduces a template but does not ensure visibility, automation, or channel-based collaboration. Option D may be useful if Jira is part of the team’s delivery workflow, but the question asks for the most effective Slack-native project management approach, not a tool-specific integration. Slack’s official automation guidance supports scheduled channel messages for recurring reminders, daily standups, and project updates.

Reference topic: Channel Strategy — project channels, recurring updates, async team syncs, transparency, and workflow automation.

==========

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 . After a workspace is migrated into Enterprise Grid, the existing workspace URL continues to function and directs users to the workspace now housed inside the Enterprise Grid organization. This matters because users may have bookmarks, desktop app references, saved links, browser history, integrations, or internal documentation that reference the original workspace URL. Telling users the URL will remain usable reduces confusion and prevents unnecessary support tickets after migration. Option B is wrong because after migration, the workspace is no longer operating as a separate original workspace outside the grid. Option C is wrong because the URL does not simply stop working as a normal migration outcome. Option D is wrong because Slack does not replace the workspace URL with a random new URL as part of the standard grid migration experience. Migration communications should explain login expectations, downtime, workspace availability, and continuity items such as the existing URL.

==========

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.

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 A. Hidden . The scenario is explicit: the merger and acquisition project is confidential, and the project team must work together in a non-public way. A hidden workspace is the strongest fit because it prevents general discovery of the workspace by the broader organization and limits awareness to invited or authorized members. Option B, Open, is completely inappropriate because it allows broad access. Option D, By request, would allow members to see that the workspace exists and request access, which does not meet the “non-public” requirement. Option C, Invite-only, sounds restrictive, but hidden is the better answer when even the existence of the workspace should not be broadly visible. For confidential M & A work, the consultant must design for privacy, controlled membership, and minimized information exposure. A hidden workspace provides the right access posture for sensitive strategic work where visibility itself could create risk.

==========

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.

==========

The correct answer is C . Org Admins on Enterprise Grid need a centralized view of adoption, activity, and usage trends across the organization. The org-level analytics dashboard is the primary administrative tool for monitoring whether Slack is driving value as the business grows. It helps admins understand membership, channel activity, message activity, and broader usage patterns that inform governance, enablement, and adoption decisions. Option A, Slack’s analytics Web APIs, can be useful for advanced reporting or custom analysis, but it is not the primary admin-facing tool for routine governance monitoring. Option B is incorrect because SCIM is related to identity provisioning and user lifecycle management, not Slack value measurement. Option D is too narrow; member-level analytics do not provide the org-wide governance view needed by an Org Admin. This question is testing the distinction between operational administration and analytics-led governance. For Enterprise Grid maturity, admins should use org-level analytics to identify adoption gaps, inactive areas, overgrown workspaces, and opportunities for targeted enablement.

==========

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 A . To evaluate Slack adoption by department and identify managers who can help nominate or develop internal champions, the client needs reliable organizational metadata in Slack. The cleanest way to achieve this is to map SCIM attributes such as dept and mgr to Slack profile fields for Department and Manager . This keeps the fields governed by the identity source rather than relying on users to manually type their own department or manager information. Option B is weak because manual updates create inconsistent, incomplete, and untrusted profile data. Option C uses overly specific or incorrect attribute naming for the tested scenario; the expected mapping is the standard department and manager-style SCIM attribute mapping into Slack profile fields. Option D is incomplete because simply creating custom fields does not define the actual SCIM attribute mapping. For adoption analysis, Slack profile data must be structured and dependable, otherwise department-level analytics and champion identification become unreliable.

==========

The correct components are target audience, objective, and delivery method . A rollout communication plan must define who the communication is for, what the communication is intended to accomplish, and how it will be delivered. The target audience matters because executives, admins, champions, managers, and end users need different information at different points in the rollout. The objective clarifies the purpose of the message, such as awareness, action, training registration, policy change, launch readiness, or reinforcement. The delivery method defines how the message reaches the audience, such as Slack announcements, email, live sessions, manager cascades, or help channels. Option A omits the objective, which is a serious gap because communication without a stated goal becomes generic broadcast messaging. Option C omits the audience, making the communication impossible to tailor. Option D omits the delivery method, leaving the plan incomplete. Channel setup recommendations may appear elsewhere in the launch plan, but they are not one of the core components of the communication plan itself.

Reference topic: Learning and Enablement — rollout communication planning, audience segmentation, communication objectives, delivery methods, and change-management messaging.

==========

The correct answer is C . The scenario has two major change-management variables: different communication habits and leadership visibility from both companies. Because one organization primarily uses email and the acquired company primarily uses Slack, the communication plan must customize the delivery method . A single channel of communication would miss part of the audience or fail to meet users where they already work. At the same time, both leadership teams need visibility and input, so the sender(s) of communication must also be customized. Communications may need to come from executives or leaders from both organizations to build credibility and reduce resistance during the transition. Option A is incomplete because sender alignment alone does not solve the email-versus-Slack delivery difference. Option B is incomplete because delivery method alone does not address stakeholder trust and leadership representation. Option D is weak because custom emojis are not a core communication-plan component for acquisition change management. The correct plan adjusts both sender and delivery method.

==========

The correct answer is B . The requirement points directly to asynchronous, easy-to-understand, regularly scheduled learning content. A #slack-tips channel is the best fit because it allows the client to post small, digestible enablement content over time, reaching employees where they already work. This supports continuous reinforcement rather than a one-time training event. Option A provides more live instruction, but the user explicitly needs asynchronous learning, not another scheduled class. Option C creates a static long-form asset, but a one-hour video is not ideal for ongoing, bite-sized learning and will likely have lower engagement. Option D, an internal Champions Network, is valuable for advocacy and peer support, but it does not directly satisfy the request for regularly scheduled learning content. A tips channel can include short posts, Help Center links, mini use cases, workflow examples, and reminders about best practices. It also creates a searchable internal knowledge stream that employees can revisit at their own pace.

Reference topic: Learning and Enablement — asynchronous enablement, continuous learning, Slack tips channel, reinforcement strategy, and scalable adoption support.

==========

The correct answer is D . For a security-conscious financial services firm, Slack 101 training must be shaped by the client’s actual policies and settings. Introductory training should not teach generic Slack behavior that conflicts with configured rules around channel creation, message retention, external sharing, app approvals, guest access, Slack Connect, file uploads, retention, or notification controls. Option A, Block Kit, is irrelevant for a basic end-user training session because Block Kit is used for app interface design, not normal Slack 101 usage. Option B and Option C are important for enterprise security architecture, but end users generally do not need deep training on the specific eDiscovery or DLP applications. What they do need is practical guidance on what they can and cannot do in Slack based on the organization’s configured controls. The learning plan must reflect the client’s compliance posture so users understand approved collaboration behavior from day one.

Reference topic: Learning and Enablement — Slack 101 customization, regulated-industry training, policies and settings alignment, secure collaboration behavior, and end-user readiness.

==========

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 D . The question asks for the most automated archive/unarchive request process. A channel workflow is the clear automation mechanism because it gives employees a structured request path instead of relying on free-form messages or direct admin intervention. In a well-designed support channel such as #plz-admin , users can open the channel workflows, select the archive/unarchive workflow, provide the required details, and route the request to the appropriate admin or approval process. Option A uses the wrong support-channel pattern and is only a manual message. Option B creates a private dependency on a workspace admin and does not scale. Option C is also manual and the channel name is malformed as #plz admin instead of a clean hyphenated Slack channel name. Option D uses the correct channel naming convention and applies Workflow Builder to standardize intake, reduce admin back-and-forth, and make the archive/unarchive process repeatable.

Reference topic: Channel Strategy — admin request channels, Workflow Builder automation, channel archive process, support-channel naming, and scalable user request management.

The correct answer is C . A small company with a lean process model and limited IT capacity should not design a support model that creates unnecessary ticket volume or constant manual monitoring. A search-first culture backed by self-serve resources is the best fit. This means users are encouraged to search Slack, consult internal help materials, review pinned or bookmarked resources, and use Slack Help Center links before escalating. Option A is risky because promising immediate response timelines creates support expectations the small IT team may not be able to meet. Option B may be useful later, but “various help channels” can fragment requests and increase overhead. Option D is also labor-intensive and conflicts with the client’s limited support capacity. The right support strategy should scale with the organization: provide clear documentation, searchable help content, FAQs, launch tips, and escalation instructions only when self-service does not resolve the issue. This keeps the user experience strong without overloading IT.

==========

The correct answer is B . After an Enterprise Grid migration, users may belong to different workspaces inside the same grid. A public channel is discoverable only to members who have access to the workspace where that channel exists, unless it is made available as a multi-workspace or org-wide channel. In this scenario, some users can find and join the training channel, while others cannot. That pattern strongly indicates the channel itself is public, but it lives in a workspace that not all attendees belong to. Option A is possible in isolated cases, but it would not explain a consistent split across attendees. Option C is irrelevant because Slack Connect is used for collaboration with external organizations, not internal training-channel discovery. Option D would prevent users from joining through search unless invited, but it would generally affect all attendees who were not invited. The training setup should either invite all participants or place the training channel in a workspace accessible to the full training audience.

==========

The best answer is Quarterly . Policies and settings should be reviewed on a predictable cadence because Slack governance is not a one-time configuration task. As user behavior, app usage, external collaboration, compliance requirements, and business structure change, the client must validate whether the current settings still support the intended operating model. Quarterly is frequent enough to identify drift before it becomes operational risk, but not so frequent that the review becomes administratively noisy. Monthly reviews are usually excessive unless the organization is in an active launch or remediation phase. Ad hoc reviews are reactive and create inconsistent governance. Annual reviews are too slow for a collaboration platform where workspace, channel, app, and Slack Connect usage can change rapidly. The Salesforce Slack Consultant domain structure treats Policies and Settings as a major exam area, reinforcing that governance controls must be designed, monitored, and adjusted throughout the lifecycle of the Slack program.

Reference topic: Policies and Settings — governance cadence, settings validation, risk control, and operating model alignment.

==========

The correct answer is B . The client is on Enterprise Grid and wants to change private-channel creation permissions across the grid, not only inside selected workspaces. That makes this an org-level policy decision. The appropriate path is org settings, organization policies, permissions, then the channel management policy for private channels. Option A is wrong because adjusting individual workspace settings would create inconsistent behavior across the grid and would not satisfy a grid-wide adoption policy. Option C is close but too imprecise; the tested location is organization policies under permissions, not simply “org settings, channel management.” Option D is invalid because members cannot change administrative channel-creation policies. From a governance standpoint, allowing everyone except guests to create private channels can reduce admin bottlenecks and increase adoption, but it must still be controlled centrally so the client maintains a consistent permission model across all Enterprise Grid workspaces.

==========