Pass the Salesforce Salesforce Administrator Salesforce-Slack-Administrator Questions and answers with CertsForce

In Slack, @channel notifies everyone in a channel, whether or not they're currently active, while @here only notifies active members.

Slack documentation explains:

"Use @channel to notify everyone in a channel of important updates. Use @here to notify only those currently online."

In a case where urgent communication needs to be received either now or seen first thing in the morning, using both ensures coverage without relying only on availability.

(Reference: Slack Administration Study Guide - Using Mentions and Channel Notifications Effectively)

===========

—

Slack Champions are:

"Advocates who model best practices, promote transparency, identify key use cases, and adapt workflows to improve team effectiveness. Champions do not need to be administrators — their main role is to drive cultural adoption."

Option A is incorrect because being a Slack Administrator is not a requirement to be a Champion.

(Reference: Slack Administration Study Guide - Building a Slack Champion Network)

===========

—

Slack documentation advises:

"Group DMs cannot be expanded to include or replace members after they are created. If you need to manage membership over time, you should create a private channel."

Converting the group DM into a private channel allows Chandler to maintain privacy, manage membership changes, and centralize discussions securely.

(Reference: Slack Administration Study Guide - Private Channels vs. Group DMs)

===========

—

Slack compliance best practices state:

"Before configuring Slack for compliance, companies should meet with legal and compliance teams to set internal communication, retention, and monitoring policies tailored to regulatory requirements."

Implementing eDiscovery (D) is important later, but setting policies first ensures the correct technology choices. B and C may not align with regulatory needs without first setting clear policies.

(Reference: Slack Administration Study Guide - Compliance and Legal Alignment)

===========

—

In Slack Connect, the same channel can have different names in each participating organization’s workspace:

"Slack Connect channels may appear with different names in each organization. Members need to search by the name it appears in their own workspace."

Therefore, even though you sent the channel name from your side, the user on the partner organization side needs to find it by the name assigned in their workspace. It is not an issue of membership (A), posting permissions (C), or privacy settings (B) in this case.

(Reference: Slack Administration Study Guide - Slack Connect Channel Management)

Slack recommends using user groups to efficiently notify a specific subset of people:

"User groups allow you to mention multiple people at once by tagging the group’s handle, ensuring the right people are notified without disturbing unrelated members."

Using @channel or @here would notify all 50 members unnecessarily. Sending 10 direct messages individually is inefficient and error-prone.

(Reference: Slack Administration Study Guide - User Groups and Targeted Notifications)

===========

Slack’s guidance for handling inactive channels states:

"Archiving a channel preserves its content and history, allowing it to remain searchable without accepting new posts."

Deleting (A) would permanently remove the content. Renaming or limiting posting (C, D) are not standard clean-up procedures for inactive channels.

(Reference: Slack Administration Study Guide - Channel Lifecycle Management)

According to Slack App Management best practices:

"Turn on app approval to restrict app installation to only those apps that have been reviewed and approved."

"Notifications about app requests should be sent to a specific Slack channel where app managers can easily review and approve or deny requests."

Options A and C suggest manual, ad-hoc processes, which are not scalable or officially recommended for structured app management. Option B incorrectly describes app restrictions not tied to a formal approval process.

(Reference: Slack Administration Study Guide - App Management and Approvals)

Slack's official documentation states:

"SCIM provisioning is ideal for automatically managing large user populations, assigning them to workspaces, and ensuring immediate onboarding or deactivation through integration with your Identity Provider (IdP)."

It is perfect for multiple workspaces (A) and large, one-time onboarding events like a company-wide Slack launch (E).

Options B and C relate to Slack Connect and app behavior, not SCIM. Option D refers to "Just-in-Time" provisioning, not SCIM.

(Reference: Slack Administration Study Guide - SCIM Provisioning)

===========

—

Slack’s internal app management documentation states:

"Adding internal app collaborators allows trusted users to manage an app’s configuration, including OAuth settings, scopes, and other integration behaviors without needing Org Admin privileges."

There is no need to promote SMEs to Org Admins (B) — which would give them excessive permissions across the entire Slack environment. A and C do not enable them to manage the app directly.

(Reference: Slack Administration Study Guide - Managing Internal Apps and App Collaborators)

===========

—