Salesforce-Slack-Administrator Salesforce Certified Slack Administrator Exam Questions and Answers

Slack best practices for organized workspaces state:

"Establishing and enforcing naming conventions helps members easily identify the purpose of a channel at a glance and maintain workspace organization."

Apps (A) aren't necessary for simple naming. Asking for descriptions (B) is unreliable. Spreadsheets (C) are cumbersome and not visible at channel creation.

(Reference: Slack Administration Study Guide - Best Practices for Channel Naming)

===========

—

Slack requires:

"Enterprise Grid must use an identity provider (IdP) to manage authentication via SSO before users can sign in. SSO must be configured first for member access."

Options A and B bypass the necessary authentication process and would create user confusion later. Downgrading to Business+ (C) defeats the purpose of deploying Enterprise Grid.

(Reference: Slack Administration Study Guide - Preparing Identity Management for Enterprise Grid)

According to Slack's official documentation:

"Channel Managers can rename and archive channels, convert public channels to private (but not vice versa), and add/manage other Channel Managers."

They cannot restore deleted channels (B, D) or manage user roles in the org-wide sense (C).

(Reference: Slack Administration Study Guide - Channel Manager Role Capabilities)

===========

—

Since Preethi needs access to multiple channels but only for a limited time:

"A Multi-channel Guest is the best choice when someone needs access to more than one channel but does not need full member access across the workspace. You can also set an expiration date for their access."

Single-channel Guest would be too limiting, and full Member access would provide more access than necessary, posing a security risk.

(Reference: Slack Administration Study Guide - Managing Guest Access)

===========

—

Slack recommends:

"Channel names should follow consistent naming conventions and use hyphens between words, e.g., help-finance for a help-related finance channel."

Option A incorrectly reverses prefix order. Option B uses incorrect formatting. Option D misuses the prefix format as well.

(Reference: Slack Administration Study Guide - Channel Naming Conventions)

===========

—

According to Slack’s best practices:

"Claim your domains as soon as possible. This process is not retroactive — workspaces created before claiming domains will continue to exist independently unless manually migrated."

Thus, prompt domain claiming ensures better control and prevents users from unintentionally creating ungoverned workspaces.

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

===========

—

Using Workflow Builder is the best way to:

"Automatically send onboarding messages when users join a channel, providing them with key guidelines like how to use Slack appropriately without requiring manual monitoring."

This automates onboarding at scale and reduces Nicole's workload as hiring ramps up.

(Reference: Slack Administration Study Guide - Onboarding Best Practices and Workflow Automation)

===========

—

Slack’s guidance for handling inactive channels states:

"Archiving a channel preserves its content and history, allowing it to remain searchable without accepting new posts."

Deleting (A) would permanently remove the content. Renaming or limiting posting (C, D) are not standard clean-up procedures for inactive channels.

(Reference: Slack Administration Study Guide - Channel Lifecycle Management)

Slack Enterprise Grid best practices emphasize:

"Assigning the right Workspace Owners and Admins for each workspace is critical for maintaining ease of administration, clear governance, and efficient management of channels, members, and policies."

While minimizing multi-workspace channels (A) and considering culture (B) are important, selecting strong admin leadership (D) has the most direct impact on administrative efficiency. Frequent workspace switching (C) does not impact administrative setup directly.

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

===========

—

Slack recommends using public channels for community-building and location-specific discussions:

"Public channels allow easy discoverability and participation by members who might also be interested, even if they aren't part of the initial group."

DMs (A, C) are not scalable or discoverable. Slack Connect (B) is for external collaboration, not internal teams.

(Reference: Slack Administration Study Guide - Best Practices for Organizing Community Channels)

According to Slack’s official SCIM documentation:

"Deactivating a user in the identity provider (IdP) automatically deactivates the user’s Slack account through SCIM provisioning."

This ensures the Workspace Admin is promptly deactivated across the Enterprise Grid without needing manual action in Slack itself. Options A, C, and D are manual or inefficient approaches when SCIM is available.

(Reference: Slack Administration Study Guide - SCIM Provisioning and Lifecycle Management)

===========

—

Slack's official administration documentation confirms that when integrating Slack with an external IdP like Google Workspace, the correct method is to set up SAML-based SSO (Single Sign-On).

