Salesforce-Slack-Administrator Practice Test Questions

Explanation:

The best way to manage time zone differences while respecting boundaries is to promote Scheduled Send. This feature enables users to compose messages whenever they want but deliver them at a later time — during the recipient’s working hours. It reduces interruptions, encourages empathy, and creates a more thoughtful digital HQ culture.

✅ Correct Answer:

B. Enable members to use the Scheduled Send feature so that messages can be sent during shared working hours.
Scheduled Send allows Slack users to write a message at any time and choose a future time for it to be delivered. This is especially helpful in globally distributed teams where working hours don't overlap. It promotes asynchronous work while maintaining respect for work-life boundaries. By rolling out Scheduled Send as part of digital HQ best practices, Org Admins can help avoid off-hours pings, reduce distraction fatigue, and demonstrate care for employees’ local schedules. This feature supports Slack’s philosophy of thoughtful collaboration, enabling flexibility without disrupting others’ routines.

❌ Incorrect Answers:

A. Enable members to set their profile status to Away whenever they are not online.
Setting a Slack status to "Away" only provides a visual cue about someone's availability. However, it does not suppress notifications, nor does it influence message delivery timing. Members will still receive notifications unless they manually enable Do Not Disturb (DND) mode. This approach relies on manual user behavior and lacks enforcement or automation. In a global organization, assuming every team member will routinely set their status is impractical and unreliable.

C. Enable members to view a recipient's local time within their profile before sending a message.
While it is true that Slack shows the recipient's local time on their profile, this is passive information and doesn’t enforce thoughtful sending. It requires the sender to remember to check the time and then manually delay or schedule the message. This approach is not scalable across a global company and still leaves room for human error. It also does not help people who compose messages quickly or in bulk without checking profiles.

D. Enable members to set reminders for themselves to send the message during shared working hours.
Setting reminders is a manual and inefficient workaround. It places the burden on users to remember to re-send the message at an appropriate time. Unlike Scheduled Send, reminders don’t automate the actual sending process. This adds cognitive load and creates room for error or delays, especially when handling time-sensitive information across global teams.

📘 Reference:
Slack Help Center – Schedule a Message
Slack Help Center – Manage Notifications

Explanation:

Teara’s goal is to shift collaboration from private DMs to public or private channels. To do this, she must increase transparency and trust in channel communication. Setting channel retention to "Keep Everything" ensures historical context is preserved, while limiting direct message retention encourages users to stop relying on DMs for key decisions. Enabling open channel creation empowers teams to start discussions without bottlenecks.

✅ Correct Answer:

D. Changing the workspace’s public channel message retention and deletion policy to "Keep Everything", changing the direct message retention and deletion policy to delete messages after 1 day, and allowing everyone to create channels
This option aligns with Slack’s best practices for driving work into channels. By keeping all messages in public channels, users have the confidence that discussions won’t disappear. Simultaneously, setting direct messages to auto-delete after 1 day discourages over-reliance on private, fragmented communication. Finally, empowering all users to create channels reduces the friction of having to request permission, which increases organic collaboration and shifts conversations into open spaces. These settings together foster a more transparent, efficient, and searchable workspace culture.

❌ Incorrect Answers:

A. Changing the workspace’s message retention and deletion policy for all channels and direct messages to "Keep Everything" and allowing everyone to create channels
While this option partially addresses the issue by retaining all messages, it fails to discourage private communication. Keeping DM history encourages continued use of DMs for discussions that should happen in shared spaces. Without a clear signal (such as auto-deletion in DMs), users have little motivation to shift behavior. The key is to reduce reliance on DMs while making channels the better alternative.

B. Sending an announcement in the #general channel notifying everyone to move conversations to channels and to DM Teara if you need a channel created
Sending an announcement is helpful as a communication strategy, but it does not address the root issue — the retention policies and permissions themselves. Moreover, requiring users to DM Teara to create a channel adds friction and delays, which discourages adoption of channels. Behavioral nudges (like deleting DMs automatically) paired with structural changes (like enabling everyone to create channels) are more effective in driving long-term change.

C. Changing the workspace’s public channel message retention and deletion policy to "Keep Everything", changing the direct message retention and deletion policy to delete messages after 1 day, and restricting the creation of channels to Owners only
This configuration sends mixed signals. While it correctly promotes transparency in public channels and discourages DMs by auto-deleting them, restricting channel creation to Owners creates a bottleneck. Users may revert to DMs or abandon collaboration altogether if creating a new space requires jumping through administrative hoops. A more scalable and inclusive approach is to let users initiate channels when needed.

