Salesforce Slack-Con-201 Practice Exam Questions & Answers

The correct answer is an automated welcome bot message that prompts the new employee to complete an introduction workflow, which is then automatically shared with the team. The client wants a warm onboarding experience where employees share fun and useful information with coworkers, and the key word is automated. Option A satisfies both requirements: it initiates the experience through Slack automatically and uses a workflow to collect and distribute the introduction consistently. Option B relies on managers to prompt the employee, which introduces inconsistency and is not fully automated. Option C depends on a manual manager message and asks the employee to post in a company-wide welcome channel, which may be too broad and less targeted than sharing with the employee's team. Option D provides a private welcome but fails to include the employee-sharing component the client requested. Workflow-based onboarding is stronger because it standardizes the experience, reduces manager workload, and makes the new hire's introduction visible in the right collaboration context.

Reference topic: Learning and Enablement --- onboarding workflows, automated welcome experiences, Workflow Builder use cases, new-hire enablement, and launch adoption.

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.

Reference topic: Policies and Settings --- Slack Connect DM permissions, default external collaboration behavior, guest restrictions, and Enterprise Grid policy review.

The correct answer is A. When a Slack Connect channel exists between a migrating workspace and the destination grid org, it is no longer truly an external Slack Connect relationship after the workspace becomes part of the same Enterprise Grid. The channel is converted into a multi-workspace channel. Because the channel is private on the migrating workspace, the safer and more restrictive privacy state is preserved post-migration, so it becomes a private multi-workspace channel. Option B is wrong because the channel spans the migrating workspace and the grid org, so it does not simply become a single-workspace channel. Option C is incorrect because after migration, the relationship is internal to the same Enterprise Grid rather than external Slack Connect. Option D is tempting because the channel is public on the grid org side, but preserving confidentiality requires honoring the private state. Migration planning must account for these channel-state changes so admins understand what users will see after the workspace joins the grid.

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.

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 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 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.