Free Slack Slack-Certified-Admin Practice Exam with Questions & Answers | Set: 2

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.

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.

Send a message that includes an @channel and @here to #supplier-bindings.

Send a message that includes an @channel and @everyone to #supplier-bindings.

Send an @everyone in a message to your workspace-wide #general channel.

Direct message your key contact who belongs to the connected channel, so they are directly informed.

Members must have a sophisticated and complex password that is updated regularly.

Members must use a biometric reader to authenticate with Slack.

Members use single sign-on (SSO) to handle the exchange of usernames and passwords on behalf of Slack.

Members must submit a verification code along with their password each time they sign in.

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.

Their accounts will be deactivated, but they won’t be signed out of their devices. A session reset is also required.

Their Slack accounts will be deleted permanently, and all messages and files will be deleted, as well, for compliance reasons.

Their accounts will be deactivated, they will be signed out on all of their devices, and their accounts will be removed from channels. However, only their messages and files in direct messages will be deleted.

Their accounts will be deactivated, they will be signed out on all of their devices, and their accounts will be removed from channels. However, their messages and files won’t be deleted.

Create workspaces for each department and sub-department in the company.

Create workspaces for each product line sold, where each workspace is the "primary" workspace for the employee.

Create workspaces based on how information is shared, and where employees have one "primary" workspace where they spend 80% of their time.

Create one workspace, where each product line sold has its own channel.

Require that invitations get approval via a #guest-invitation-approval channel so Admins can action the requests and inform project leaders to invite individuals from outside companies as Single-Channel Guests. Set expiry dates for the Single-Channel Guests.

Require that invitations get approval via a #guest-invitation-approval channel so Admins can action the requests and inform project leaders to invite individuals from outside companies as Multi-Channel Guests. Set expiry dates for the Multi-Channel Guests.

Have the Admins individually send out Single-Channel Guest invitations.

Ask the outside companies to upgrade to the paid plan. Then, share the launch channel externally to the companies, and set a reminder to unshare the channel when the launch is complete.