The Fabric admin wants every workspace grouped under the network's conservation-branch domain to default to the same Spark pool configuration, without visiting each workspace individually to set it up. What should the admin configure?
Select an answer to reveal the explanation.
Short Explanation
Domain-level settings work like a template stamped onto every workspace in the group -- set the Spark configuration once at the domain, and every member workspace picks it up automatically instead of the admin repeating the setup everywhere.
Full Explanation
Domain-level workspace settings, including Spark configuration, can be defined once at the domain and inherited by default across every workspace assigned to that domain -- exactly the one-time setup the admin is looking for, since it avoids visiting each workspace individually. Assigning every workspace to the same capacity controls shared compute billing and throughput limits, not default Spark pool configuration inheritance. Applying the setting manually one workspace at a time is the very repetition the admin is trying to avoid, and it doesn't scale as branches are added. Creating one shared deployment pipeline manages lifecycle promotion between environments; it has nothing to do with propagating a default configuration setting across a domain's member workspaces. A caveat worth knowing: an individual workspace can typically still override an inherited domain default if it has a genuine need to diverge. Confirm the setup by checking a newly added conservation workspace's Spark settings show the domain's configuration applied without manual entry.