Explanation:

✅ C. Set a mobile session duration of 2 weeks for all mobile devices.
Setting a fixed mobile session duration balances security and usability. A 2-week session timeout is a common practice that helps ensure users don’t have to log in too frequently—reducing frustration and improving adoption—while still limiting the risk of unauthorized access if a device is lost or compromised.

❌ Why the other options are less appropriate:

A. Allow users to set their own mobile session duration.
This can lead to inconsistent security policies and weaker protection if users choose overly long sessions.

B. Log all users out of mobile anytime your organization experiences a security threat.
While necessary in some high-risk scenarios, this reactive approach can disrupt users frequently and hurt productivity.

D. Allow all users to remain logged in infinitely.
This poses significant security risks, especially if devices are lost or stolen, and is not recommended.

Reference:
Slack Help Center – Manage session duration and device access

Explanation:

Private channels in Slack are best used when:

➡️ The conversation involves sensitive or confidential information (e.g., HR discussions, compensation, performance reviews, legal matters).
➡️ Membership should be restricted and controlled by channel admins.
➡️ Visibility needs to be limited to a specific set of participants.

In this case, HR and hiring teams discussing candidates, salaries, and role requirements require confidentiality, making a private channel the most appropriate choice.

❌ Why the Other Options Are Incorrect:

B. A team kicking off a new project...
✗ Best suited for a public channel, so others in the org can find, join, and contribute if relevant. Promotes transparency.

C. A cross-functional team exploring new product ideas...
✗ Works better in a public channel to encourage broad visibility, contributions, and collaboration across functions.

D. Globally distributed org creating an HQ events channel...
✗ Should be public, so all interested employees (especially those near HQ) can join freely. No confidentiality required.

📖 Reference:
Slack Help: Types of channels
Slack Best Practices: Use public channels for transparency and collaboration, private channels for sensitive/confidential work.

👉 Key exam rule of thumb:
Public channel = transparency & collaboration.
Private channel = confidentiality & restricted access.

Explanation:

The two best benefits of creating user groups for your workspace are:
✅ A. Notifies a group of members who often need to be notified at once. For example: @managers
✅ D. Assigns default channels to users when they start working at the company.

Here's an explanation for each:

✅ A. Notifies a group of members who often need to be notified at once. For example: @managers
This is one of the primary and most common uses of user groups. Instead of individually tagging multiple people, you can tag a user group (e.g., @marketing, @support-team, @on-call) to notify everyone within that group simultaneously. This saves time and ensures consistent communication to relevant teams or roles.

✅ D. Assigns default channels to users when they start working at the company.
User groups can be used in conjunction with Slack's provisioning settings (especially if integrated with an identity provider like Okta or Azure AD) to automatically add new users to specific channels based on their role or department. For instance, all new employees in the "Sales" user group could automatically be added to #sales-announcements, #sales-team, and #general. This streamlines the onboarding process and ensures new hires have immediate access to relevant information and conversations.

Let's look at why the other options are not correct:

❌ B. Sets channel management permissions at the workspace level.
Channel management permissions (e.g., who can create channels, archive channels) are typically set at the workspace or organization level (in Enterprise Grid) for roles like Workspace Admins or Owners, not directly by user groups. User groups primarily manage membership for notification and channel assignment purposes.

❌ C. Sets permissions on who can view your workspace analytics.
Access to workspace analytics is generally controlled by Slack roles (e.g., Workspace Owners, Workspace Admins) or specific permissions granted within the analytics dashboard, not directly by assigning users to a user group.

❌ E. Assigns default Slack app integrations to users when they start working at the Company.
Slack app integrations are usually installed and managed at the workspace or channel level by admins, and their availability can be controlled. While certain apps might be relevant to specific teams, user groups themselves don't directly "assign" app integrations to individual users upon joining. Users typically discover and add apps relevant to their work or are directed to use specific apps available in their channels.

Reference:
These benefits are fundamental features of Slack user groups and are commonly highlighted in Slack's official documentation regarding user group functionality.

Explanation:

🟢 A. Deactivate the members in the Organization Settings 'Members' tab.
As an Org Admin on an Enterprise Grid plan, you have the ability to manage user accounts, including deactivation. The recommended and standard way to deactivate members who are leaving is to do so directly in the Organization Settings under the 'Members' tab. This allows you to efficiently deactivate multiple users before their departure date.

🔴 Why other options are less suitable:

B. Contact Slack via /feedback to get the members deactivated.
This is unnecessary and inefficient. Admins have direct control over user management and do not need to rely on Slack support for routine user deactivation.

C. Deactivate the members utilizing the SCIM API.
While SCIM API can be used for automated user provisioning and deprovisioning, it typically requires setup and developer resources. For a standard admin task like deactivating a known list of users, using the Admin Console is faster and simpler.

D. Request the Primary Org Owner do this, as they are the only one who can perform this action.
Org Admins also have the permissions needed to deactivate members. It’s not restricted solely to the Primary Org Owner.

Reference:
Slack Help Center – Deactivate or delete members
Slack Enterprise Grid Admin Guide – Manage members across your organization

Explanation:

When a Slack Connect channel is disconnected:

➡️ Each participating organization retains an archived copy of the channel in their own workspace.
➡️ All messages and files shared by all organizations remain visible to members of that org, even after disconnection.
➡️ The channel becomes read-only (archived), meaning no new messages or files can be posted.

This ensures both parties still have a full record of the collaboration, which is often important for reference, compliance, or auditing.

❌ Why the Other Options Are Incorrect:

A. All organizations will retain full access... and can continue to use it as normal.
✗ Incorrect — the channel is archived after disconnection, so it cannot be used as normal.

B. Ad Heroes will retain full control... and can continue to post messages and files.
✗ Wrong — once disconnected, posting is no longer possible (archived = read-only).

C. Ad Heroes will keep an archived version, but only files posted by Ad Heroes are visible.
✗ Misleading — the archive contains all messages and files from all participants, not just those from Ad Heroes.

📖 Reference:
Slack Help: Disconnect a Slack Connect channel
Slack Connect FAQ

👉 Exam tip: Anytime a question mentions “disconnected Slack Connect channels”, remember:
➡️ Archived copy remains in each org, with all shared history preserved, but no new posting allowed.