📘 Reference:
✔️ Slack Help Center: data retention in Slack
✔️ Slack Best Practices: Shift from DMs to Channels
✔️ Slack Admin Guide: Manage who can create channels

Explanation:

As hiring scales, Nicole needs a scalable, automated onboarding solution. Slack’s Workflow Builder enables custom workflows that can greet new members when they join specific channels and share onboarding materials proactively. This reduces manual workload and ensures consistency in messaging while preventing inappropriate channel usage.

✅ Correct Answer:
D. Use Workflow Builder to welcome teammates to channels with automatic onboarding messages, including a link to "How to use Slack" guides.
Workflow Builder allows Nicole to create an onboarding workflow that automatically triggers when someone joins a specific channel. She can include a friendly welcome message, a link to a "How to use Slack" guide, and other key onboarding resources. This proactive automation ensures new hires are immediately guided with the right information without needing to rely on memory or manual posts. It also reinforces channel purpose and etiquette — reducing the chances that new hires will accidentally post in announcement-only channels. As hiring increases, this automation scales effortlessly with the organization’s growth and reduces Nicole’s manual workload.

❌ Incorrect Answers:
A. Create a "How to use Slack guide" and post it in all of the team-specific channels so that the new hires see it.
While this helps disseminate information, it’s manual and repetitive. Nicole would need to continuously repost in every team-specific channel for each new hire, which doesn’t scale well with rapid onboarding. It also relies on users finding the post amid other content. Compared to Workflow Builder, this approach lacks automation, personalization, and real-time engagement when users join a channel.

B. Create a custom Slackbot response that welcomes teammates to channels when the words "new hire" are used in Slack.
Slackbot responses only work when specific keywords are typed in a message. This approach is reactive and not reliable — new hires might not trigger the keyword or may never see the response if they don’t mention “new hire.” It also doesn’t prevent them from posting in the wrong channels. This is not a structured or automated way to deliver onboarding content compared to Workflow Builder’s trigger-based messages.

C. Email a "How to use Slack guide" to new hires before they start.
Emailing a guide in advance may provide early instruction, but it’s disconnected from the Slack experience and easy to overlook. Many new hires won’t read pre-start emails in detail, and Slack usage is learned best in context. This method also lacks scalability and automation — Nicole would still need to manually send emails each time. Additionally, it does not prevent misposting or reinforce expectations inside Slack itself.

📘 Reference:
Slack Help Center: Guide to Workflow Builder
Slack Blog: 4 automated workflows for onboarding new hires
Slack Help: Welcome new members with Workflow Builder

Explanation:

In Slack Enterprise Grid, Org Admins can manage all members across workspaces from the organization-level analytics dashboard. Exporting member data from this dashboard provides a centralized, efficient way to audit all guest accounts across the Grid organization without needing to visit each workspace individually.

✅ Correct Answer:

C. Export the data from the Members section of the org analytics dashboard.
This is the most efficient method because the Org-level analytics dashboard provides a complete, consolidated view of all members, including Single-Channel Guests and Multi-Channel Guests, across every workspace within the Enterprise Grid. From this section, Org Admins can export a .CSV file containing user types, roles, and access levels — making it simple to filter out guest accounts for audit purposes. This method eliminates redundancy, centralizes access, and aligns with Enterprise Grid’s architecture, which is designed to manage users at the org level instead of the workspace level.

❌ Incorrect Answers:

A. Gather the data from the Manage Members section of each workspace's administration dashboard.
While this method would eventually yield the necessary data, it is inefficient and error-prone. You would need to repeat the audit manually across all workspaces (in this case, two — but potentially many more). It also does not give you a unified view of guest accounts across the organization and can lead to duplication or oversight, especially with Multi-Channel Guests who may appear in multiple workspaces.

B. Open a ticket with Slack's Customer Experience team to see which guest accounts are active.
This approach is unnecessarily time-consuming and involves external support for something Org Admins already have the permissions and tools to perform themselves. Slack's admin tools are specifically designed to empower internal admins to manage users efficiently without relying on support tickets. Using Slack’s built-in org analytics is faster, more private, and scalable.

