Free Salesforce Slack-Dev-201 Practice Exam with Questions & Answers

Bolt is Slack's higher-level application framework for building Slack apps with common platform patterns already organized for developers. Rather than manually wiring every incoming event, interaction, Web API request, acknowledgment, and middleware concern, Bolt provides listener registration, context injection, utilities such as `say()` and `ack()`, and convenient access to Slack API clients. Official Bolt implementations are available for JavaScript, Python, and Java, each built around Slack's corresponding SDK capabilities. Bolt is not a message database, a Marketplace billing system, or a CSS framework for Block Kit. Block Kit is Slack's UI composition system, while Bolt is application-development infrastructure. Therefore, B accurately describes Bolt as a higher-level framework that simplifies event handling, interactivity, and calls to Slack platform APIs.

The `slack login` command authenticates the Slack CLI with a development workspace. During this process, the CLI guides the developer through authorization so subsequent commands can operate in the selected Slack environment. This is a prerequisite for common development tasks such as creating, running, and installing a Slack app through the CLI. Slack's quickstart documentation explicitly instructs developers to run `slack login` after installing the CLI and before starting the app-development workflow. The other options are not the documented authentication command: `slack auth`, `slack connect`, and `slack workspace add` do not perform the standard CLI login flow described by Slack. Therefore, B is correct because `slack login` is the supported command for connecting and authenticating the Slack CLI to a workspace.

C corrects the supplied document's marked answer of A. The customers described are separate businesses rather than multiple workspaces belonging to one Enterprise organization. Consequently, Enterprise organization distribution is not the correct model. Organization-ready apps are installed at the level of a single Enterprise organization and then granted access to selected workspaces belonging to that organization. They are not a distribution mechanism for unrelated customer organizations. Slack's current application-lifecycle guidance describes unlisted distributed apps—historically described as publicly distributed apps—as the correct architecture when an application needs to be installed in other customer workspaces without being publicly discoverable in the Slack Marketplace. After configuring OAuth and enabling distribution, the developer can provide the installation link specifically to selected customers. A single-workspace app cannot be installed in customers' independent workspaces. Marketplace distribution would maximize discoverability rather than keep installation restricted to the agency's customers. Therefore, the appropriate option from the supplied choices is C. Public app distribution, more precisely called unlisted distribution in current Slack documentation. This belongs to Distribute Your App, covering undistributed, unlisted distributed, Marketplace, and Enterprise organization distribution models.

Slack explicitly recommends applying the principle of least privilege when choosing OAuth scopes. An application should request only the minimum permissions required to perform its intended functionality. Every unnecessary scope expands the data or operations available to the application and therefore increases the potential impact of credential compromise, implementation defects, or inappropriate application behavior. Slack's security guidance recommends defining minimal scope sets and auditing requested permissions regularly. Marketplace guidance reinforces the same principle because users and administrators may reject applications that request excessive access to sensitive Slack data. Slack does not charge applications according to their number of scopes, and narrower scopes do not exist primarily to improve performance. Broad scopes have not simply been universally deprecated; rather, developers are expected to justify and minimize permissions. Therefore, B accurately captures Slack's security model and recommended application-design practice.

Among the supplied options, B is the intended answer because Slack's Web API is HTTP-based and Web API responses are JSON objects. Successful and failed responses contain a top-level Boolean `ok` property, together with method-specific fields or an `error` value. Many write methods also accept `application/json` request bodies. However, one technical correction is important: current Slack documentation explicitly states that the Web API is not a REST API. Slack describes it more precisely as a collection of HTTP RPC-style methods with endpoints such as `https://slack.com/api/METHOD_FAMILY.method`. Therefore, “REST with JSON” is not perfectly worded, but it is still the only defensible choice among A–D because SOAP/XML, GraphQL, and gRPC are incorrect. For current Slack terminology, “HTTP RPC-style methods with JSON responses” would be more precise.

`chat.postMessage` is Slack's standard Web API method for publishing a message to a conversation. The method accepts a `channel` identifier together with message content such as `text`, Block Kit `blocks`, or supported attachments. It requires the `chat:write` scope for bot or user tokens. Depending on the app's permissions and conversation membership, it can post to public channels, private channels, and supported direct-message conversations. Apps requiring the ability to post to public channels without joining them can request the additional `chat:write.public` scope. Slack's official Web API documentation identifies `chat.postMessage` as the primary method for sending messages. `messages.send`, `channel.write`, and `chat.create` are not valid Slack Web API equivalents for this operation. Therefore, A is correct.

The legacy Slack term group historically referred to what the modern platform calls a private channel. Slack's current Group object documentation explicitly directs developers to the Conversation object documentation for private channels and explains that older private channels were historically known as “private groups.” Modern Slack development uses the unified Conversations API. A conversation can represent a public channel, private channel, direct message, multi-person direct message, or other supported conversational surface. Developers can inspect properties such as is_private, is_im, and is_mpim rather than relying on older resource naming. A Group DM is instead represented as an MPIM and is conceptually different from a private channel. A direct message is a one-to-one conversation, while a User Group is an administrative grouping of workspace members used for functions such as mentions and organizational categorization. Therefore, D correctly translates the legacy term in the context of Slack API objects. This question maps to Apps in the Slack Platform, particularly the modern Conversations API object model and interpretation of legacy Slack documentation.

One of the strongest benefits of Slack app manifests is that application configuration becomes portable, reviewable, and reproducible. Slack explicitly recommends storing manifests in version-control systems such as GitHub, where collaborators can understand application setup and track configuration changes over time. A manifest can then be reused to create or configure apps consistently instead of manually reproducing settings through the web interface. This significantly reduces configuration drift between development, testing, and related application environments. A manifest is not the only mechanism for enabling bot functionality, does not eliminate OAuth authorization requirements, and does not automatically publish an application to the Slack Marketplace. Distribution and Marketplace publication remain separate lifecycle processes with their own requirements. Therefore, the version-controlled and repeatable configuration benefit described in B is precisely aligned with Slack's manifest documentation.

The `slack create` command is used to create a new Slack application project from a supported template. Slack CLI can prompt the developer to choose a starter project, or a template can be supplied directly, after which the command creates the local project directory and required project files. Slack's current quickstarts use `slack create` as the standard starting point for Bolt-based development in JavaScript or Python. This command is distinct from `slack run`, which executes the application locally, and from deployment or configuration commands used later in the lifecycle. `slack init`, `slack new`, and `slack bootstrap` are not the documented Slack CLI commands for scaffolding a new project. Therefore, option C correctly identifies the supported project-creation command.

Slack shortcuts provide explicit entry points that users can invoke to start application functionality. Slack supports two principal shortcut types: global shortcuts and message shortcuts. Global shortcuts can initiate functionality without requiring an existing message context, while message shortcuts are attached to individual messages and appear in the message context menu. When a shortcut is invoked, Slack sends an interaction payload to the application containing contextual information and a `trigger_id`, which can be used to open a modal or continue another interactive flow. Webhooks are message-delivery mechanisms rather than user action entry points. OAuth scopes define permissions, while manifests describe application configuration. Consequently, Shortcuts is the Slack feature specifically designed to let users invoke application actions from Slack UI locations.