Pass the Salesforce Salesforce Administrator Salesforce-Slack-Administrator Questions and answers with CertsForce

Slack’s best practices for app approval workflows recommend:

"Gather information on licensing requirements and urgency to prioritize app approvals and ensure security reviews align with business needs."

Asking about DLP (A) and EKM (C) are technical security details assessed by IT or Security, not by the requestor. Competitor usage (B) is irrelevant to Slack security or approval decisions.

(Reference: Slack Administration Study Guide - Managing App Approvals)

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+)

===========

—

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)

===========

—

On Slack Enterprise Grid:

"Org Owners are responsible for organization-wide security and compliance settings, including configuring and managing Single Sign-On (SSO) for the entire organization."

Workspace Owners manage workspace-level settings such as retention policies (A) or app approvals (D), but they cannot manage enterprise-wide SSO configurations. Resetting passwords individually (B) is not something either can do directly — identity is managed via the IdP in Enterprise Grid.

(Reference: Slack Administration Study Guide - Roles and Permissions in Enterprise Grid)

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)

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’s policy specifies:

"When a user creates a channel, they are automatically assigned the Channel Manager role for that channel and can manage actions such as archiving when the project is complete."

There is no need to promote the user to Workspace Admin (A). Slack does not automatically archive channels based on inactivity (B) unless using external tools. Slack doesn't have a native automatic expiration feature for channel deletion (D).

(Reference: Slack Administration Study Guide - Channel Manager Roles and Responsibilities)

—

Slack recommends that:

"Workspace Admins should be knowledgeable about Slack best practices, support user adoption, enforce etiquette, and provide feedback on policies."

The candidate in A already demonstrates leadership in Slack usage, policy understanding, and peer support. B focuses on technical integration (more developer-like), C focuses on Slack Connect specifics (not general admin readiness), and D describes a user who needs support rather than offering it.

(Reference: Slack Administration Study Guide - Choosing Workspace Admins)

===========

—

Slack’s Enterprise Grid documentation clearly states:

"Syncing IdP groups with Slack allows you to automatically manage workspace membership, channel membership, and access control based on IdP group assignments."

Key benefits include:

Automatically provisioning and deprovisioning members to specific workspaces (A).

Maintaining mandatory membership in designated channels (B).

Maintaining mandatory membership in designated workspaces (C).

Assigning system roles, approved apps, or admin roles (D, E, F) is not automatically handled through IdP group syncing.

(Reference: Slack Administration Study Guide - Identity and Access Management)

SAML SSO provides:

"Organizations with more control over their authentication policies, including password requirements, session durations, and login behaviors."

"Employees can use their existing login credentials for all applications, including Slack, through SSO integration with the identity provider."

Option B is wrong because SSO depends on having an IdP in the first place. Option C is incorrect because SSO is available only on certain Slack paid plans (not all). Option E refers to Enterprise Key Management (EKM), not SSO.

(Reference: Slack Administration Study Guide - Single Sign-On (SSO) Benefits)

===========

—