"You can configure SAML-based SSO with Slack to manage access via your IdP. When transitioning from username/password to SSO, you'll need to send out binding emails to link existing Slack accounts with the IdP profiles."

Google Workspace supports SAML 2.0 standard integration with Slack, and the binding process ensures existing users' Slack accounts are properly connected to their new IdP credentials.

Options A and C are incorrect because Slack natively supports Google Workspace SAML without needing a custom SAML setup, and option B incorrectly suggests setting up a new workspace, which is unnecessary.

(Reference: Slack Administration Study Guide - Integrations and Authentication Management)

===========

—

Slack defines "By Request" access as:

"A workspace or channel is visible to all users, but users must request to join, and Admins or Owners must approve each request."

This model fits Jorge’s need for visibility plus control over membership approval.

(Reference: Slack Administration Study Guide - Workspace Access Levels)

Slack's best practice for controlling fragmentation of discussions is:

"Restrict who can create public and private channels to Workspace Admins and Owners to maintain governance and reduce channel sprawl."

This ensures that projects stay visible in agreed-upon channels and minimizes unnecessary duplication.

(Reference: Slack Administration Study Guide - Channel Management Governance)

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)

===========

—

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)

===========

—

When engagement in public channels drops, Slack recommends education and re-engagement campaigns like hosting a “Slack day” to showcase best practices.

Slack documentation highlights:

"Slack Days are opportunities to encourage better usage patterns, provide learning sessions, and reinforce the importance of open communication through public channels."

Option A and D focus on short-term fixes and notifications, not improving behavior sustainably. Option B alone is not a complete strategy.

(Reference: Slack Administration Study Guide - Driving Adoption and Maintaining Engagement)

To define Slack’s success, it's essential to tie usage to business outcomes and improved productivity — not just technical setup or user counts.

Slack documentation recommends:

"Engage business units to identify opportunities where Slack has improved workflows, collaboration, or response times, and measure these against baseline expectations."

This makes the success conversation focused on value and business impact rather than technical completeness or adoption rates alone.

(Reference: Slack Administration Study Guide - Defining Success and ROI with Slack)

===========

—

The most efficient method to ensure all users are automatically added is:

"Make the workspace a default workspace for the Enterprise Grid organization. This way, all current and future members will automatically be added without manual intervention."

Syncing IdP groups (Option D) could work but requires additional setup complexity and group management.

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

===========

Slack recommends:

"Using SCIM provisioning combined with IdP group mapping allows organizations to efficiently manage large groups of users and assign roles based on IdP groups."

This way, you automate role assignment (faculty as Workspace Admins) while onboarding users. Options A and D don’t promote users automatically. Option C is less efficient compared to pre-provisioning via SCIM and group mapping.

(Reference: Slack Administration Study Guide - SCIM Provisioning and IdP Group Mapping)

===========

—

The proper course of action involves:

Deleting the file through an integrated Data Loss Prevention (DLP) solution.

Reviewing access through the Audit Logs API.

Slack documentation confirms:

"A DLP integration allows detection and remediation (e.g., deletion) of sensitive files or messages. The Audit Logs API provides detailed logs of user activity, including file downloads."

Mobile Device Management (MDM) focuses on device security, not file tracking, and EKM controls encryption but doesn't show file download actions.

(Reference: Slack Administration Study Guide - Security and Compliance - Data Loss Prevention and Audit Logs)

===========

—

In the Slack Business+ plan, to meet compliance requirements where deleted files must remain discoverable, you must set file retention to:

"Keep all files, including deleted files."

This ensures that even after a user deletes a file, it remains accessible for auditing and compliance purposes. Simply keeping files (B) does not guarantee deleted files are retained. Options involving "for a set number of days" (C, E) would risk data loss after the timeframe expires, and D (all file versions) focuses on version history, not deletion recovery.

(Reference: Slack Administration Study Guide - File Retention and Compliance Settings)

===========

—

Slack EKM guidelines specify:

"If sensitive information is exposed improperly (for example, shared in the wrong channel), you can revoke the encryption key, making that content permanently inaccessible."

