Free Salesforce Slack Developer Practice Test Questions

Explanation:

The question asks which Block Kit element type should be used inside a block to collect free-text input in a modal. In Slack's Block Kit framework, modals are built using input blocks, and the element placed inside an input block determines what kind of data the user can provide.

Correct Answer: B. plain_text_input – plain_text_input is the Block Kit element designed specifically for collecting free-form text from users. It is used inside an input block and supports features like multiline, min_length, max_length, placeholder, and dispatch_action. When the user submits the modal, the entered text is returned in the view_submission payload. This makes it the only element among the options capable of capturing unrestricted, user-typed text.

Why Other Options Are Incorrect:

A. button
– A button is an interactive element that triggers an action when clicked. It does not collect any text input from the user. Buttons are valid only inside section or actions blocks, not as data-entry elements.

C. static_select
– A static_select is a dropdown menu that lets users choose from a predefined list of options. It cannot accept arbitrary or free-text input, so it fails the requirement of collecting open-ended user text.

D. overflow – An overflow element is a compact menu (typically shown as a "⋮" icon) that presents a short list of actions or choices. Like static_select, it only allows selection from fixed options and provides no free-text entry capability.

Only plain_text_input satisfies the requirement of capturing unrestricted text typed by the user inside a modal.

📚 References

Slack API – plain_text_input element

Explanation

In Slack's Block Kit framework, surfaces represent the visual areas where apps interact with users. A modal is a focused pop-up window that overlays the Slack client interface. Modals are primarily designed to collect structured inputs, display detailed context, or guide users through interactive workflows without requiring users to leave their current channel or conversation. They are UI surfaces, not background processes or authentication mechanisms.

Why the other options are incorrect

A. Background scheduled job
– A background scheduled job refers to asynchronous server-side processing or scheduled tasks. It is unrelated to Block Kit's front-end UI surfaces and does not represent a visual interface for users.

C. A type of OAuth token
– OAuth tokens, such as bot or user tokens, are used for authentication and API authorization. They control access to Slack APIs and resources rather than defining visual user interface elements.

D. Workspace-wide announcement banners
– Announcement banners are administrative or messaging features used to communicate information across a workspace. They are different from Block Kit modals, which are interactive UI surfaces that apps can invoke dynamically.

Official References

Slack API Surfaces - Modals – Official Slack documentation describing modals as focused views for interactive forms and structured content above the main Slack interface.

Block Kit Overview – Official Slack documentation describing Block Kit as a UI framework for building Slack app surfaces such as Messages, Home Tabs, and Modals.

Explanation

When a user interacts with a Slack shortcut, slash command, or interactive UI component such as a button or menu, Slack sends a payload to the app containing a temporary trigger ID called trigger_id. To open a modal, the app calls the views.open API method and provides this trigger_id. The trigger_id authorizes the modal-opening action and is short-lived, so it must be used within 3 seconds of receipt. Therefore, trigger_id is the required value for opening a modal.

Why the other options are incorrect

A. token
– The token parameter is associated with request verification and older Slack authentication mechanisms. It is not the value required by views.open to open a modal. Slack's current request verification approach uses signing secrets and signature headers.

B. response_url
– The response_url is a temporary webhook URL used to send responses or follow-up messages associated with an interaction. It does not provide the authorization context required to open a modal with views.open.

C. callback_id
– The callback_id is a developer-defined identifier used to associate an interaction or view with application logic. It identifies context but does not authorize or initiate the opening of a modal.

Official References

Slack API - views.open Method – Official Slack documentation explaining that views.open requires a trigger_id generated by a user interaction.

Slack API Surfaces - Modals – Official documentation describing how applications open interactive modal views using a trigger ID.

Explanation:

The question asks about the purpose of slash commands in Slack. Slash commands are an interactivity feature that lets users invoke an app's functionality directly from the message input box by typing `/` followed by a command name, such as `/remind`, `/poll`, or `/ticket`. When a user sends a slash command, Slack sends an HTTP POST request to the URL configured by the app developer. The request includes information such as the command name, arguments, user, team, channel, and response URL. The app can then process the request and respond with a message, initiate a workflow, or use the interaction context to perform another supported action. Therefore, slash commands are a standard way for users to trigger app functionality on demand.

Why Other Options Are Incorrect:

A. Encrypting messages
– Slash commands are not an encryption mechanism. Encryption protects the confidentiality of data, while slash commands provide a way for users to invoke application functionality.

C. Changing a workspace's theme
– Workspace themes are managed through Slack's user interface and preferences. Slash commands are designed to trigger application functionality, not manage workspace appearance.

D. Deleting channels
– Slash commands do not inherently delete channels. Channel administration and deletion are controlled through Slack's administrative features and appropriate API permissions.

Reference:

Slack API Documentation – Slash Commands – Official Slack documentation explains that slash commands allow users to invoke app functionality by typing a command beginning with `/` and describes the request payload and response mechanisms.