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

Slack's immediate response guidance states:

"If SCIM provisioning is unavailable, Workspace Admins should manually deactivate users through Slack settings to immediately prevent access."

Changing the email (A) is messy and not recommended. Making #general read-only (B) doesn't prevent broader access. Contacting support (D) is useful, but not immediate enough for stopping access.

(Reference: Slack Administration Study Guide - Managing User Access in Case of SCIM Outage)

===========

—

Slack encourages using threads to keep conversations organized and prevent clutter in busy channels.

Official Slack documentation says:

"Threads help organize conversations around specific messages, allowing multiple discussions to happen simultaneously within a single channel without causing confusion."

While thanking or quick responses (Option B) can also be done in threads, the primary reason for using threads is to manage multiple discussions efficiently.

(Reference: Slack Administration Study Guide - Best Practices for Channel Communication and Threading)

===========

—

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)

User groups provide two major benefits according to Slack official documentation:

"User groups allow you to quickly notify an entire group of people with an @mention (e.g., @designers, @managers)."

"They can also be configured so that new users assigned to the group are automatically added to default channels, streamlining onboarding."

They do not control channel management permissions (B) or app integrations (E), nor do they affect workspace analytics permissions (C).

(Reference: Slack Administration Study Guide - Managing User Groups)

===========

—

To ensure that all users have seamless access to Google Calendar within Slack:

"Enable domain-wide authentication for Google Calendar in Slack. This ensures the app is automatically installed and authorized for all users without requiring manual setup."

Pre-approving (C) still requires individual installation by users. Posting instructions (A) is manual and inconsistent. Using Admin API (D) helps manage app requests but does not guarantee seamless access.

(Reference: Slack Administration Study Guide - Managing Apps and Domain-Wide Authentication)

SCIM provisioning offers two major benefits:

"Automatically deactivating user accounts when they are deactivated in the identity provider (IdP)."

"Pre-provisioning Multi-Channel and Single-Channel Guests in Slack."

SSO (Option B) relates to authentication, not provisioning. Automatic account creation upon login (Option D) is tied to Just-in-Time (JIT) provisioning with SSO, not SCIM.

(Reference: Slack Administration Study Guide - SCIM Provisioning Benefits)

===========

—

Slack recommends:

"Workspace Admins are ideal for handling workspace-specific tasks such as member management, approval of apps, and settings management for individual business units."

Assigning Org Admins (B) or Org Owners (D) grants broader permissions than necessary and increases risk. Creating a channel for managing requests (C) does not delegate actual admin permissions.

(Reference: Slack Administration Study Guide - Delegating Workspace-Level Administration)

===========

—

The best practice outlined in Slack Enterprise Grid documentation:

"Enable workspace creation requests, so users can request new workspaces that will be routed to Org Admins via an internal channel for review and approval."

This approach scales better for high-volume requests, allowing multiple admins to track and approve them efficiently from a centralized channel, rather than relying on manual direct messages.

(Reference: Slack Administration Study Guide - Enterprise Grid Workspace Management)

===========

—

Slack automation for app approvals suggests:

"Admins can define conditional rules to automatically approve or restrict apps and integrations and notify requesters of the approval status, while creating rules both at the org and workspace level for flexibility."

Listing trusted members (B) does not automate the process. Cost-based approvals (C) are too narrow and risky.

(Reference: Slack Administration Study Guide - Automating App and Integration Approvals)

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)

===========

—