Free Salesforce Slack Developer Practice Test Questions

Explanation

The  App Home is the Block Kit surface displayed when a user opens an app's dedicated tab in the Slack sidebar. Every Slack app can have a Home tab, and developers publish content to it using the views.publish method with a home view type built from Block Kit blocks. This surface is where apps typically display a personalized dashboard, onboarding content, or interactive controls for the user. This makes option B the correct answer.

Why the other options are incorrect:

A. Modal – A modal is a pop-up dialog that appears on top of the Slack interface, typically triggered by an interaction such as a button click or slash command. It is opened with views.open and is not the surface shown when a user opens an app's sidebar tab.

C. Message attachment – Message attachments are a legacy way of adding secondary content (fields, buttons, images) to messages posted in channels or DMs. They appear within messages, not in the app's dedicated sidebar tab.

D. Workflow step – A workflow step is a component used in Workflow Builder to let users configure and run steps within automated workflows. It is not a Block Kit surface displayed in the app's sidebar tab.

Reference:

Slack Developer Documentation — App Home overview, describing the Home tab as the Block Kit surface displayed when users open the app in the sidebar and explaining how it is published using the views.publish method.

Explanation

The Home tab (App Home) is the surface designed to display a persistent, personalized summary view for users, along with interactive buttons and controls. Because the app needs to help employees schedule, manage, and leave feedback on interviews, the Home tab is the ideal place to present an overview — such as upcoming interviews, pending feedback requests, and action buttons — that users can return to at any time. Slack recommends using the Home tab for app dashboards and personalized summary views, published via   with a  > view type built from Block Kit. This makes option A the correct answer.

Why the other options are incorrect:

B. Shortcuts – Shortcuts (global, message, or channel shortcuts) are entry points that trigger an action when invoked, such as opening a modal or running a workflow. They are not a surface for displaying a persistent summary view; they are triggers rather than a display area.

C. Modals – Modals are pop-up dialogs used to collect input or present focused, temporary content. They are opened on demand with views.open and are dismissed once completed. A modal is not suited to displaying an ongoing summary view that users return to repeatedly.

D. Messages – Messages are content posted into channels or direct messages. While messages can contain Block Kit elements and buttons, they are event-driven and scattered across conversations rather than being a single, dedicated summary surface tied to the app. They do not provide the persistent, personalized dashboard experience that the Home tab offers.

Reference:

Slack Developer Documentation — App Home overview, describing the Home tab as a surface for displaying personalized, persistent views and interactive controls published via views.publish.

Explanation

Slack's Block Kit design guidelines recommend using the appropriate purpose-built input elements for each type of data and keeping modal layouts simple and scannable. For a parking reservation flow, the modal should use a date picker for the date, a  time picker (or time selection element) for the time range, and a  static select (dropdown) for choosing among the vehicles a user has saved. Storing multiple vehicles and presenting them as a dropdown aligns with Slack's recommendation to use select menus when a user must choose one option from a known list, and to default to the most recently used item where helpful. Among the options, option C best matches this guidance: it captures the date, the time block, and the vehicle via a dropdown in a single clean modal. This makes option C the correct answer.

Why the other options are incorrect:

A. Create a modal with fields for selecting a date and time block. If multiple vehicles exist, show a dropdown with the last used vehicle selected by default – This option omits an explicit vehicle selection when only one vehicle exists and otherwise relies on a defaulted dropdown. It is less clear and complete than a consistent dropdown approach, and does not cleanly present the vehicle choice as a standard input element in the layout.

B. Create a modal with fields for selecting a date and time block and one button for each vehicle they've saved in their settings – Using one button per vehicle clutters the modal and does not scale well. Slack guidelines favor a select menu over multiple action buttons for choosing among a dynamic, potentially long list of options.

D. Create a modal with a datetime picker field and a drop-down with the vehicles they've saved in their settings – Slack's Block Kit does not provide a combined "datetime picker" element. Date and time are separate input elements (datepicker and timepicker), so this option references a component that does not exist as described.

Reference:

Slack Developer Documentation — Block Kit reference for input elements, including