Explanation:

To balance retaining important information while limiting retention for less critical channels, keep the default retention settings and set a one-month retention policy for channels with less important information (Option B). This approach ensures critical data is preserved by default while allowing targeted deletion for specific channels, aligning with the Business+ plan’s capabilities.

✅ B) Keep the default retention settings, but set a message retention policy of one month for channels with less important information.
On the Slack Business+ plan, default retention settings typically keep messages indefinitely, ensuring important information remains searchable. Setting a one-month retention policy for specific channels with less critical data allows the Workspace Owner to customize retention without affecting other channels. This approach leverages Slack’s channel-specific retention settings, available on Business+, to balance compliance and storage needs. It’s efficient, scalable, and aligns with the Salesforce Certified Slack Administrator Exam’s focus on managing data retention policies effectively while prioritizing user access to critical information.

Incorrect Answers:

❌ A) Set your global message retention policies for one month, and adjust retention settings for important channels to keep everything.
Setting a global one-month retention policy deletes messages across all channels by default, risking loss of critical data. Adjusting settings for important channels to keep everything is possible but requires more effort to identify and configure multiple channels, making it less efficient than targeting only less critical channels.

❌ C) Set the retention policy for public channels to keep all messages and allow members to determine how long they'd like to keep messages in private channels.
Slack’s Business+ plan doesn’t allow members to set retention policies for private channels; only admins can configure retention. This option is impractical and misaligns with Slack’s administrative controls, which centralize retention settings for compliance.

❌ D) Set the retention policy for private channels to keep everything, and set the retention policy for public channels to one month.
This approach incorrectly prioritizes private channels for indefinite retention while limiting public channels, which may contain critical information. It doesn’t align with the need to keep important data searchable across both channel types and is less flexible than channel-specific settings.

Reference:
Slack Help Center: Set message and file retention policies
Salesforce Trailhead: Slack Enterprise Grid Security

Explanation:

To set up an effective app-approval process, turn on app approval to restrict installations to pre-approved apps (Option D) and send notifications to a specific channel for app managers to review (Option E). These actions leverage Slack’s built-in controls for centralized app management and streamlined approvals, ensuring security and efficiency.

Correct Answers:

D) Turn on app approval so members can only install apps that have been pre-approved.
Enabling app approval in the Admin Dashboard restricts members to installing only pre-approved apps, ensuring security and compliance. This feature, available on Business+ and Enterprise Grid plans, allows Workspace Owners to review and approve apps based on organizational needs, preventing unauthorized installations. It’s a core component of Slack’s app management system and a key focus of the Salesforce Certified Slack Administrator Exam, as it centralizes control and mitigates risks from unvetted apps.

E) Send all notifications to a specific channel that includes all app managers for app approval.
Routing app approval notifications to a dedicated channel (e.g., #app-approvals) ensures all app managers are informed and can collaborate on reviews. This streamlines the approval process, improves visibility, and supports governance by keeping requests organized. It aligns with Slack’s best practices for managing app requests efficiently, as emphasized in the exam.

Incorrect Answers:

A) Instruct app requestors to post a business justification in #help-admins when requesting apps.
While a business justification is useful, manually posting in a channel like #help-admins is inefficient and lacks formal structure. Slack’s built-in app approval workflow automatically collects justifications, making this approach redundant and less scalable for managing requests.

B) Restrict apps that aren't already used by your organization.
Slack doesn’t have a setting to restrict apps based on prior use. App restrictions are managed through pre-approval settings or by limiting app sources, not by usage history. This option is impractical and misaligned with Slack’s app management capabilities.

C) Send all app approval requests to app managers in a Slackbot message.
Sending requests via Slackbot messages to individual app managers is disorganized and lacks transparency. It doesn’t support collaborative review or tracking, unlike a dedicated channel, making it less effective for managing the approval process.

Reference:
Slack Help Center: Manage app settings and permissions
Salesforce Trailhead: Slack App Management

Explanation:

To add consultants as Multi-Channel Guests on the Enterprise Grid plan, the marketing team should invite them through the workspace drop-down menu and route approvals to a dedicated channel for admin approval (Option A). This leverages Slack’s guest invitation workflow, ensuring a structured and trackable process. Other methods are less formal or misaligned with guest access protocols.

✅ A) Invite consultants through the workspace drop-down menu, and route approvals to a dedicated channel for admin approval.
On the Enterprise Grid plan, inviting Multi-Channel Guests via the workspace drop-down menu initiates a formal request process, allowing Org Admins or Owners to approve access. Routing approvals to a dedicated channel (e.g., #guest-approvals) centralizes and streamlines the process, ensuring visibility and compliance. This method supports governance by tracking requests and aligns with Slack’s best practices for managing guest access, a key topic in the Salesforce Certified Slack Administrator Exam. It ensures consultants are added securely with appropriate permissions.

Incorrect Answers:

❌ B) Add the consultants as full members to provide the most flexibility in their ability to access necessary channels.
Adding consultants as full members grants excessive access, including all channels and features, which is insecure and unnecessary for consultants who only need limited access. Multi-Channel Guest roles are designed for this purpose, making this option inappropriate.