Guests (A) or contractors in Slack Connect (B) are expected collaboration contexts and do not warrant revoking keys unless data leakage happens.

(Reference: Slack Administration Study Guide - Enterprise Key Management (EKM) Operations)

===========

—

Slack recommends organizing discussions into appropriate channels for clarity and relevance:

"Questions or discussions about specific projects should happen in project-related channels to maintain topic focus and ensure all relevant stakeholders can view and contribute."

#general should be reserved for organization-wide announcements or broad discussions, not for project-specific questions. DMing individuals (A, B) bypasses team collaboration. Deleting the message (C) is unnecessarily punitive.

(Reference: Slack Administration Study Guide - Best Practices for Channel Organization)

—

In Slack Enterprise Grid, a Workspace Admin is the correct role for someone managing settings and guest invitations for a specific workspace.

Slack documentation says:

"Workspace Admins can manage workspace-level settings, invite and manage guests, and perform administrative tasks for their designated workspace."

Assigning Frank as a Workspace Admin gives him the necessary permissions to manage the workspace without granting organization-wide control (which is reserved for Org Admins and Primary Org Owners). Options like Member or Multi-Channel Guest do not have the needed permissions.

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

===========

—

According to Slack Enterprise Grid documentation:

"To allow users to integrate external tools into workflows, admins must enable steps from apps and allow workflows to include webhook triggers."

Also,

"Enabling Workflow Builder and allowing users to create workflows (except Guests) ensures flexibility."

While A (App Managers) grants permission to approve apps, it is not needed for creating workflows. Channel emails (C) are unrelated. Workflow creation policy (E) is important too but the critical steps for app usage and webhook integration are B and D.

(Reference: Slack Administration Study Guide - Workflow Builder with External Integrations)

—

For ongoing external data archiving and retrieval:

"Slack recommends using a third-party eDiscovery or archiving app to pull Slack data and store it securely in a separate data warehouse or compliant system."

Corporate exports (Option A) are manual and not continuous, retention policies (Option B) keep data inside Slack, and DLP (Option C) manages risk but not long-term archiving externally.

(Reference: Slack Administration Study Guide - Data Governance and eDiscovery Options)

Slack’s app management guidelines advise:

"Before approving an app, you should review its compliance with your organization's data security policies and understand which external services and APIs the app communicates with."

Availability in the Slack App Directory (A) doesn’t guarantee security compliance. Whether the app connects with your HR system (D) is helpful but not a core initial security evaluation criterion.

(Reference: Slack Administration Study Guide - App Review and Security Considerations)

===========

—

Slack recommends using Workflow Builder to:

"Trigger onboarding workflows automatically when employees join channels, and use custom forms to collect consistent information and reduce unnecessary communication."

Inviting new hires as Single-Channel Guests (Option B) is not relevant because they are expected to have full access pre-onboarding.

(Reference: Slack Administration Study Guide - Automating Onboarding with Workflows)

===========

—

Slack documentation for Enterprise Grid states:

"Org Owners and Org Admins can enable workspace creation requests via Org Settings, making the process efficient and standardized."

Posting requirements (B) is not a controlled or actionable system. DM requests (C) are informal and untrackable. Workflows (D) are helpful, but Slack has built-in support for workspace creation requests through Org Settings, which is more efficient.

(Reference: Slack Administration Study Guide - Managing Workspace Creation on Enterprise Grid)

===========

—

Slack best practices state:

"If channel content needs to become more sensitive or confidential, converting a public channel to private helps control access to information."

Low membership (B) or duplicate conversations (C) are not valid reasons. Notification preference (A) does not relate to confidentiality.

(Reference: Slack Administration Study Guide - Guidelines for Converting Channels)

===========

—

Slack recommends for external collaboration:

"Use Slack Connect to collaborate with external partners in shared channels rather than relying on guest accounts, especially for long-term relationships."

Guests (A, C) require manual account management. A new Slack workspace (D) would fragment communication unnecessarily.

(Reference: Slack Administration Study Guide - Using Slack Connect for External Collaboration)

===========

—

Workspace Owners and Admins can:

"Remove any custom emoji via the 'Customize Slack' page, ensuring that inappropriate or unwanted emoji are promptly deleted."

