Slack Slack-Certified-Admin Slack Certified Admin Exam Exam Practice Test

To use slash commands without disturbing the rest of the channel members

To add responses such as “thank you” or “I’m looking into it” without cluttering the channel needlessly

To make multiple discussions in the same channel easier to follow

To ensure that others in a channel will be notified of new messages

Using an integrated Data Loss Prevention (DLP) solution, delete the file, and then review the Audit Logs API to see who downloaded the file.

Using MDM, disable file downloads and then use session management to see who was logged in and downloaded the file.

Using a third-party eDiscovery app, delete the file and use data exports to determine who downloaded the file.

Using Slack Enterprise Key Management (EKM), revoke key access for the file, and review the EKM logs to see who downloaded the file.

Allow each region to create new channels and name them after famous landmarks in their region, then assign regional team members to monitor each channel.

Create a private channel for the global workplace team to triage requests from #help-workplace into the appropriate regions.

Create new regional channels and name them using the #help-workplace-region format, then assign regional team members to monitor each channel.

Continue to use one centralized channel to minimize confusion for channel members on where workplace requests should be submitted, but require that members start posts with the name of the region where they're requesting assistance.

Convert #bread-buds to private, archive it, and direct everyone to #carbohydrate-chats.

Delete #bread-buds, reference its messages as needed, and direct everyone to #carbohydrate-chats.

Remove all members from #bread-buds, and invite them to #carbohydrate-chats.

Post a message in #bread-buds redirecting everyone to #carbohydrate-chats, and archive #bread-buds.

Convert the channel to private, and then archive it; members of the channel will retain access to the files.

Archive the public channel; anyone can still browse the conversation history in Slack, and messages will appear in search results.

Delete the channel; messages from a deleted channel are still available via search.

Remove all members from the channel, and then archive it; this way, members can find messages via search but will not be able to browse the channel history itself.

Create a new public workspace called "Expenses" with access granted to all employees.

Create a private channel called #expense-system-updates with all employees added.

Create a new invite-only workspace called "Expenses."

Create a public announce-only channel for the expense system.

It supports integration with various third-party apps for easy data transfer between services.

Non-developers can easily automate business processes.

Templates are available for download.

Developers and engineers can easily automate efficiencies in their development.

It is not possible to create a custom workflow for your team in fewer than five clicks.

Workspace Owners and Admins can view all published workflows created by members of their workspaces.

To see all workflows in a workspace, you need to be an Owner or Admin of that workspace.

It is currently possible for Org Owners and Admins to view all workflows created in an Enterprise Grid org.

Create a public channel for co-ordination, but continue using group DMs, and DMs for content that needs to stay private.

Continue using the group DM, and invite the new members to it.

Start a new group DM with only the new members of the team.

Convert the group DM to a private channel, and then invite the new members.