Salesforce Slack-Dev-201 Practice Exam Questions & Answers

A and C are the two choices that best align with the current official Slack design guidance. Slack emphasizes concise, easily processed content. Applications should communicate clearly and minimize unnecessary cognitive load so users can understand information quickly rather than reading lengthy or overly complex interfaces. This supports the principle represented by option A. Slack's Block Kit design guidance also recommends simplifying suitable information with pictures. For example, faces may communicate user identity more efficiently than lists of names, and maps can sometimes communicate location more effectively than text. Images must still be accessible through appropriate alt_text; the recommendation is not to remove essential textual meaning indiscriminately. Option B is incorrect under current official guidance. Slack explicitly states that shortcut names should start with a verb, not a noun. Option D conflicts with Slack's recommendation to avoid excessive notifications, while option E is directly contrary to the guidance to reduce complexity by progressively revealing controls and information. The supplied document marks A and B, but B conflicts with Slack's published developer guidance and therefore should not be retained as the verified answer. This question belongs under Design a Great User Experience.

Slack identifies rate-limit exhaustion through the HTTP status code 429 Too Many Requests. When this occurs, the response includes a Retry-After header containing the number of seconds the application must wait before retrying the rate-limited operation. Slack applies Web API limits primarily on a per-method, per-workspace basis. Consequently, reaching the limit for conversations.list does not necessarily mean that every Web API method for the same workspace has become unavailable. Applications should read Retry-After, wait for the indicated interval, and retry responsibly rather than immediately issuing more requests. Pagination is also important. Slack explicitly notes that methods supporting cursor-based pagination may receive stricter rate treatment when an application attempts to retrieve extensive datasets without using pagination appropriately. A growing workspace therefore makes efficient pagination and caching increasingly important. HTTP 500 generally indicates a server-side failure rather than rate limiting. HTTP 200 can contain method-level errors or warnings but is not Slack's rate-limit signal. A Timeout header is not the prescribed rate-limit response mechanism. This is a core Design for Scale concept: applications must handle API limits predictably as data volume and workspace size increase.

A modal is a focused application surface that appears over the Slack interface and maintains the user's attention until it is submitted or dismissed. Slack describes modals as alert boxes, pop-ups, or dialog-style interfaces used for focused interactions. Applications commonly use them to collect structured information, present temporary details, configure settings, or guide a user through a task. Modal content is constructed using Block Kit blocks and interactive elements, including text inputs, select menus, buttons, and date pickers. Modals are typically opened after an explicit user interaction by calling `views.open` with a valid `trigger_id`. They are not scheduled background processes, authentication tokens, or organization-wide announcement mechanisms. Therefore, option B accurately describes the purpose and presentation model of a Slack modal.

When using the HTTP delivery model for the Events API, Slack sends subscribed events as HTTP POST requests containing JSON payloads to the application's configured Request URL. That URL must be a publicly reachable HTTPS endpoint capable of receiving and acknowledging Slack requests. Slack currently provides two event-delivery architectures: HTTP Request URLs and Socket Mode. Socket Mode replaces the public Request URL with a WebSocket connection, so the question's phrase ''by default'' is slightly imprecise under current documentation. Nevertheless, among the available options, A is unequivocally the intended and technically valid Events API delivery mechanism. Email, desktop notifications, and SMS are not mechanisms Slack uses to deliver application Events API payloads. Applications using HTTP should also verify Slack request signatures before processing the payload.

Slack's current architecture guidance explicitly favors HTTP Request URLs for production applications when Socket Mode is not required. WebSockets are stateful, which makes them more complex to scale horizontally and more susceptible to connection interruptions, network partitions, and transient disconnections. Slack describes Socket Mode as particularly convenient for local development, on-premises integrations, environments behind firewalls, or applications unable to receive inbound HTTP traffic. For maximum application-connectivity reliability, Slack recommends HTTP for production applications and advises developers to continue using HTTP request URLs when their deployment does not specifically require Socket Mode. Socket Mode also does not replace the Web API; applications commonly receive events over Socket Mode and then invoke Web API methods to perform actions. Therefore, B accurately reflects Slack's present production-scale guidance.

Slack shortcuts provide explicit entry points that users can invoke to start application functionality. Slack supports two principal shortcut types: global shortcuts and message shortcuts. Global shortcuts can initiate functionality without requiring an existing message context, while message shortcuts are attached to individual messages and appear in the message context menu. When a shortcut is invoked, Slack sends an interaction payload to the application containing contextual information and a `trigger_id`, which can be used to open a modal or continue another interactive flow. Webhooks are message-delivery mechanisms rather than user action entry points. OAuth scopes define permissions, while manifests describe application configuration. Consequently, Shortcuts is the Slack feature specifically designed to let users invoke application actions from Slack UI locations.