D. Export the data using the Export Data tab in the org administration dashboard.
The “Export Data” tab typically refers to data exports for messages and files, not user metadata. This functionality is intended for legal compliance and audit use cases (e.g., message history in channels or DMs), and it does not provide structured member or guest account reports. It also often requires special permissions or approval, depending on the export type. It’s not the correct tool for auditing guest users.

📘 Reference:
Slack Help Center: View analytics for your Enterprise Grid organization
Slack Help: Manage members in an Enterprise Grid org
Slack Enterprise Grid Overview

Explanation:

To ensure confidentiality and centralization, the HR Director should use a private, org-wide channel. This ensures sensitive HR and recruiting conversations remain private but accessible across multiple workspaces (i.e., Enterprise Grid). This balances the need for secure access and organization-wide collaboration.

✅ Correct Answer:

B. Create an org-wide private channel for recruiting and hiring, and add all hiring managers in the organization.
In an Enterprise Grid environment, an org-wide private channel allows members from multiple workspaces (like HR and other departments) to securely collaborate while maintaining privacy. HR-related topics — including recruiting decisions and policy discussions — often contain sensitive personal or organizational information. A private org-wide channel ensures that only approved hiring managers and HR personnel can view or participate in the conversation, while still allowing cross-workspace access without duplicating efforts or risking visibility to unintended audiences. This configuration supports centralization, confidentiality, and efficient HR collaboration at scale.

❌ Incorrect Answers:

A. Create an org-wide public channel for recruiting and hiring, and add all hiring managers in the organization.
This option allows for org-wide access but fails to protect sensitive HR information. Recruiting and hiring conversations may include confidential candidate evaluations, interview feedback, or internal HR strategies — none of which should be visible to the full organization. Public channels are accessible by all workspace members by default, so this option would violate data privacy best practices and Slack's recommendations for secure information sharing.

C. Create a private channel in the HR workspace, and add all hiring managers in the organization.
While this ensures privacy, it limits access to only users who are members of the HR workspace. Since most hiring managers belong to other workspaces (e.g., department-specific), they may not have access unless you manually grant them workspace membership. This makes user management harder, introduces access friction, and breaks the Enterprise Grid principle of connecting workspaces through org-wide channels.

D. Create a public channel in the HR workspace, and add all hiring managers in the organization.
Similar to option A, this method exposes sensitive HR discussions to anyone in the HR workspace and could be discoverable by others if mistakenly joined. Public channels should be used for broadly applicable announcements, not private or regulated information. Additionally, not all hiring managers may be part of the HR workspace, so access gaps could occur, making this setup both insecure and inconsistent.

📘 Reference:
Slack Help: About private channels
Slack Help: Channel management in Enterprise Grid
Slack Enterprise Grid Overview

Explanation:

To effectively communicate across the entire organization, you should use a default org-wide announcement channel and limit posting permissions to admins or designated roles. This ensures clarity, reduces clutter, and makes messages reliable and visible to all users without overwhelming noise.

✅ Correct Answer:

A. Create a default org-wide channel called #announcements, and post your newsletter in this channel.
Creating a default channel like #announcements ensures that every user in every workspace is automatically added, including those who join in the future. Slack Enterprise Grid allows Org Owners to restrict posting in specific channels using channel management settings, so only Org Admins or designated roles can publish content in the channel. This allows newsletters and critical information to be shared in a trusted, centralized location where all users know to look for updates. Using this approach promotes clarity, increases engagement with important announcements, and maintains consistent delivery across the entire Slack organization.

❌ Incorrect Answers:

B. Send your newsletter to your team's channel and then copy/paste the link to your message to each team channel in your organization.
This method is highly manual and inefficient, especially in a large organization. It introduces inconsistencies, increases the chance of mistakes or missed updates, and causes redundancy. It also fragments communication by requiring users to click through to find the original message rather than having a consistent source of truth. This solution does not scale with an Enterprise Grid setup, where centralized communication is critical.

C. Send your newsletter in all of your department-specific channels to maximize visibility.
Posting in multiple department channels creates information overload and inconsistency. Team channels are typically used for department-level discussion, not org-wide announcements. Important action items may get buried in unrelated conversations, and the duplication of messages can create confusion about where to reply or seek clarification. Unlike a centralized announcement channel, this strategy lacks uniform visibility and posting control.

