Free Salesforce Slack-Dev-201 Practice Exam with Questions & Answers | Set: 4

Block Kit Builder is Slack's official visual prototyping environment for designing and previewing Block Kit interfaces. Developers can use it to assemble blocks, configure their properties, rearrange components, inspect the resulting structured payload, and preview how the interface will appear within supported Slack surfaces. Slack's Block Kit documentation specifically recommends using Block Kit Builder to experiment with available blocks before incorporating the generated structures into an application. This is especially useful when designing complex messages, modals, and Home tabs because developers can validate visual hierarchy and component compatibility interactively rather than repeatedly modifying application code. Slack Studio, Bolt Designer, and Surface Editor are not the official Block Kit prototyping tools described in Slack Developer documentation. Consequently, option A is the only answer that corresponds to Slack's documented visual interface-development tooling.

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

An organization-ready Slack application can be installed once at the Enterprise organization level, generating an organization-wide token that represents the application's authorization across the Enterprise organization. Slack explicitly identifies one of the advantages of organization-ready applications as requiring users to authorize the app once rather than creating separate credentials for each individual workspace. Therefore, with the application appropriately approved and configured with the necessary scopes, installing it at the Enterprise Grid organization level produces the token architecture required by the scenario. Installing separately into every workspace, as described by A, would defeat the stated objective of avoiding multiple-token management. A further architectural distinction is important: organization-level installation does not necessarily make the application automatically visible or usable in every workspace. Slack can separately grant an organization-installed app access to selected workspaces. However, that deployment/access process is distinct from the question's specific requirement to generate the single organization-wide token. Slack's Admin API scopes similarly require the application to be installed across the organization rather than only to an individual workspace. Thus B represents the intended token-generation procedure. This belongs to APIs for Managing Your Slack, particularly Enterprise organization-ready applications, org-level authorization, and administrative token management.

Block Kit Builder is Slack's visual prototyping environment for designing and previewing Block Kit layouts. It allows users to add, rearrange, and configure blocks while simultaneously reviewing the associated JSON representation and seeing how the completed layout will render. For the HR newsletter use case, the team can therefore construct and visually review a formatted message before the application or automation sends it to the required regional channel. Slack describes Block Kit Builder as a tool for choosing, configuring, arranging, and previewing blocks across Slack surfaces. Option A overstates its function: Block Kit Builder is not fundamentally a template-management repository for organizing recurring newsletters. Option C is also too broad. The builder can expose example interaction payloads and validate message composition, but it does not execute an application's complete backend interactivity workflow end-to-end. Option D is unsupported; it does not automatically convert arbitrary word-processing documents into production-ready Block Kit structures. Therefore, B accurately describes its intended role: prepare and preview the Slack UI/message composition before deployment. This belongs to Tools, specifically Block Kit Builder and visual prototyping of Slack application surfaces.

Slash commands are application entry points that allow users to invoke Slack app functionality directly from the message composer. A user enters a forward slash followed by the registered command—for example, `/todo`—and Slack routes the resulting command payload to the associated application. The payload includes contextual information and any text entered after the command. The application must acknowledge the request promptly and can respond through mechanisms such as `respond()`, `say()`, or subsequent Web API operations. Slack's official documentation explicitly describes slash commands as allowing users to invoke an app by typing a string into the message composer. They are unrelated to message encryption, workspace theme configuration, or general channel deletion. Therefore, B accurately describes the purpose of Slack slash commands.

conversations.history is Slack's current unified Web API method for retrieving message history from conversations. With the relevant OAuth scopes, a bot token can retrieve message history from conversations in which the bot is a member. Public-channel history requires channels:history, while private-channel history requires groups:history. Therefore, the app must be present in the applicable channels and possess the corresponding history scopes. Option C relies on legacy methods. Slack consolidated historically separate channel APIs into the Conversations API, making conversations.history the supported method for both public and private conversation history. The Events API can deliver newly occurring message events, but it does not independently provide the historical messages already stored in the conversation. Therefore, A does not meet the requirement to read both existing and subsequent message history. The Discovery API is a specialized Enterprise security and compliance capability and is inappropriate for an ordinary internal application. The source question and marked answer are therefore consistent with current Slack behavior. This maps to Design Your Workflows: Spotlight on Slack's APIs, particularly conversation membership, history scopes, and the unified Conversations API.

App Home provides an application with a dedicated, private space for interacting with each individual Slack user. Slack defines App Home as a one-to-one space shared between a user and an app. Its Home tab is fully customizable using Block Kit and can contain dashboards, personalized information, application controls, workflow entry points, settings, and interactive components. Applications publish and update Home-tab content dynamically, allowing the surface to function as persistent application real estate rather than a transient interaction. A modal is temporary and focused, while slash commands are invocation mechanisms rather than persistent surfaces. Workflow steps are reusable automation components and likewise do not provide an app-specific sidebar destination. Therefore, App Home is the correct dedicated application surface represented by option A.

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.

Slack's documented macOS and Linux installation method uses the official shell installer hosted on Slack's downloads domain. The command `curl -fsSL https://downloads.slack-edge.com/slack-cli/install.sh | bash` retrieves the installer securely and runs it through Bash, installing the Slack CLI and making the `slack` command available for development. Slack's current CLI installation documentation presents this command as the supported installation path for macOS and Linux. The alternatives do not represent the official installation command in the Slack Developer documentation: Slack CLI is not installed through the listed npm or pip commands, and `brew install slack` does not correspond to Slack's documented CLI installer. Therefore, option B is the verified installation command for the environments named in the question.

Enterprise Grid is Slack's enterprise architecture for organizations that need centralized governance across multiple Slack workspaces. Workspaces can exist within one Enterprise organization while organization-level administrators manage identity, policies, applications, security, and other administrative functions across the broader environment. Slack's current Enterprise documentation continues to describe Enterprise Grid organizations as containing multiple workspaces, and migration tooling allows standalone workspaces to be incorporated into an Enterprise organization. Enterprise functionality also enables organization-level application installation, Admin APIs, centralized app-management policies, and other large-scale administrative capabilities. Enterprise Grid is therefore not a pricing utility, UI theme, or authentication token type. Among the available options, B correctly captures its architectural purpose as Slack's offering for large organizations operating multiple managed workspaces.