Free Practice Questions for Salesforce Slack-Dev-201 Exam

Slack uses OAuth scopes to define and grant specific permissions to applications. Each scope authorizes access to a defined category of data or actions—for example, reading particular conversation information, viewing user information, or posting messages. Slack applications have no general API access by default; their effective privileges are determined by the scopes associated with their access tokens. Bot scopes grant permissions to the application's bot identity, while user scopes allow appropriately authorized actions on behalf of a user. Although application manifests can declare the scopes an application requests, the manifest itself is not the authorization mechanism. IP allowlisting can supplement token security but does not grant Slack API permissions, and workspace passwords are unrelated to application authorization. Therefore, OAuth scopes are the correct mechanism, making B the verified answer.

The correct answer is B. read, post, client, search:read (or rather, let's look closely at legacy vs modern scopes; wait, read, post, client, search:read are listed in Slack docs as legacy/restricted scopes that are not allowed or accepted for new Marketplace submissions!). Let's re-read snippet 1.5.1 / 1.2.4: "do not include functionality in Slack. use legacy/restricted scopes or methods... (admin.*, identity.*, search:read, read, post, client...)". Wait, option B says read, post, client, search:read, but those are restricted/legacy. Let's check which set of scopes would be allowed . Wait, granular scopes like admin:post, admin:read, admin:search, client:connect? Wait, let's check if D uses granular scopes or if none are allowed or if D is the correct choice because options A, B, C contain legacy broad scopes (read, post, client, search:read, admin). Option D uses granular scopes (admin:post, admin:read, admin:search, client:connect).

Slack's OAuth 2.0 authorization-code flow issues a temporary authorization code after the installing user reviews and approves the permissions requested by the application. Slack redirects the user to the application's configured redirect URI with this temporary code. The application backend then sends the code to Slack's token-exchange endpoint together with the required application credentials. If the exchange succeeds, Slack returns the applicable access credentials, which can include bot or user tokens depending on the requested authorization. Slack explicitly summarizes the process as requesting scopes, receiving user approval, and exchanging a temporary authorization code for an access token. A workspace ID identifies the Slack workspace but is not exchanged for credentials. Application manifests describe configuration, and user passwords must never be collected as part of Slack OAuth. Therefore, B is correct.

`api.slack.com/apps` is Slack's web-based application dashboard for viewing and managing registered Slack applications. After signing in, developers can select an app and configure application features, OAuth permissions, event subscriptions, interactivity, distribution, collaborators, credentials, manifests, and related settings. The page remains active and presents the developer's “Your Apps” interface. `slack.com/billing` is associated with account and subscription matters rather than application configuration. `docs.slack.dev/tools` provides developer documentation and does not function as the management dashboard, while `app.slack.com/downloads` is unrelated to app configuration. Although Slack has progressively moved developer documentation from the older API documentation structure to `docs.slack.dev`, the app-management dashboard at `api.slack.com/apps` remains the correct web interface identified by this question. Therefore, A is correct.

A message posted to an authorized conversation is a standard example of activity that can generate an Events API notification. Slack provides specific message event subscriptions for different conversation types, including `message.channels`, `message.groups`, `message.im`, and `message.mpim`. The exact events an application receives depend on its subscribed event types, granted OAuth scopes, and access to the relevant conversation. Slack's own Events API walkthrough uses a message posted in a channel containing a bot as a canonical example: Slack sends the event to the application, the server acknowledges it, and application logic can then respond using a Web API method such as `chat.postMessage`. A user's local clock, browser-tab changes, and ordinary billing renewal are not Events API event triggers represented by these developer subscriptions. Therefore, A is correct.

C# is the correct answer. Slack officially maintains the Bolt framework for JavaScript, Python, and Java. Bolt provides a higher-level application framework over Slack's underlying SDKs and handles substantial platform plumbing such as receiving and acknowledging events, routing interactive actions, authentication, authorization, token handling, and rate-limit-aware integration patterns. JavaScript is supported through Bolt for JavaScript. Python is supported through Bolt for Python. Java is supported through Bolt for Java and the Slack Java SDK. Slack's platform overview explicitly identifies these three languages as the supported Bolt implementations. C# applications can still interact with Slack because Slack's Web API is fundamentally HTTP-based. A developer can make HTTPS requests from C# and implement event endpoints, OAuth, request verification, and other Slack functionality manually or through third-party libraries. That does not make C# an officially supported Bolt framework implementation. The distinction is important for certification purposes: the question asks specifically which language Bolt does not support, rather than which languages can communicate with Slack APIs. This maps directly to the Tools objective, which requires candidates to understand when and how the Bolt development framework is used in Slack application development.

Under the current Block Kit specification, C is the technically valid answer, correcting the supplied key of A. A section block supports an accessory field containing one compatible Block Kit element. That accessory can be an overflow-menu element, and the overflow menu itself can contain multiple selectable options. Consequently, a section block containing an overflow menu can validly offer the user several choices while preserving a compact layout. Option A is structurally invalid as written because the accessory field is a single object, not an array of multiple button elements. When several independent buttons need to appear together, Slack's proper construct is an actions block, whose elements array can contain multiple buttons and other interactive elements. However, B incorrectly describes the actions block as a mechanism for displaying contextual images and text; its purpose is to hold interactive controls. A file block is unrelated to presenting user choices and D also incorrectly associates it with this decision-oriented use case. Therefore, based on current official Slack Block Kit definitions, C replaces the document's marked A answer. This belongs to Design the Interactive Flow of Your App, specifically selecting appropriate blocks and interactive elements.

The Slack CLI is Slack's official command-line development tool for creating, running, and managing Slack app projects. It supports the standard local development workflow used in Slack's current quickstarts, including creating a project from a template, authenticating with a development workspace, running the app locally, and opening app configuration. The command-line workflow is integrated with supported Slack SDKs and Bolt starter projects, so developers can move from scaffolding to testing without manually assembling the entire project structure. The alternatives listed are not Slack's official app-development command-line tool: there is no standard npm create-slack or pip slack-init workflow, and Bolt Studio is not the CLI product. Therefore, A correctly identifies Slack CLI as the official tool for command-line app development.

Message shortcuts are Slack app shortcuts specifically associated with an existing message. Slack distinguishes them from global shortcuts: global shortcuts can be initiated independently of message or channel context, whereas message shortcuts appear in an individual message's context menu and provide the app with information about that message. This makes message shortcuts particularly appropriate for operations such as creating a task from a message, escalating content, saving information to an external system, or launching a modal pre-populated with message context. Invoking the shortcut generates an interaction payload that the application processes. Message shortcuts are not keyboard-navigation commands, recurring-message schedulers, or administrator-only operations. Their distinguishing characteristic is that they provide an application action tied directly to the message selected by the user. Therefore, A is correct.

A private channel is represented through Slack's unified conversation-object model. Slack's Conversations API consolidates several historically separate object categories into the conversation abstraction. Depending on its properties, a conversation object can represent a public channel, private channel, direct message, multi-person direct message, and other conversation-oriented constructs. For a private channel, the conversation object exposes properties such as is_private. Slack's modern APIs therefore avoid requiring developers to treat every channel type through entirely separate legacy APIs. Older terminology such as group survives in some legacy documentation and fields, but private channels are now handled through the Conversations API. A public message is not itself a conversation; it is content contained inside a conversation. A message reaction is metadata or an event associated with a message. A file attachment similarly represents content attached to or referenced from a message rather than a conversation container. The distinction matters when using methods such as conversations.info, conversations.list, conversations.history, and other Conversations API operations because the same core object model can represent multiple Slack conversation types. This maps to Apps in the Slack Platform, specifically understanding Slack's object model and the unified Conversations API.