D. Send your newsletter to your organization’s #general channel, and use the @channel notification.
Using the #general channel for announcements is not reliable in Slack Enterprise Grid, where #general is workspace-specific — meaning each workspace has its own version. A message sent to the #general channel of one workspace won’t reach members in others unless they are part of that specific workspace. Additionally, frequent use of @channel can lead to notification fatigue. Instead, creating a custom org-wide default channel like #announcements ensures consistent and targeted communication.

📘 Reference:
Slack Help: Manage default channels for new members
Slack Help: Set posting permissions in a channel
Slack Enterprise Grid: Channels Overview

Explanation:

The best approach is to remove the sensitive content quickly and use Slack's Audit Logs API to trace download events. When integrated with a DLP (Data Loss Prevention) tool, Slack can monitor, control, and automate actions like file removal, while the Audit Logs API provides visibility into sensitive activity — including file access.

✅ Correct Answer:

A. Using an integrated Data Loss Prevention (DLP) solution, delete the file, and then review the Audit Logs API to see who downloaded the file.
Slack Enterprise Grid supports integration with leading DLP platforms to help manage compliance and mitigate risk. These tools can automate detection and response actions — such as deleting a confidential file posted in a public channel. Once the file is removed, Slack’s Audit Logs API enables Org Owners and Admins to track user actions, including file access and downloads. This ensures that Amy can act swiftly to minimize exposure and maintain visibility into the incident. This option provides the necessary control, security, and traceability that Enterprise-grade compliance requires.

❌ Incorrect Answers:

B. Using MDM, disable file downloads and then use session management to see who was logged in and downloaded the file.
Mobile Device Management (MDM) primarily manages mobile device access and session behavior, but does not provide visibility into specific file downloads. Session management can show who was logged in but not whether they accessed or downloaded a specific file. Moreover, disabling downloads reactively via MDM would not help in identifying who already downloaded the file before it was removed. It also does not offer file removal or automated compliance action capabilities like DLP tools.

C. Using a third-party eDiscovery app, delete the file and use data exports to determine who downloaded the file.
eDiscovery apps are designed for legal compliance and long-term data archiving. While they may allow message/file search and export, they do not track download activity or provide real-time file deletion. Additionally, Slack’s standard data exports (especially in Enterprise Grid) do not include file access logs. This approach is inefficient for rapid response and lacks the auditing granularity required to identify who downloaded the file.

D. Using Slack Enterprise Key Management (EKM), revoke key access for the file, and review the EKM logs to see who downloaded the file.
Slack EKM lets organizations control their encryption keys, but EKM logs only track when data is accessed and decrypted, not when a file is downloaded or who downloaded it. It does not offer the ability to delete content or prevent file sharing retroactively. EKM is not a file management or content moderation tool — it's an encryption and access control mechanism. Therefore, it cannot fulfill the requirements in this scenario.

📘 Reference:
Slack Help: Use Slack with DLP tools
Slack Developer Docs: Audit Logs API
Slack Enterprise Grid Security
Slack EKM Overview

Explanation:

To ensure consistent communication across all current and future workspaces, the most scalable and efficient method is to create an org-wide channel. This allows Enterprise Grid administrators to broadcast messages across the entire organization regardless of the number of workspaces, ensuring everyone sees the training information.

✅ Correct Answer:

A. Create an org-wide channel dedicated to company trainings.
In Enterprise Grid, org-wide channels are a powerful tool to distribute information to all users across every workspace, both now and in the future. When you create an org-wide channel, all current members are added automatically, and new members (or newly created workspaces) are also joined automatically. This eliminates the need to manage multiple channels across different workspaces. For company-wide training, this ensures everyone receives the announcement without relying on individual admins to communicate locally. It is the most centralized and reliable option for critical information dissemination.

❌ Incorrect Answers:

B. Create a multi-workspace channel for training that exists in each workspace.
While multi-workspace channels do span more than one workspace, they must be manually configured and maintained. They do not automatically include all future workspaces or members. Additionally, they require administrative overhead to ensure they stay in sync as your org scales, making them less effective than an org-wide channel for broad announcements.

C. Have each Workspace Admin post in the correct public training channel.
This method lacks consistency and central control. It depends on each Workspace Admin to remember to share training announcements and do so correctly and on time. This introduces variability, risk of missed communication, and additional coordination overhead. It’s not scalable or reliable for a growing organization.

