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

Slack's Workflow Builder allows users to create workflows without writing code, and Admins have visibility over workflows to maintain governance.

According to Slack documentation:

"Workspace Owners and Admins can view and manage all published workflows in their workspace." "For Enterprise Grid organizations, Org Owners and Org Admins can see workflows across all workspaces."

Option A is false — creating a workflow is a quick process requiring fewer than five clicks. Option C is inaccurate because regular members can also view workflows they have access to via Workflow Builder, not just Owners or Admins.

(Reference: Slack Administration Study Guide - Workflow Builder and Admin Controls)

===========

—

In Slack Enterprise Grid, for workspaces set to Invite Only (especially those involving external partners), users must be explicitly invited.

According to Slack documentation:

"Invite-only workspaces require an invitation from a Workspace Admin before members can join."

Because the External workspace is likely Invite Only for security reasons, the new hire must be invited to join it. Searching and seeing the workspace does not bypass the requirement.

(Reference: Slack Administration Study Guide - Workspace Visibility and Access Control)

===========

—

Slack recommends for mobile session management:

"Setting a mobile session duration of around two weeks provides a good balance between security and usability, ensuring users aren't prompted to log in too frequently."

Allowing users to set their own session length (A) would reduce security controls. Logging everyone out during any threat (B) is too disruptive for normal operations. Allowing infinite sessions (D) risks serious security exposure.

(Reference: Slack Administration Study Guide - Mobile Security Best Practices)

According to Slack’s API documentation:

"The chat:write scope allows an app to send messages as @bot into channels, groups, and DMs where the app is authorized."

admin.apps:write (B) relates to managing apps, not sending messages. admin.conversations:read (C) relates to reading conversations at admin level. chathistory (D) relates to reading message history.

(Reference: Slack Administration Study Guide - App Scopes and Permissions)

===========

—

Slack’s recommendation for increasing adoption and productivity states:

"Connect existing tools that users are already familiar with to Slack, so they immediately see value without needing extensive new training."

This approach enhances workflows and familiarity, without adding a heavy burden of learning or complex processes.

(Reference: Slack Administration Study Guide - Accelerating Slack Productivity with Integrations)

===========

—

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)

Slack's immediate response guidance states:

"If SCIM provisioning is unavailable, Workspace Admins should manually deactivate users through Slack settings to immediately prevent access."

Changing the email (A) is messy and not recommended. Making #general read-only (B) doesn't prevent broader access. Contacting support (D) is useful, but not immediate enough for stopping access.

(Reference: Slack Administration Study Guide - Managing User Access in Case of SCIM Outage)

===========

—

Slack recommends:

"When social channels overwhelm the workspace and impact findability of work-related content, creating a separate workspace for social and community discussions helps maintain focus and discoverability."

Simply deleting channels (B, D) risks damaging community culture. Making channels multi-workspace (A) doesn’t solve workspace clutter — it just duplicates visibility.

(Reference: Slack Administration Study Guide - Workspace Design for Scalability and Discoverability)

===========

—

Slack recommends using multi-workspace private channels to manage sensitive information securely across workspaces.

"Multi-workspace private channels allow members from multiple workspaces to securely collaborate, making them ideal for department-specific discussions and sensitive topics."

Public channels (A) are inappropriate due to the sensitivity of the HR discussions. Private channels limited to one workspace (C) would restrict access. Group DMs (D) are not scalable or organized for ongoing collaboration.

(Reference: Slack Administration Study Guide - Managing Multi-Workspace Private Channels)

===========

—

Mandatory Two Factor Authentication (2FA) adds an extra layer of security to member accounts. When enabled, Slack requires that:

"Members must enter a verification code from an authentication app or text message after submitting their password to successfully sign in."

This means each time members sign into Slack, they must provide both their password and a second factor, typically a code generated by a mobile authentication app or received via SMS. This prevents unauthorized access even if a password is compromised.

The other options (A, B, C) describe different security measures but do not accurately represent the behavior of 2FA as configured in Slack.

(Reference: Slack Administration Study Guide - Security and Compliance - Two Factor Authentication)