Pass the Salesforce Developer Slack-Dev-201 Questions and answers with ExamsMirror

Slack's response_url provides a temporary callback mechanism that lets an application send additional responses after receiving a slash command or supported interactive-action payload. Current Slack documentation specifies that the URL can be used up to five times within 30 minutes after the application receives the original payload. That makes B the precise platform restriction. A response_url does not require the app to attach a bot or user OAuth token. Slack treats the URL itself as an authorized response pathway associated with the originating interaction. It can therefore bypass ordinary channel posting permissions for that response context. Option C is incorrect because global shortcuts do not inherently provide a response_url; their primary payload contains a trigger_id, which can be used to open a modal. Option A is also incorrect because interaction responses can modify or replace originating messages where the interaction type supports such behavior. If an app needs to communicate after the 30-minute response window or after exhausting the permitted responses, it should use standard messaging APIs such as chat.postMessage. This maps directly to Design the Interactive Flow of Your App, particularly slash commands, interaction acknowledgments, and asynchronous responses.

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.

A bot token represents the bot identity associated with a Slack app installed in a workspace and is the standard credential used by many Slack applications when calling Web API methods. Modern bot tokens use Slack's granular permission model, meaning their actual capabilities are determined by the bot scopes approved during installation. Bot tokens conventionally begin with `xoxb-`. They differ fundamentally from app-level tokens, which represent the application itself across installations and are limited to specific application-level functionality such as Socket Mode connectivity. A session cookie is not an application API credential. A refresh token is used when token rotation is enabled to obtain replacement access tokens rather than serving as the ordinary credential for API operations. Consequently, among the available choices, the bot token is the correct token type for routine workspace application API operations.

Installing an organization-ready Slack application at the Enterprise organization level does not automatically add the application to every workspace in that organization. Slack explicitly separates organization-level installation from workspace access. After installation at the organization level, an Org Admin must grant the application access to one or more individual workspaces—or all workspaces—before members in those workspaces can actually use it. This architecture allows centralized authorization and token management while retaining administrative control over where the application is available. Option B is therefore incorrect because organization-level installation alone does not make the application immediately operational in every workspace. Option C incorrectly describes the requirement as installation “to a channel.” Applications are granted to workspaces; channel membership may subsequently matter for specific APIs or event subscriptions, but that is a separate issue. Application collaborators manage application configuration and development access and are not required merely to activate an organization-installed application. Slack identifies simplified token storage and centralized policy as major advantages of organization-ready installation while retaining workspace-level access control. This aligns directly with Design for Scale, especially Enterprise organization deployment and organization-ready applications.

Slack's current Agent quickstart guides developers through creating an AI-powered Slack agent. The official quickstart uses a sample support agent named Casey and demonstrates building the application with the Slack CLI and Bolt frameworks while integrating supported AI agent frameworks such as the Claude Agent SDK, OpenAI Agents SDK, or Pydantic AI. The resulting agent can interact through direct messages, app mentions, App Home, modals, reactions, and threaded responses. Developers begin by installing the Slack CLI, authenticating with a workspace, and creating the agent project using the provided sample template. This is application-development guidance for Slack's AI agent platform, not billing, workspace theming, or Block Kit Builder extensions. Therefore, B precisely matches the purpose of the Agent quickstart.

Slack modals support a view stack containing up to three views, while only one view is displayed to the user at any particular moment. Applications can push new views onto the stack, update existing views, and allow users to return to prior views with their state preserved. This makes D correct and directly makes C incorrect. The App Home Home tab is also an application-controlled surface. An app composes its Home view using Block Kit and publishes that view with views.publish. The application can subsequently republish the Home view as application data changes, enabling personalized dashboards, summaries, settings, workflow entry points, and other persistent experiences. Therefore, E is correct and A is false. Block Kit applies to both modals and Home tabs, so B is incorrect. The distinction between these surfaces is architectural: a modal is focused and transient, suited to completing a defined task, whereas App Home is persistent and suited to information users revisit. This question therefore maps to Design the Interactive Flow of Your App, particularly Slack surfaces, modal view-stack behavior, Block Kit composition, and dynamic Home-tab publishing.

Block Kit is Slack's UI framework for constructing structured and interactive application interfaces. It provides reusable blocks, block elements, and composition objects that developers combine to create messages, modal views, and App Home experiences. Blocks define major visual sections of an interface, while elements provide interactive controls such as buttons, menus, text inputs, date pickers, and other components. Slack applications represent these interfaces through structured payloads and can use them across supported Slack surfaces. Block Kit is therefore concerned with presentation, interaction, information hierarchy, and application user experience. It does not provide message encryption, administrative user-role management, or API rate-limiting functionality. Those responsibilities belong to separate security, administrative, and platform-control mechanisms. Option B precisely describes Block Kit's documented function as a framework for building rich and interactive Slack application layouts.

Slack's app approval and app-management controls allow administrators to govern application installation and usage. Workspace Owners can enable app approval, pre-approve applications, restrict applications, and determine whether members can request unapproved apps. In Enterprise organizations, Org Owners can establish organization-level app-management policies that enable app approval across workspaces and control which applications may be installed or used. Enterprise administrative interfaces also support approving, restricting, installing, and distributing apps across selected workspaces. Block Kit Builder is a UI-design utility, Socket Mode is an event-delivery mechanism, and the Events API delivers Slack activity notifications; none of those features governs app installation policy. Therefore, option A is the correct administrative control for determining which applications users are allowed to install or request within managed Slack environments.

Option A is the correct answer from the supplied choices. Slack historically exposed its complete Web API method reference at `api.slack.com/methods`, and that address currently redirects to Slack's modern developer documentation under the Methods reference at `docs.slack.dev/reference/methods/`. The reference contains Slack's available method families, including `admin.*`, `apps.*`, `auth.*`, `chat.*`, `conversations.*`, `files.*`, `users.*`, `views.*`, and many others. Each individual method page identifies supported access mechanisms, OAuth scopes, parameters, response structures, errors, and rate-limit information. The pricing and legal pages are unrelated to API-method documentation, while `app.slack.com/methods` is not Slack's developer method reference. Therefore, A remains valid, although the current canonical documentation location is Slack Developer Docs.

The `slack run` command starts a Slack app in the local development environment and supports the install-and-test workflow against a selected workspace. Slack CLI uses the project's configuration to run the application locally, and current development tooling can watch supported source files and restart the running process when code changes. This enables an iterative development cycle in which the developer edits code, runs or reloads the local app, and immediately tests behavior inside Slack. `slack deploy` serves a different lifecycle purpose for supported hosted applications, while `slack start` and `slack serve` are not the standard commands documented for this workflow. Consequently, B is correct: `slack run` is the command Slack's quickstarts use to run the application locally and make it available for live workspace testing.