❌ C) @mention their Workspace Admin in the appropriate #proj channel to request guest access.
@mentioning a Workspace Admin in a project channel is informal and lacks a structured approval process. It risks oversight and doesn’t leverage Slack’s guest invitation workflow, making it less effective for managing guest access requests.

❌ D) Direct message (DM) an Org Owner requesting that their consultants be added as guests.
DMing an Org Owner is unstructured and bypasses Slack’s formal guest invitation process. It lacks transparency and tracking, making it inefficient and prone to errors compared to using the workspace drop-down menu with a dedicated approval channel.

Reference:
Slack Help Center: Invite guests to your workspace
Salesforce Trailhead: Slack Enterprise Grid Administration

Explanation:

To enable users to start working on Slack Enterprise Grid quickly while choosing an IdP, use Slack’s built-in authentication with email and password (Option B). This allows immediate access without requiring SSO configuration, which can be implemented later. Other options either delay access or misuse guest roles.

✅ B) Use Slack's built-in authentication, which will prompt members to sign in using their email address and Slack password.
Slack’s built-in authentication allows new users to sign in with their email and a Slack password, enabling immediate access to the Enterprise Grid while the organization selects and configures an IdP. This method avoids delays from waiting for SSO setup and ensures users can start collaborating quickly. Once the IdP is chosen, SSO can be configured without disrupting existing users. This approach aligns with the Salesforce Certified Slack Administrator Exam’s focus on balancing security and user onboarding efficiency during Enterprise Grid deployment.

Incorrect Answers:

✖️ A) Add all new users to your Enterprise Grid as guests, so their sign-in process is not disrupted after you choose an IdP and configure SSO.
Adding users as guests restricts their access to specific channels, unsuitable for full employees. Guests don’t require SSO, but this approach misaligns with the need for full user access and creates unnecessary complexity when transitioning to SSO.

✖️ C) Downgrade your Slack plan to Business+ and turn off SSO.
Downgrading to Business+ is unnecessary and counterproductive, as Enterprise Grid is designed for large organizations with advanced security needs. Turning off SSO doesn’t address the goal of enabling immediate user access and limits scalability.

✖️ D) Choose and configure your IdP before configuring single sign-on (SSO), since end users can't sign in to Enterprise Grid without SSO.
This is incorrect, as Enterprise Grid supports built-in authentication, allowing users to sign in without SSO. Waiting for IdP configuration delays user access unnecessarily, conflicting with the goal of enabling users to start working as soon as possible.

Reference:
Slack Help Center: Set up single sign-on for your organization
Salesforce Trailhead: Slack Enterprise Grid Security

permissions to manage users and channels with the fewest privileges, avoiding excessive access. Other roles either grant too much or too little authority.

✅ B) Workspace Admin
The Workspace Admin role on the Business+ plan grants permissions to manage users (e.g., inviting, deactivating) and channels (e.g., creating, archiving) within a single workspace, meeting the needs of the task with minimal privileges. Unlike Org Admin or Workspace Owner roles, which are relevant for Enterprise Grid or have broader access, Workspace Admin is tailored for Business+ and avoids granting unnecessary control. This aligns with the Salesforce Certified Slack Administrator Exam’s emphasis on assigning roles based on least privilege for effective governance and security.

Incorrect Answers:

✖️ A) Org Admin
Org Admin is specific to Enterprise Grid plans, not Business+, and grants organization-wide permissions across multiple workspaces. This exceeds the needs of managing a single workspace, violating the principle of least privilege for the Head of IT’s tasks.

✖️ C) Workspace Owner
Workspace Owner has broader permissions than Workspace Admin, including managing billing and workspace settings like SSO. This role grants more access than necessary for user and channel management, making it less appropriate than Workspace Admin.

✖️ D) Member
The Member role lacks administrative permissions, preventing the Head of IT from managing users or channels. Members can only participate in channels and use Slack features, making this role insufficient for the required duties.

Reference:
Slack Help Center: Roles and permissions in Slack
Salesforce Trailhead: Slack Admin Basics

Explanation:

To secure internal information on mobile devices while allowing Slack communication, requiring mobile devices to have a passcode (Option B) is the best option. This ensures devices are protected against unauthorized access if lost or stolen, balancing security and accessibility. Other options are either impractical or less effective.

✅ B) Require mobile devices to have a passcode.
Requiring a passcode on mobile devices ensures that lost or stolen devices are protected from unauthorized access, safeguarding internal Slack data. Slack’s Enterprise Mobility Management (EMM) integration, available on Enterprise Grid, allows Org Admins to enforce passcode requirements via Mobile Device Management (MDM) solutions. This approach is proactive, aligns with compliance needs, and maintains user access to Slack for communication. It’s a key security practice covered in the Salesforce Certified Slack Administrator Exam, emphasizing device-level security for mobile workforces without disrupting productivity.

