Salesforce Updated Slack-Dev-201 Exam Questions and Answers by antonia

Slack workflows can begin from multiple types of triggers rather than being limited to scheduled execution. Workflow Builder supports event-driven automation, and available triggers can include Slack activity, user-invoked links or shortcuts, scheduled execution, webhook-based initiation, and other supported events. Slack's developer examples specifically demonstrate workflows starting when an emoji reaction is applied, while Workflow Builder documentation describes combining supported triggers with workflow steps to create automations. The precise trigger choices available can vary by workflow architecture, workspace plan, and evolving Workflow Builder capabilities, but the central concept remains that workflows can start from many different events or user actions. Therefore, options A, C, and D are overly restrictive. Among the supplied answers, B best represents Slack's event-driven and scheduled workflow-trigger model and is the correct answer.

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.

A Slack modal is a temporary focused interface displayed over the current Slack experience. Slack describes modals as alert boxes, pop-ups, or dialog boxes that capture and maintain user focus until the modal is submitted or dismissed. Applications commonly use modals for structured forms, configuration tasks, data entry, confirmation flows, and detailed information that would otherwise clutter a message or Home tab. Modal views are built using Block Kit and can contain input elements, select menus, buttons, text, and other supported components. Applications normally open them through `views.open` using a recently generated `trigger_id`. Channels and workspaces are persistent Slack organizational structures, while workflow triggers begin automations rather than rendering focused pop-up interfaces. Therefore, A is correct.

Retention policies govern how long Slack conversation content is preserved before eligible data is deleted according to administrative policy. Slack provides Enterprise administrative functionality for configuring custom conversation retention, including the `admin.conversations.setCustomRetention` method. The official method description states that the endpoint sets a conversation's retention policy and requires an appropriately authorized user token with the `admin.conversations:write` scope. Retention settings concern conversation data lifecycle and organizational information-governance requirements; they are unrelated to OAuth scope expiration, Block Kit Builder history, or bot-token rotation. Administrators can use retention controls to enforce organizational, regulatory, privacy, or records-management requirements on Slack content. Consequently, among the available choices, A correctly identifies custom retention as controlling how long message and associated conversation content is retained.