Path1.Mod1.b - Explore ML Workspace - Team Workspace Setups

Question 1

Workspace per Team setup - Use Case

Answer 1

When team members require the same level of access to data and experiment assets

Question 2

Workspace per Team setup - Pros

Answer 2

Assets stored in ONE place!!

Question 3

Workspace per Team setup - Cons

Answer 3

No granular permissions control using RBAC or ACL (Access Control Lists) for data sources or assets == no support for data segregation use cases

Question 4

Workspace per Project setup - Use Case

Answer 4

When you require data and asset segregation by project, or cost managment per project requirements. Ex. Four ML Teams each with three projects = 12 workspaces

Question 5

CM PLA vs TLA

Workspace per Project setup - Pros

Answer 5

• Costs managed at a project level
• Project level access, instead of Team level access, simplifies collaboration efforts

Question 6

Workspace per Project setup - Cons

Answer 6

Results and Asset Isolation; discovery and reuse is difficult due to them being spread across multiple project Workspaces.

Question 7

Single Workspace setup - Use Case

Answer 7

When you have non-team/non-project work, or when costs aren’t directly associated to any specific billable unit

Question 8

Single Workspace setup - Pros

Answer 8

• Decoupling of individual, non-project work from project-related costs
• Reduces “Azure footprint”

Question 9

”C”W SWpBD

Single Workspace setup - Cons

Answer 9

• “Cluttered” workspace (forced to use UI-based filtering for assets)
• Forces creation of shared workspaces per business division to mitigate scaling concerns