Tam Corp sells 15 versions of their software to customers around the world. They have a global team (e.g., sales, engineering, support, and human resources) of 500 employees.
Tam Corp is moving to the Enterprise Grid plan from two workspaces on the Plus plan. On their current Plus plan, they organize one workspace by team (e.g., #sales-team, #engineering-team, and #support-team), and the other workspace is primarily for recruiting discussions and the leadership team.
Leadership does not want the move from Plus to Grid to significantly impact how teams are communicating today.
When considering how to structure the Enterprise Grid, what is the structure that aligns with leadership and allows the teams to communicate most effectively?

• A. Create workspaces for each product line sold, where each workspace is the "primary" workspace for the employee.
• B. Create workspaces based on how information is shared, and where employees have one "primary" workspace where they spend 80% of their time.
• C. Create workspaces for each department and sub-department in the company.
• D. Create one workspace, where each product line sold has its own channel.

A few months ago, a team of developers at Blue Inc identified a new issue during testing and created a public channel called #bug-cricket to communicate about the issue. After some casual conversation back and forth in the channel, the team discovered that a problem with the old architecture caused this bug.
They may need to reference the history in the future.
Of note, there has not been any new activity in #bug-cricket for months, and the bug case has been closed.
What should the team do with #bug-cricket?

• A. Convert the channel to private, and then archive it; members of the channel will retain access to the files.
• B. Delete the channel; messages from a deleted channel are still available via search.
• C. 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.
• D. Archive the public channel; anyone can still browse the conversation history in Slack, and messages will appear in search results.

Britt is a Workspace Admin who created a public channel called #bread-buds for co-workers who enjoy bread- making.
The company has had new team members join, and the conversation has become more general about all types of carbohydrates. Britt decides it's time to expand the channel. Rather than rename it, Britt creates a new channel #carbohydrate-chats to be inclusive and start fresh with activity. At the same time, Britt want to keep
#bread-buds so the team can reference baking instructions that have been gathered over the past few years, but she doesn't want anyone posting in it.
What should Britt do?

• A. Remove all members from #bread-buds, and invite them to #carbohydrate-chats.
• B. Post a message in #bread-buds redirecting everyone to #carbohydrate-chats, and archive #bread-buds.
• C. Delete #bread-buds, reference its messages as needed, and direct everyone to #carbohydrate-chats.
• D. Convert #bread-buds to private, archive it, and direct everyone to #carbohydrate-chats.

How many integrations can be installed on a workspace on the Standard plan?

• A. 25 integrations
• B. 5 integrations
• C. Unlimited
• D. 10 integrations

Your company is conducting an internal security assessment of Slack prior to implementation. Which of the following is true about security in Slack?

• A. Slack data is stored on your company's servers.
• B. Workspace Admins can see all direct message content at any time through the Admin console.
• C. Slack members can only access Slack when on the corporate network.
• D. Slack data is encrypted at rest and in transit.