Slack best practices recommend:

" For external users who need access to multiple channels but not the entire workspace, a Multi-Channel Guest account is the ideal solution. "

Full member access (D) is inappropriate for external users. Slack Connect DMs (B) would not provide full channel collaboration. Single-Channel Guest (C) would limit the contractor unnecessarily.

(Reference: Slack Administration Study Guide - Managing Guest Accounts in Enterprise Grid)

===========

—

Slack ' s official administration documentation confirms that when integrating Slack with an external IdP like Google Workspace, the correct method is to set up SAML-based SSO (Single Sign-On).

" You can configure SAML-based SSO with Slack to manage access via your IdP. When transitioning from username/password to SSO, you ' ll need to send out binding emails to link existing Slack accounts with the IdP profiles. "

Google Workspace supports SAML 2.0 standard integration with Slack, and the binding process ensures existing users ' Slack accounts are properly connected to their new IdP credentials.

Options A and C are incorrect because Slack natively supports Google Workspace SAML without needing a custom SAML setup, and option B incorrectly suggests setting up a new workspace, which is unnecessary.

(Reference: Slack Administration Study Guide - Integrations and Authentication Management)

===========

—

Slack’s Enterprise Grid security recommendations state:

" Org Admins can remotely sign a member out of all sessions (desktop, mobile, web) via the admin dashboard to immediately prevent further access without deactivating the user. "

Asking the user (A) is unreliable because they lost the device. Deactivation (B) is extreme if the device may be recovered. Workspace-level action (D) is insufficient for org-wide risk.

(Reference: Slack Administration Study Guide - Managing Lost or Compromised Devices)

===========

—

Slack documentation for Enterprise Grid states:

" Org Owners and Org Admins can enable workspace creation requests via Org Settings, making the process efficient and standardized. "

Posting requirements (B) is not a controlled or actionable system. DM requests (C) are informal and untrackable. Workflows (D) are helpful, but Slack has built-in support for workspace creation requests through Org Settings, which is more efficient.

(Reference: Slack Administration Study Guide - Managing Workspace Creation on Enterprise Grid)

===========

—

Slack API best practices specify:

" The channels.rename method within the Slack API allows admins to programmatically rename channels, making bulk updates efficient and standardized. "

Manually managing through Channel Manager roles (B) or joining channels (D) is slow and error-prone. Keyword notifications (A) don’t rename channels.

(Reference: Slack Administration Study Guide - Managing Channels and Using APIs)

Slack’s documentation for the Business+ plan specifies:

" Workspace Owners can use the standard Import/Export Data tool to export data from public channels without needing to contact Slack or request additional permissions. "

Discovery APIs (D) are only available on the Enterprise Grid plan. A and B would only apply for more extensive exports (such as private channels, which would require special approval, typically for compliance or legal reasons).

(Reference: Slack Administration Study Guide - Exporting Data from Slack)

Slack official plan features state:

" Customizable message and file retention policies are available on Pro, Business+, and Enterprise Grid plans. "

Free plan (C) does not support customizable retention. It ' s limited to 90 days history unless upgraded. Enterprise Grid-only (D) is too restrictive.

(Reference: Slack Administration Study Guide - Message and File Retention Policies)

Slack EKM guidelines specify:

" If sensitive information is exposed improperly (for example, shared in the wrong channel), you can revoke the encryption key, making that content permanently inaccessible. "

Guests (A) or contractors in Slack Connect (B) are expected collaboration contexts and do not warrant revoking keys unless data leakage happens.

(Reference: Slack Administration Study Guide - Enterprise Key Management (EKM) Operations)

===========

—

Slack ' s best practices for private, sensitive, or surprise planning activities:

" Create a private channel when planning events that should remain confidential to a specific group of people. "

This protects the surprise. Public channels (A) expose planning. Group DMs (B) are limited (maximum of 8 people) and informal. A thread in a public space (C) is risky for surprises.

(Reference: Slack Administration Study Guide - Managing Sensitive Conversations)

===========

—

In Enterprise Grid , if auto-provisioning is enabled via an IdP group , when a member is added to that group, they are automatically provisioned to the specified workspace . According to Slack’s official Enterprise Grid documentation:

" When a member is added to an IdP group that’s mapped to a workspace, they will be automatically provisioned (added) to the workspace, unless the workspace is set as hidden. "

Hidden workspaces require an invitation or manual addition and are excluded from automatic group provisioning. Therefore, unless the workspace is hidden, members will automatically join it without needing to take any manual action.

(Reference: Slack Administration Study Guide - Enterprise Grid Configuration and IdP Group Management)