Option A disables all custom emoji creation but doesn't address removing a specific emoji. Option B incorrectly suggests Brian (a non-admin) can delete it. Option D is incorrect — deletion is fully possible for Admins.

(Reference: Slack Administration Study Guide - Managing Custom Emoji and Content Moderation)

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)

===========

—

Slack's official analytics guidelines recommend:

"The average number of active days per user is a strong measure of engagement and adoption."

Number of DMs (A) focuses only on private messaging, not overall adoption. Channel/workspace membership (B) doesn't measure activity. New workspace creation (D) is not typically relevant to students and is often disabled.

(Reference: Slack Administration Study Guide - User Activity Analytics)

===========

—

On the Standard plan (and higher tiers), Slack allows:

"Unlimited app integrations, meaning you can install as many apps from the Slack App Directory or custom-built apps as needed."

There are no integration limits beyond any practical workspace-specific guidelines.

(Reference: Slack Administration Study Guide - Slack Pricing Plans and Feature Comparisons)

===========

—

Slack recommends:

"Before finalizing your Enterprise Grid design, survey teams to understand how they collaborate, where informal knowledge networks exist, and what natural groupings of people and work already exist."

Migrating before design (A) is premature. SSO review (C) is important but unrelated to channel and workspace structure design. Champions networks (D) are helpful for rollout, but not initial design.

(Reference: Slack Administration Study Guide - Planning Your Enterprise Grid Design)

===========

—

Slack Enterprise Grid provides an Org-level Members analytics section where you can view and export detailed information about all users, including guest accounts.

"Org Admins and Org Owners can export member lists from the Org analytics dashboard, including guest account details like type (single-channel or multi-channel), status, and associated workspaces."

Gathering from each workspace (A) is inefficient and manual. Exporting from the Export Data tab (D) relates to message and file exports, not member data. Opening a ticket with Slack (B) is unnecessary for this standard administrative task.

(Reference: Slack Administration Study Guide - Org Analytics and Member Exports)

===========

—

Slack recommends for sensitive or confidential projects:

"An 'Invite Only' workspace allows Org Admins or Workspace Owners to control membership, ensuring sensitive topics remain private until disclosure is appropriate."

Hidden (C) conceals the workspace name, but Invite Only (D) is the correct choice for manually controlling access during sensitive phases.

(Reference: Slack Administration Study Guide - Workspace Access Management)

Two critical elements in Change Management are understanding user needs and promoting solutions that fit their workflows.

• Running a campaign promoting Slack's mobile app addresses their need for mobility. Slack documentation notes:

"Promoting the Slack mobile app to teams that are highly mobile ensures they remain connected to important communications and workflows."

• Surveying the Sales team will help prioritize relevant integrations and workflows based on real-world challenges they face:

"Understanding end-user pain points is crucial for designing Slack solutions that users find genuinely helpful."

Simply installing the Salesforce app without understanding their needs may not be effective, and using threats (option B) is contrary to Slack’s recommended adoption strategies.

(Reference: Slack Administration Study Guide - Driving Slack Adoption and Change Management)

===========

—

Slack recommends:

"When social channels overwhelm the workspace and impact findability of work-related content, creating a separate workspace for social and community discussions helps maintain focus and discoverability."

Simply deleting channels (B, D) risks damaging community culture. Making channels multi-workspace (A) doesn’t solve workspace clutter — it just duplicates visibility.

(Reference: Slack Administration Study Guide - Workspace Design for Scalability and Discoverability)

===========

—

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)

===========

—

Slack recommends setting a global policy and making specific exceptions where needed:

"Setting a shorter global retention policy and then setting exceptions to keep important messages longer in specific channels gives you flexibility while controlling overall data retention."

Default settings (B) would not provide an organization-wide policy. Allowing members to manage private channel retention (C) can be risky. Setting public retention short and private channels to everything (D) doesn't align with best practices for most businesses.

(Reference: Slack Administration Study Guide - Message Retention and Exceptions)

===========

—

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)

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

===========

—

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 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’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 user group functionality explains:

"When a user group is @mentioned, all members of the user group are notified, making it easy for others to reach all members at once for questions or updates."

