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

When a Slack Connect channel is disconnected:

"Each organization will keep an archived copy of the channel. All messages and files shared by members of both organizations remain accessible to each organization's members."

Neither side can continue posting after disconnection — the channel is archived.

(Reference: Slack Administration Study Guide - Managing Slack Connect Disconnections)

===========

—

Slack’s SCIM API documentation states:

"SCIM provisioning can be used to sync user attributes, like department, title, and location, from an Identity Provider to Slack profiles."

Analytics API (A) and Custom Profile API (C) focus on reporting or manual updates, not syncing at scale. Manual field creation (D) does not automate the syncing.

(Reference: Slack Administration Study Guide - SCIM Attribute Syncing)

===========

—

Slack role definitions specify:

"Workspace Owners have the highest level of permissions at the workspace level, including setting permissions, managing members, and configuring settings."

Workspace Admins (C) have significant permissions but not complete control. Org Admins (B) are for org-wide actions, and Roles Admin (D) is specific to assigning roles, not broader workspace management.

(Reference: Slack Administration Study Guide - Roles and Permissions Overview)

===========

—

Slack advises:

"Turning on Mobile Session Duration policies allows admins to automatically log users out of Slack mobile apps after a set period, reducing risk if a device is lost or stolen."

Requiring a passcode (B) is good mobile practice but not Slack-specific. A (manual sign-out) is unreliable. D (no app downloads) would block necessary communication entirely.

(Reference: Slack Administration Study Guide - Mobile Security Features)

Slack guidance emphasizes:

"Default channels help orient new members by exposing them to important organizational channels and reinforcing naming conventions and community norms."

A is inaccurate — default channels are typically public (not required for all communication). B is incorrect because default channels cannot be private. C refers to general Slack usage, but not specifically about default channels.

(Reference: Slack Administration Study Guide - Setting Default Channels for Workspaces)

===========

—

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)

===========

—

In Slack, only the Primary Owner has the ability to deactivate other Workspace Owners.

Slack documentation states:

"Only the Primary Owner can deactivate or transfer ownership of another Workspace Owner's account."

Thus, Cortez, despite being a Workspace Owner himself, cannot deactivate Camdin’s account.

(Reference: Slack Administration Study Guide - Workspace Roles and Account Deactivation)

===========

—

For long-term archiving and compliance with regulatory requirements:

"eDiscovery integrations allow organizations to collect, archive, and export Slack messages and files to meet legal, regulatory, and compliance needs."

DLP (A) focuses on preventing data leaks. MDM (B) secures mobile access, and EKM (C) controls encryption keys but does not inherently archive data.

(Reference: Slack Administration Study Guide - Security and Compliance - eDiscovery Integration)

===========

—

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)

Slack recommends:

"Multi-workspace channels allow you to share a channel between select workspaces within an Enterprise Grid org, enabling collaboration across designated workspaces while keeping others excluded."

Org-wide channels (A) include all members by default. Slack Connect (B) is for external organizations, not internal collaboration. Inviting Internal members as guests (C) is unnecessary and inefficient.

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

===========

—