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:

CORRECT ANSWER:

Option B: When there is a new line of business at your company
This is the strongest justification for creating a channel. A new line of business involves cross-functional collaboration, ongoing strategy discussions, documentation, and the potential for many stakeholders to join over time. Channels provide a dedicated, searchable space where teams can share updates, files, and decisions transparently. Unlike DMs, channels are discoverable by others who might need to contribute or catch up later. For example, a #new-business-expansion channel could centralize discussions, reducing the need for repetitive updates or fragmented email threads. This scalability and transparency make channels the ideal choice for significant initiatives.

INCORRECT ANSWERS:

Option A: When you need to confirm meeting times
This scenario is better suited for a direct message (DM) or a calendar invite rather than a channel. Confirming meeting times typically involves a small, specific group of participants and is often a one-time or brief exchange that doesn't require ongoing collaboration or documentation. Using a channel for scheduling would clutter the space with transient messages and reduce its usefulness for broader discussions.

Option C: When a few questions need to be answered quickly
Quick, ad-hoc questions are best resolved via direct messages. Channels are designed for broader, asynchronous collaboration, while DMs excel at immediate, focused communication with a small group. For one-off or time-sensitive queries, DMs prevent channel noise and ensure faster responses.

Option D: When you need to let your manager know you are not feeling well
This is a private matter that warrants a DM, not a channel. Personal health updates are irrelevant to broader teams and could unnecessarily expose sensitive information. Channels are for work-related topics accessible to multiple members, whereas DMs maintain confidentiality.

KEY TAKEAWAY
Channels are ideal for collaborative, persistent conversations involving multiple stakeholders (Option B), while DMs are better for private, temporary, or small-group communications (Options A, C, D). The choice depends on the audience, purpose, and longevity of the discussion.

Reference: Slack's Communication Guidelines.

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.