Option A is misleading because visibility of user groups depends on workspace settings. B and C are inaccurate — external users cannot be added, and users cannot add themselves to user groups.

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

Slack documentation states:

"To add Multi-Channel Guests, workspace admins or owners should invite them via the workspace menu, and if necessary, route the requests through an approval process."

Adding them as full members (B) would grant excessive access. DMing Org Owners (D) is inefficient and informal. @mentioning (C) is not the standard request process.

(Reference: Slack Administration Study Guide - Managing Guest Accounts on Enterprise Grid)

===========

—

When designing an Enterprise Grid deployment, Slack recommends a thoughtful, structured approach.

According to Slack’s Enterprise Grid best practices:

"Develop a clear business case outlining why a strategic design is important, addressing key goals such as minimizing noise and maximizing collaboration.

Define success criteria and key design principles early, and work with your Slack account team to evaluate different workspace design models."

The idea is to ensure leadership understands the need for a strategic design and that the team has clear success metrics. C and E describe possible implementation strategies but jump ahead without a strategic foundation. D (surveying users) is helpful later but not the first step.

(Reference: Slack Administration Study Guide - Enterprise Grid Workspace Design Best Practices)

===========

—

Slack recommends using multi-workspace private channels to manage sensitive information securely across workspaces.

"Multi-workspace private channels allow members from multiple workspaces to securely collaborate, making them ideal for department-specific discussions and sensitive topics."

Public channels (A) are inappropriate due to the sensitivity of the HR discussions. Private channels limited to one workspace (C) would restrict access. Group DMs (D) are not scalable or organized for ongoing collaboration.

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

===========

—

Slack recommends using Slack Connect for external collaboration across companies.

According to Slack Connect official guidelines:

"Slack Connect lets you securely collaborate with external organizations in channels or direct messages, without needing to add external users as guests in your workspace."

Rather than creating guest accounts (A) or modifying your IdP (C), the correct and scalable method is setting up Slack Connect channels. Option D (setting up a separate Slack workspace) is not necessary and would complicate governance.

(Reference: Slack Administration Study Guide - Slack Connect Best Practices)

===========

—

Slack Clips are recommended for asynchronous communication:

"Slack Clips allow users to record video, screen shares, and voice messages directly in Slack, which teammates can view at their convenience."

Starting a Huddle (C) is synchronous and not asynchronous. Recording outside Slack (B) and importing is less efficient. Public channels limited to specific workspaces (D) won’t reach the entire org unless users join manually.

(Reference: Slack Administration Study Guide - Using Clips for Asynchronous Communication)

===========

—

Slack’s Enterprise Grid security recommendations state:

"Org Admins can remotely sign a member out of all sessions (desktop, mobile, web) via the admin dashboard to immediately prevent further access without deactivating the user."

Asking the user (A) is unreliable because they lost the device. Deactivation (B) is extreme if the device may be recovered. Workspace-level action (D) is insufficient for org-wide risk.

(Reference: Slack Administration Study Guide - Managing Lost or Compromised Devices)

===========

—

Slack’s Workflow Builder is designed to:

"Allow non-developers to automate routine tasks without writing code, support integrations with apps and services for enhanced workflows, and provide templates that users can customize."

While developers can use Workflow Builder, it is primarily aimed at non-technical users; developers usually prefer building custom apps or using Slack APIs.

(Reference: Slack Administration Study Guide - Workflow Builder Overview)

===========

—

Slack's best practice for Enterprise Grid states:

"You can use your identity provider (IdP) groups to automatically provision users into the appropriate workspaces, ensuring that workspace membership reflects organizational structure."

Manual additions by HR (A) or managers (C) are error-prone and inefficient. User groups (D) control notification settings inside workspaces, but not workspace membership.

(Reference: Slack Administration Study Guide - Managing Workspace Membership via IdP Groups)

===========

—

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's recommendation for secure external collaboration is:

"Single-Channel Guests are ideal for providing external users with access to only one channel, maintaining strict control over permissions and access."

Multi-Channel Guests (B, C) grant access to multiple channels, which is unnecessary and riskier. Creating a new workspace (A) adds administrative burden and is unnecessary for one project.

(Reference: Slack Administration Study Guide - Managing External Users via Guest Roles)

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)