Slack-Dev-201 Exam Questions Tutorials

Slack AI agents are built on the core Slack application platform rather than an entirely isolated development system. Slack's agent documentation describes Slack as particularly suitable for agent experiences because it already provides a conversational environment, Block Kit interaction model, multiple application surfaces, identity, permissions, and contextual information. The official Agent quickstart demonstrates an agent using familiar Slack application mechanisms such as Bolt, App Home, modals, direct messages, app mentions, reactions, and threaded messaging. Developers can therefore combine AI reasoning and external model frameworks with established Slack primitives for events, messages, interfaces, authentication, and Web API actions. Agent functionality may introduce specialized capabilities and scopes, but it does not replace the underlying Slack platform. Agents can also post and stream responses. Consequently, B is the technically correct answer.

Slack's current Marketplace review policy explicitly requires applications to request only scopes associated with functionality that reviewers can currently test. Developers should not request access for speculative or future features. Because the feature requiring files:read does not yet exist, the application should omit that scope from the present submission. Once the feature has been implemented and can be demonstrated to Slack reviewers, the developer should update the requested OAuth permissions and submit the modified application for review again. That makes C correct. Option B is incorrect because adding a materially new scope to a published Marketplace application cannot simply bypass review. Slack reviews both application functionality and the permissions required to implement it. Options A and D violate least privilege by requesting access before any production feature requires it. This is particularly important for files:read, which Slack currently classifies among scopes that can provide substantial access to workspace data and may therefore trigger enhanced review. The older term App Directory in the source question corresponds to today's Slack Marketplace. This belongs to Distribute Your App, with a strong relationship to security through scope minimization and Marketplace review governance.

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