Salesforce-Slack-Administrator Exam Dumps - Salesforce Administrator Questions and Answers

Slack's official analytics guidelines recommend:

"The average number of active days per user is a strong measure of engagement and adoption."

Number of DMs (A) focuses only on private messaging, not overall adoption. Channel/workspace membership (B) doesn't measure activity. New workspace creation (D) is not typically relevant to students and is often disabled.

(Reference: Slack Administration Study Guide - User Activity Analytics)

===========

—

According to Slack’s official documentation regarding Legal Holds:

"The Legal Holds feature is only available on the Enterprise Grid plan. Legal holds allow Workspace Owners and Org Owners to preserve messages and files of specific users for compliance and legal purposes."

Legal Holds are a critical feature for enterprises with compliance requirements, and they are not available on the Free, Pro, or Business+ plans.

(Reference: Slack Administration Study Guide - Security, Compliance, and Legal Holds)

===========

—

Slack best practices for organized workspaces state:

"Establishing and enforcing naming conventions helps members easily identify the purpose of a channel at a glance and maintain workspace organization."

Apps (A) aren't necessary for simple naming. Asking for descriptions (B) is unreliable. Spreadsheets (C) are cumbersome and not visible at channel creation.

(Reference: Slack Administration Study Guide - Best Practices for Channel Naming)

===========

—

According to Slack’s best practices:

"Claim your domains as soon as possible. This process is not retroactive — workspaces created before claiming domains will continue to exist independently unless manually migrated."

Thus, prompt domain claiming ensures better control and prevents users from unintentionally creating ungoverned workspaces.

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

===========

—

Slack documentation states:

"When public file sharing is enabled, file sharing settings apply to files uploaded by any organization participating in a Slack Connect channel."

DLP monitoring (A) is separate and applies differently. File upload permissions (C) can be restricted through Slack Connect settings. Any user, not just admins (D), can create external file links if allowed.

(Reference: Slack Administration Study Guide - Managing Public File Sharing in Slack)

===========

—

Slack Connect rules state:

"Once an external organization joins a Slack Connect channel, they can see all existing channel history unless otherwise configured. Before they accept, Org Owners can revoke the pending invitation to prevent access."

Thus, channel history will be visible, and the requestor should be shown how to revoke the invite.

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

===========

—

Workflow Builder allows launching workflows based on specific triggers. Slack officially states:

"Supported triggers include when a new member joins a channel and at a scheduled date and time."

Keyword usage (A) is not currently a native trigger without a custom app. New channel creation (B) is not a trigger. New member joining a workspace (D) by itself is not a trigger unless tied to joining a specific channel.

(Reference: Slack Administration Study Guide - Workflow Builder Triggers)

===========

—

Slack EMM documentation states:

"After EMM is activated, users must complete the EMM setup within a 72-hour window or they will be automatically signed out from Slack."

EMM does not force re-authentication every 72 hours (C). Device OS updates (A) are not mandatory for EMM sign-ins. "Keep users signed in" (D) relates to desktop sessions more than mobile EMM enforcement.

(Reference: Slack Administration Study Guide - Enterprise Mobility Management (EMM) Setup Requirements)

—

Slack recommends converting public channels to private when:

"Sensitive or confidential information (e.g., financial results, M&A activity) begins to be discussed and needs to be restricted to a limited group."

Quarterly earnings (D) are sensitive, non-public information, justifying the need for a private channel. Options A and B refer to comfort and tone but not confidentiality. Option C relates to relevance, not security.

(Reference: Slack Administration Study Guide - Channel Privacy and Confidential Conversations)

===========

—

Slack best practices for app governance recommend:

"The most efficient method is to proactively restrict high-risk apps and automatically allow safe, non-restricted apps, minimizing admin intervention."

Annual whitelisting (B) is infrequent and can quickly become outdated. Asking users to self-rate risk (C) is unreliable. Complex rule chains (D) are difficult to maintain.

(Reference: Slack Administration Study Guide - Streamlining App Management)

===========

—