Free Salesforce Slack Developer Practice Test Questions (2026)

Explanation

The slack login command is used to authenticate the Slack CLI with a Slack workspace. When executed, it initiates a login flow (typically via a verification code or browser-based authentication) that authorizes the CLI to act on behalf of the developer for that workspace. The official Slack CLI documentation lists slack login with the example $ slack login, confirming it as the correct command for authenticating the CLI. This makes option B the correct answer.

Why the other options are incorrect:

A. slack auth – While the Slack CLI does have a slack auth command, it is used to "Add and remove local team authorizations" after login, not to perform the initial authentication with a workspace. It manages stored authorization credentials rather than initiating the login flow itself.

C. slack connect – There is no slack connect command in the Slack CLI. This is not a valid command; the correct command for CLI authentication is slack login.

D. slack workspace add – There is no slack workspace add command in the Slack CLI. This is not a valid command. Workspace selection and authorization are handled through slack login and slack auth.

Reference:

Slack Developer Documentation — Slack CLI command reference, listing slack login as "Log in to a Slack account" and providing the example $ slack login.

Explanation

Bolt is Slack's official higher-level framework for building Slack apps. It abstracts away much of the boilerplate involved in working directly with the Slack API — such as verifying requests, parsing event payloads, routing events to the correct handlers, and calling Web API methods — so developers can focus on app logic. Bolt provides built-in listeners (for events, messages, commands, actions, views), middleware support, and simplified authorization handling across JavaScript, Python, and Java. This makes option B the correct answer.

Why the other options are incorrect:

A. A database for storing messages – Bolt is not a database. It is a development framework. Message storage is not part of Bolt's functionality; developers who need persistence use Slack's Datastores feature, external databases, or other storage solutions.

C. A Slack Marketplace billing tool – Bolt has nothing to do with billing or the Slack Marketplace. It is purely a framework for building apps that interact with Slack's APIs and events.

D. A CSS framework for Block Kit – Bolt is not a CSS or UI framework. Block Kit is Slack's UI framework for building message layouts and modals, and it is entirely separate from Bolt. Bolt handles the logic and event handling side of app development, while Block Kit handles the visual presentation.

Reference:

Slack Developer Documentation — Bolt framework overview, describing Bolt as a framework that simplifies building Slack apps by handling event listening, request verification, and API calls.

Explanation

App-level tokens are used to authenticate at the app level rather than on behalf of a user or bot, and they are required for features like Socket Mode and the apps.connections.open method. Slack prefixes app-level tokens with xapp-. These tokens are generated in the app configuration under the "Basic Information" section and are distinct from bot tokens and user tokens. This makes option B the correct answer.

Why the other options are incorrect:

A. xoxb – The xoxb- prefix identifies bot tokens, which authenticate a bot user within a workspace. Bot tokens are used for calling Web API methods as the bot, not for app-level operations like opening a Socket Mode connection.

C. xoxp – The xoxp- prefix identifies user tokens, which authenticate on behalf of a specific user and carry that user's permissions. User tokens are unrelated to app-level authentication and Socket Mode connections.

D. bearer – "Bearer" is not a token prefix; it is an HTTP authorization scheme (e.g., Authorization: Bearer ). Slack does not issue tokens with a bearer prefix. It describes how a token is transmitted in a request header, not the token type itself.

Reference:

Slack Developer Documentation — Tokens overview, describing token types and prefixes including xoxb- (bot), xoxp- (user), and xapp- (app-level).

Explanation

Slack's standard Bolt starter templates and the Slack CLI support Bolt for JavaScript and  Bolt for Python out of the box. When you use slack create to scaffold a new app, the CLI presents official templates for these two languages, and the Slack CLI's built-in tooling (such as slack run and slack deploy) is designed around them. Bolt for Java exists as an official framework, but it is not part of the standard CLI starter template flow. This makes option B the correct answer.

Why the other options are incorrect:

A. Ruby and Go – Neither Ruby nor Go has an official Bolt framework maintained by Slack. Community libraries exist for both languages, but they are not part of the standard Bolt starter templates and are not supported by the Slack CLI scaffolding workflow.

C. C# and PHP – Slack provides no official Bolt framework for C# or PHP. These languages are not included in the standard starter templates, and no first-party support exists for them in the Bolt ecosystem.

D. Rust and Swift – Neither Rust nor Swift has an official Bolt framework from Slack. Community projects may exist, but they are not part of the standard Bolt starter templates or the Slack CLI's supported languages.

Reference:

Slack Developer Documentation — Slack CLI and Bolt getting started guides, showing official starter templates for Bolt for JavaScript and Bolt for Python.

Explanation

The  Block Kit Builder is Slack's official visual tool for designing and previewing Block Kit layouts before adding them to code. It provides a drag-and-drop interface where developers can compose blocks (sections, dividers, inputs, actions, etc.), see a live preview of how the message or modal will render in Slack, and then copy the generated JSON payload directly into their app code. This makes option A the correct answer.

Why the other options are incorrect:

B. Slack Studio – There is no official Slack tool called "Slack Studio." This is not a real Slack product or development tool; it appears to be a fabricated name.

C. Bolt Designer – There is no official tool called "Bolt Designer." Bolt is Slack's app development framework, but it does not include a visual design tool by this name.

D. Surface Editor – There is no official Slack tool called "Surface Editor." While Slack uses the term "surfaces" to describe where content appears (messages, modals, Home tabs, canvases), no visual editing tool by this name exists.

Reference:

Slack Developer Documentation — Block Kit Builder, described as an interactive tool for prototyping and previewing Block Kit layouts before integrating them into app code.