Incorrect Answers:

❌ A) Require users to sign out of Slack on their mobile device when it’s not in use.
Requiring users to sign out manually is impractical for traveling sales associates who need frequent access. It relies on user compliance, which is unreliable, and doesn’t prevent unauthorized access to the device itself, making it less secure than a passcode.

❌ C) Turn on Mobile Session Duration to invoke an automatic logout from the Slack mobile app after specified time frame.
Mobile Session Duration logs users out after a set period, but it doesn’t protect the device from unauthorized access if lost or stolen. Data cached in the app remains vulnerable without a device passcode, making this less effective.

❌ D) Do not allow Slack app download on corporate mobile devices.
Preventing Slack app downloads ensures security but eliminates mobile communication, conflicting with the need for associates to stay connected. This approach is impractical and disrupts productivity, making it unsuitable.

Reference:
Slack Help Center: Enable Enterprise Mobility Management for your organization
Salesforce Trailhead: Slack Enterprise Grid Security

Explanation:

To prevent non-approved vendors from communicating via Slack Connect, adjust the Slack Connect settings to allow only Org Admins and Org Owners to send and accept DMs from outside organizations (Option B). This restricts external communication to authorized roles, ensuring proper vetting. Other options are less effective or misaligned.

B) Adjust the Slack Connect for direct messages settings so that only Org Admins and Org Owners can send and accept direct messages (DMs) from outside organizations.
On the Enterprise Grid plan, restricting Slack Connect DMs to Org Admins and Owners ensures that only vetted individuals can initiate or accept external communications, preventing non-approved vendors from engaging. This setting, configurable in the Admin Dashboard, centralizes control and aligns with the procurement team’s vetting process. It’s a key security feature for managing external collaboration, as emphasized in the Salesforce Certified Slack Administrator Exam, ensuring compliance without limiting approved Slack Connect channel usage.

Incorrect Answers:

A) Set up the custom messaging in Guidelines for using Slack Connect with the policy for communicating with approved vendors only.
Custom messaging in Slack Connect guidelines informs users of policies but doesn’t enforce restrictions. Non-approved vendors could still initiate communication, as guidelines rely on user compliance rather than technical controls, making this ineffective.

C) Restrict Slack Connect to a specific workspace so that only users who have access to that workspace can also access your Slack Connect channels.
Restricting Slack Connect to a specific workspace limits channel access but doesn’t prevent non-approved vendors from sending DMs or connection requests. This approach doesn’t address the concern of unvetted external communication.

D) Disable the Use Slack Connect with free teams option so that only paid workspaces can access your Slack Connect channels.
Disabling Slack Connect with free teams limits interactions to paid plans but doesn’t ensure vendors are approved by the procurement team. Non-approved vendors on paid plans could still connect, making this insufficient.

Reference:
Slack Connect: Manage your organization’s connections
Salesforce Trailhead: Slack Enterprise Grid Administration

Explanation:

To notify only the 10 marketing team members about an urgent re-prioritization for their planning meeting, the marketing director should create an @marketing-team user group and use it in #marketing-discussion (Option B). This ensures targeted notifications to the relevant team members, avoiding unnecessary alerts to others. Other methods are either inefficient or overly broad.

✅ B) Create an @marketing-team user group and use the @marketing-team user group in #marketing-discussion to communicate the change in priority to the team that needs to be informed for tomorrow’s team meeting.
Creating an @marketing-team user group allows the marketing director to notify only the 10 team members in the #marketing-discussion channel, ensuring they receive the urgent re-prioritization message for the planning meeting. User groups streamline recurring notifications, ideal for weekly updates, and maintain clarity in a channel with 50 members. This approach leverages Slack’s user group functionality, a key feature in the Salesforce Certified Slack Administrator Exam, for efficient and targeted communication without disturbing non-relevant members.

Incorrect Answers:

❌ A) Send a separate direct message to each of the 10 team members notifying them of the change.
Sending individual DMs to 10 team members is time-consuming and inefficient, especially for weekly re-prioritizations. It lacks the scalability and organization of a user group, making it impractical for recurring notifications.

❌ C) Post a message to #marketing-discussion, without notifying anyone.
Posting without notifications risks the message being missed by the 10 team members, especially in a busy channel with 50 members. This approach fails to meet the need for ensuring the team is actively notified before the meeting.

❌ D) Use @here and @channel to notify the entire channel of the change.
Using @here or @channel notifies all 50 members, including those not attending the meeting, causing unnecessary distractions. This approach is too broad and doesn’t target the specific 10 team members required.

Reference:
Slack Help Center: Create and manage user groups
Salesforce Trailhead: Slack Admin Basics

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