Free Salesforce Salesforce-Slack-Administrator Practice Exam with Questions & Answers | Set: 3

According to Slack’s role management documentation:

"Roles Admins have the ability to assign and manage system roles for members across the Slack organization."

Compliance Admins (A) manage legal holds and data exports. Channels Admins (C) manage channel structures. Users Admins (D) manage member profiles and deactivations. Only Roles Admins manage assignment of admin permissions.

(Reference: Slack Administration Study Guide - System Roles Overview)

Slack recommends for secure, large-scale onboarding:

"Using a SAML-based IdP with SCIM provisioning allows automatic user creation and deactivation based on your identity provider, ensuring security and control."

Email signup (B) and JIT provisioning (C) are less secure. Admin invites (D) are manual and error-prone at this scale.

(Reference: Slack Administration Study Guide - Secure User Provisioning on Business+)

===========

—

When you claim relevant domains for your Enterprise Grid organization:

"Any user with an email address matching a claimed domain who attempts to create a new workspace will be directed to join the Enterprise Grid organization, ensuring that all workspaces fall under centralized policies for security, compliance, and retention."

This process prevents rogue or unmanaged workspaces and ensures consistent governance.

(Reference: Slack Administration Study Guide - Claiming Domains and Managing Grid Compliance)

===========

—

The best practice outlined in Slack Enterprise Grid documentation:

"Enable workspace creation requests, so users can request new workspaces that will be routed to Org Admins via an internal channel for review and approval."

This approach scales better for high-volume requests, allowing multiple admins to track and approve them efficiently from a centralized channel, rather than relying on manual direct messages.

(Reference: Slack Administration Study Guide - Enterprise Grid Workspace Management)

===========

—

Slack recommends for external collaborations:

"Slack Connect channels are the preferred method to collaborate securely with external organizations instead of bringing external users into your workspace as full members or guests."

Inviting 15 external users as Multi-Channel Guests (C) is less scalable and harder to manage. Adding them to the IdP (B) is unnecessary and risky for external contractors. Creating a new workspace (D) would complicate governance.

(Reference: Slack Administration Study Guide - Slack Connect Collaboration Best Practices)

The proper course of action involves:

Deleting the file through an integrated Data Loss Prevention (DLP) solution.

Reviewing access through the Audit Logs API.

Slack documentation confirms:

"A DLP integration allows detection and remediation (e.g., deletion) of sensitive files or messages. The Audit Logs API provides detailed logs of user activity, including file downloads."

Mobile Device Management (MDM) focuses on device security, not file tracking, and EKM controls encryption but doesn't show file download actions.

(Reference: Slack Administration Study Guide - Security and Compliance - Data Loss Prevention and Audit Logs)

===========

—

Slack provides an option to restrict the use of @channel, @here, and @everyone mentions to Workspace Owners and Admins only.

Slack’s guidance states:

"To prevent disruption, you can limit the ability to use @channel, @here, and @everyone mentions to only Workspace Owners and Admins."

This prevents misuse in large public channels while still preserving structured communications.

(Reference: Slack Administration Study Guide - Notification Settings and Messaging Restrictions)

Slack recommends setting and communicating a strong channel naming and creation policy to improve discoverability and reduce confusion.

According to Slack best practices for channel management:

"A consistent channel naming convention helps employees find information more easily and prevents the creation of duplicative channels. A documented and communicated policy ensures that channel creators follow structure guidelines without needing admin intervention."

Pinning guides (A) and posting lists (B) are helpful for awareness but do not solve the underlying structural issues. Requiring admins for every new channel (C) is too restrictive and counter to Slack's flexibility model.

(Reference: Slack Administration Study Guide - Channel Management and Naming Conventions)

===========

—

According to Slack Enterprise Grid documentation:

"To allow users to integrate external tools into workflows, admins must enable steps from apps and allow workflows to include webhook triggers."

Also,

"Enabling Workflow Builder and allowing users to create workflows (except Guests) ensures flexibility."

While A (App Managers) grants permission to approve apps, it is not needed for creating workflows. Channel emails (C) are unrelated. Workflow creation policy (E) is important too but the critical steps for app usage and webhook integration are B and D.

(Reference: Slack Administration Study Guide - Workflow Builder with External Integrations)

—

Slack recommends:

"Use public announce-only channels for company-wide updates. Only designated members can post, while everyone else can view and react without disrupting the information flow."

This keeps updates structured and prevents off-topic discussion, while maximizing visibility to the whole organization.

(Reference: Slack Administration Study Guide - Announce-Only Channel Best Practices)

===========

—