Explanation

The slack app settings command opens an app's configuration page in a browser, allowing developers to manage settings such as permissions, OAuth scopes, event subscriptions, and interactivity. This is part of the slack app command group, which handles installing, uninstalling, listing teams, and managing app settings. This makes option A the correct answer.

Why the other options are incorrect:

B. slack config open – There is no slack config open command in the Slack CLI. Configuration-related tasks are handled through slack app settings and the broader slack app command group, not a config open subcommand.

C. slack edit – There is no slack edit command in the Slack CLI. Editing app properties is done through slack app settings (which opens the browser-based configuration page) or by syncing a manifest with slack sync.

D. slack dashboard – There is no slack dashboard command in the Slack CLI. While Slack provides a web-based dashboard for app management, there is no CLI command by this name.

Reference:

Slack Developer Documentation — Slack CLI command reference, listing slack app as the command group for installing, uninstalling, and listing teams with the app installed, and describing slack app settings as the way to open and manage an app's configuration.

Explanation

The full list of available Slack Web API methods is documented at api.slack.com/methods. This is Slack's official API reference, where every Web API method is listed and organized by category (e.g., conversations, users, files, chat, reactions). The page content confirms it is the "Methods" reference page with a searchable list of methods, their descriptions, and family groupings. Each method page includes its URL, required and optional arguments, token types, scopes, and example responses. This makes option A the correct answer.

Why the other options are incorrect:

B. docs.slack.dev/pricing – This is not a valid reference for API methods. The page does not host API documentation; it is unrelated to the Web API method reference. Developers looking for the methods list would not find it here.

C. slack.com/legal – This is Slack's terms and policies page, containing legal documentation such as terms of service, privacy policies, and compliance information. It has nothing to do with the Web API method reference.

D. app.slack.com/methods – This URL returns a 404 error and is not a valid Slack documentation endpoint. The app.slack.com domain is used for the Slack client application, not for hosting API documentation. The correct location for the methods list is api.slack.com/methods.

Reference:

Slack Developer Documentation — Web API methods reference, the official index of all available Web API methods organized by category (api.slack.com/methods).

Explanation

The slack create command scaffolds a new Slack app project from a starter template. When executed, the Slack CLI prompts the developer to choose a template (such as a Bolt for JavaScript or Bolt for Python starter), a name for the project, and a destination directory, then generates a complete project structure ready for development. The official Slack CLI command reference lists slack create as "Create a new Slack project," and the examples show $ slack create for creating a new Slack app. This makes option C the correct answer.

Why the other options are incorrect:

A. slack init – The slack init command is used to initialize an existing project to work with the Slack CLI, not to scaffold a brand-new project from a template. It adds the necessary configuration to a project that already exists.

B. slack new – There is no slack new command in the Slack CLI. This is not a valid command; the correct command for scaffolding a new project from a template is slack create.

D. slack bootstrap – There is no slack bootstrap command in the Slack CLI. This is not a valid command. Project scaffolding is handled by slack create.

Reference:

Slack Developer Documentation — Slack CLI command reference, listing slack create as "Create a new Slack project" and providing the example $ slack create for creating a new Slack app.

Explanation

Socket Mode requires an  app-level token to establish the WebSocket connection with Slack. Specifically, the app must call the apps.connections.open method using an app-level token, which is prefixed with xapp-. This token authorizes the app to open a Socket Mode connection and is generated in the app's configuration under the "Basic Information" section with the connections scope. Without an app-level token, the app cannot initiate a Socket Mode session. This makes option B the correct answer.

Why the other options are incorrect:

A. Bot token only – A bot token (prefixed with xoxb-) is used to call Web API methods as the bot user, but it cannot open a Socket Mode connection on its own. While a bot token is typically needed alongside an app-level token for the app to function, it is the app-level token that is specifically required to initiate Socket Mode.

C. Legacy token – Legacy tokens are deprecated, older-generation tokens that Slack no longer issues or recommends. They are not the required token type for Socket Mode, and Slack has moved to the app-level token model for this purpose.

D. No token is required – This is incorrect. Socket Mode requires authentication via an app-level token. Slack will not accept a WebSocket connection without a valid app-level token, so a token is mandatory.

Reference:

Slack Developer Documentation — Socket Mode overview, stating that an app-level token with the connections scope is required to call apps.connections.open and establish a Socket Mode connection.

Explanation

The official way to install the Slack CLI on macOS and Linux is to run the installation script hosted by Slack: curl -fsSL https://downloads.slack-edge.com/slack-cli/install.sh | bash. This script downloads and installs the Slack CLI binary to the appropriate location on the system. Slack's official documentation provides this exact command for macOS/Linux installation, making option B the correct answer.

Why the other options are incorrect:

A. npm install -g slack-cli – The Slack CLI is not distributed as an npm package under the name slack-cli. While Bolt for JavaScript is installed via npm, the CLI itself is a standalone binary installed via the shell script, not through npm.

C. brew install slack – While Homebrew is a common package manager for macOS, brew install slack installs the Slack desktop application, not the Slack CLI. The CLI is not installed through this Homebrew formula under this name.

D. pip install slack-cli – The Slack CLI is not a Python package and cannot be installed via pip. While Bolt for Python is installed via pip install slack_bolt, the CLI itself is a separate standalone tool installed via the shell script.

Reference:

Slack Developer Documentation — Slack CLI installation guide, providing the curl -fsSL https://downloads.slack-edge.com/slack-cli/install.sh | bash command for macOS and Linux.