The correct answer is B. Unless the Enterprise Grid’s Slack Connect settings have been restricted, users are not limited to only an “External” workspace for external collaboration. Slack Connect is an Enterprise Grid capability that can be governed centrally, and by default the collaboration capability can apply across the workspaces in the grid. The client may later decide to restrict external collaboration to selected workspaces, such as an External workspace, but that would be a deliberate policy decision, not the default assumption. Option A is tempting because the workspace is named “External,” but workspace naming alone does not automatically restrict Slack Connect requests to that workspace. Option C and Option D are arbitrary and have no relationship to Slack Connect policy behavior. The consultant should clarify that workspace architecture and policy settings work together: the grid can include an External workspace for strategic organization, but administrators still need to configure policies if they want external collaboration limited to that workspace only.