Free Practice Questions for Salesforce Salesforce-Slack-Administrator Exam

To automatically manage user deactivation:

"If your Identity Provider supports SCIM provisioning, and it is correctly configured with Slack, user deactivation in the IdP will trigger automatic deactivation of the user's Slack account."

SCIM ensures seamless deprovisioning. Just-in-Time deactivations (D) are not a Slack feature, and changing the email manually (A) is not secure or scalable.

(Reference: Slack Administration Study Guide - User Deprovisioning with SCIM)

The best way to manage noise while protecting sensitive information includes:

• Limiting posting permissions — According to Slack’s official guidance:

"You can restrict who can post to a channel by limiting posting permissions to specific people, ensuring that only authorized individuals can post while others can read."

• Creating a private channel with a personal benefits workflow:

"Private channels are suitable for discussions requiring confidentiality. Workflows can route sensitive questions to HR without public visibility."

Encouraging DMs (option C) helps, but it is not a structured or scalable solution for organizational processes. Archiving the channel (option D) would disrupt access to the historical benefits information and is unnecessary.

(Reference: Slack Administration Study Guide - Channel Management Best Practices and Workflows)

—

Slack's documentation on EMM policies specifies:

"Enterprise Mobility Management (EMM) requirements apply only to full members of your Slack organization. Guest accounts (Single-Channel or Multi-Channel Guests) are not required to use the Slack for EMM app."

Thus, guests are exempt from EMM enforcement. Options B and C incorrectly state guests can be controlled via EMM. D is unrelated.

(Reference: Slack Administration Study Guide - EMM and Guest Account Behavior)

Moving sales channels into the Global workspace and making default channels private would:

Create confusion and friction in adoption.

Reduce transparency and cross-functional collaboration.

Slack documentation highlights:

"Workspaces should be structured to align naturally with how teams operate. Making core channels private may limit discoverability and collaboration, which contradicts Slack’s goals for connection and transparency."

Options B, C, and D promote transparency and collaboration, which is the intended use of Slack across cross-functional teams.

(Reference: Slack Administration Study Guide - Change Management and Slack Adoption Strategies)

===========

—

Slack recommends:

"When moving to Enterprise Grid, consolidate where possible but avoid unnecessary disruption. Rename and rebrand workspaces appropriately while keeping existing structures when they serve their users well."

This keeps the marketing team undisturbed and consolidates sales into one clean, unified workspace.

(Reference: Slack Administration Study Guide - Enterprise Grid Migration Strategy)

The best practice for completed projects that may need to be referenced later is:

"Archive the public channel. Archived channels remain searchable and can be browsed for historical reference, but new posts are disabled."

Deleting the channel would risk losing accessibility to discussions, and unnecessary privacy changes would confuse users.

(Reference: Slack Administration Study Guide - Channel Archiving and Searchability)

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)

===========

—

Slack best practices advise creating a new channel:

"When you need a dedicated, transparent space for an ongoing topic, team, or project, such as a new line of business."

For quick or personal conversations (Options A, C, and D), direct messages are more appropriate.

(Reference: Slack Administration Study Guide - Channel vs. Direct Message Best Practices)

Slack recommends using Workflow Builder to:

"Trigger onboarding workflows automatically when employees join channels, and use custom forms to collect consistent information and reduce unnecessary communication."

Inviting new hires as Single-Channel Guests (Option B) is not relevant because they are expected to have full access pre-onboarding.

(Reference: Slack Administration Study Guide - Automating Onboarding with Workflows)

===========

—