D. Create a Slack Connect channel dedicated to company trainings.
Slack Connect is designed for cross-company collaboration, not internal communications. It enables you to connect with external organizations, vendors, or partners. It cannot be used to span multiple internal workspaces within your Enterprise Grid org. Using Slack Connect for internal training announcements would be inappropriate and ineffective.

📘 Reference:
Slack Help: About org-wide channels
Slack Enterprise Grid: Admin Guide
Slack: Channels in Enterprise Grid

Explanation:

Slack provides guest account types to help organizations securely collaborate with external individuals without giving them full access to internal communications. Since the contractor needs access to multiple project channels, a Multi-Channel Guest account is the most appropriate option. This maintains security and control while enabling collaboration.

✅ Correct Answer:

A. Multi-Channel Guest with access to all relevant project channels
Slack Enterprise Grid supports Multi-Channel Guest accounts, which are designed for external collaborators who need to participate in more than one channel. This is ideal for a contractor who’s helping multiple teams, as it allows them to access only the channels they need — nothing more. Admins can control their channel access, set expiration dates for their membership, and manage their visibility across workspaces. This option ensures compliance with company policies, minimizes security risk, and supports seamless collaboration for the duration of the project.

❌ Incorrect Answers:

B. Slack Connect direct message (DM) between the contractor and project lead
Slack Connect DMs are suitable for quick communication with someone from another Slack organization, but the contractor does not have Slack, so they can’t participate in Slack Connect. Also, DMs don’t support collaboration across multiple teams and channels. It’s too limited for the described use case.

C. Single-Channel Guest with access to one project channel
Single-Channel Guest accounts are limited to just one channel. This is not appropriate when a contractor needs to work with multiple teams and participate in various channels across the marketing workspace. Assigning them as a Single-Channel Guest would hinder productivity and require creating multiple accounts to span multiple channels, which is not scalable or manageable.

D. Full member with access to the marketing workspace
This option gives the contractor excessive access. Full members can browse all public channels within a workspace and may inadvertently access sensitive or unrelated information. Since the contractor is external, granting full membership would violate security best practices. Slack strongly recommends using guest roles for external collaborators to maintain compliance and reduce risk.

📘 Reference:
Slack Help: Types of Slack accounts
Slack Help: Manage Slack Connect and guest accounts
Slack Enterprise Grid: User provisioning

Explanation:

Slack Connect is specifically designed to enable secure, scalable communication with external organizations. It allows users from different companies to collaborate in shared channels — without giving them guest access or requiring internal provisioning. Since this is a long-term collaboration with multiple users and channels involved, Slack Connect provides flexibility, centralized security controls, and seamless access.

✅ Correct Answer:

B. Advise the employee to initiate one or more Slack Connect channels to collaborate with the external organization. The external organization can set up a free Slack instance if they are not already using Slack.
Slack Connect enables organizations to securely communicate with partners, vendors, or clients — each side maintains control over its own users. The external company can participate in shared channels using their own Slack instance (even a free plan), ensuring role-based access, SSO security, and compliance auditing remain intact for both parties. It scales easily, supports multiple users, and avoids the administrative overhead of managing external guest accounts in your internal workspace.

❌ Incorrect Answers:

A. Approve the employee's request, then invite the external users to your workspace as Multi-Channel Guests with a 12-month expiration date.
While Multi-Channel Guest access allows some flexibility, it is intended for individual collaborators, not entire teams or organizations. Provisioning 15 external guests introduces security risks and admin overhead. You lose visibility and control on how the guest users collaborate, and they would exist within your internal Slack instance, which is not recommended for large-scale external engagements.

C. Advise the employee to request the external users be added to your identity provider (IdP) so they can authenticate to your workspace with SAME single sign-on (SSO).
This suggestion is inappropriate for external collaborators. Adding users to your internal IdP means treating them like full internal employees, which poses serious compliance, security, and privacy issues. It violates best practices and exposes internal systems to external identities.

D. Advise the employee to set up a separate Slack workspace that is jointly owned by both organizations.
Creating a new shared workspace is complex and unnecessary. It lacks the centralized security features of Enterprise Grid and Slack Connect. Plus, managing a jointly owned Slack workspace introduces governance issues, versioning discrepancies, and redundant effort. Slack Connect is purpose-built for cross-company work and eliminates the need for setting up new shared environments.

📘 Reference:
Slack Help: Slack Connect Overview
Slack Help: Share a channel with a partner organization
Slack Blog: Why Slack Connect is better than email