# Hub-and-Spoke Model

The hub-and-spoke model combines a central team that provides shared expertise, standards, and capabilities with distributed teams that deliver solutions for their own business domains.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/hub-and-spoke-model

> For enterprise AI, the hub is typically an AI center of excellence, while the spokes are business-unit or product teams responsible for applying AI to specific problems. This arrangement helps organizations scale beyond isolated pilots by reusing infrastructure and governance without removing delivery ownership from domain experts.

Practice exams covering Hub-and-Spoke Model: [AIB-C01 (beta) AWS Certified AI Business Strategist](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist).

## 6 key aspects of Hub-and-Spoke Model

The model combines shared foundations and governance with domain-owned execution, supported by explicit responsibilities and continuous cross-team collaboration.

1. **Centralized enablement**: The hub provides reusable platforms, standards, specialist expertise, and training. It should make approved delivery paths easier to use rather than become the mandatory implementer of every solution.
2. **Distributed business ownership**: Spokes own domain-specific use cases, acceptance criteria, adoption, and business outcomes. Their operational responsibilities should be explicitly agreed with the central platform team.
3. **Shared governance with local execution**: Common security, privacy, evaluation, and lifecycle requirements apply across teams. Spokes implement these requirements using approved patterns, with documented exceptions and risk-based escalation when necessary.
4. **Reusable cloud foundations**: Governed accounts, infrastructure templates, deployment pipelines, and shared artifacts reduce repeated setup work. Workload isolation and explicit access permissions preserve appropriate boundaries between spokes.
5. **Cross-functional feedback loops**: Domain representatives, office hours, architecture forums, and shared backlogs connect the COE with delivery teams. These mechanisms help turn successful local practices into reusable enterprise capabilities.
6. **Balanced decision rights and measurement**: Define which decisions belong to the hub, the spokes, or a joint review. Measure delivery speed, control effectiveness, reuse, cost, and business value to detect either central bottlenecks or excessive fragmentation.

## Cloud services for Hub-and-Spoke Model

AWS Organizations and AWS Control Tower establish account boundaries and baseline controls for distributed teams. AWS Service Catalog makes centrally approved infrastructure available through repeatable provisioning paths. Within those environments, Amazon SageMaker AI supports model development and lifecycle workflows, while AWS Lake Formation supports governed access to shared data. Together, these services can provide the technical foundation for central enablement and local delivery. They do not create an AI center of excellence by themselves: decision rights, funding, cross-functional participation, operational ownership, and escalation procedures still need to be established by the organization.

- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: A central team can organize workload accounts and apply service control policies across organizational units, while spoke teams operate within their own accounts. Service control policies constrain available permissions; they do not grant permissions or replace workload-level access controls.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: A platform hub can use a governed landing zone and Account Factory to provision accounts for spoke teams with consistent baseline controls. This supports repeatable onboarding but does not define the COE's organizational responsibilities or AI approval process.
- **[AWS Service Catalog](https://blowstack.com/tools/cloud-services-hub/aws-service-catalog)**: The hub can publish approved infrastructure products and share portfolios with spoke accounts. Spokes provision those products within configured constraints, reducing repeated platform work while retaining ownership of their deployments.
- **[AWS Lake Formation](https://blowstack.com/tools/cloud-services-hub/aws-lake-formation)**: A central data-governance function can define fine-grained access to data catalog resources and share governed resources across accounts. Spoke teams can consume authorized data without requiring unrestricted access or consolidation of every dataset into one account.

## Hub-and-Spoke Model exam questions

Real practice exam questions on Hub-and-Spoke Model, with the correct answer and its explanation.

### Question 1 (AIB-C01 (beta))

**Question:**

A diversified company is expanding AI assistants across procurement, human resources, and customer service. Its AI center of excellence (COE) maintains a common evaluation framework with mandatory privacy and safety checks. Each department also needs tests for its own workflows. Currently, departments copy the framework and modify it independently, so central updates are difficult to adopt and useful improvements rarely reach other teams. Leadership wants to preserve mandatory checks, support department-specific evaluation, and avoid requiring the COE to manage every application's releases. Which collaboration approach should the AI business strategist recommend?

**Correct answer:** Have the COE maintain a versioned common framework with mandatory checks and supported extension points; departments own workflow-specific tests and release decisions, while departmental representatives help review contributions for inclusion in the shared framework.

**Explanation:** This applies a hub-and-spoke operating model: the COE stewards reusable capabilities and enterprise requirements, while departments retain domain-specific delivery ownership. Supported extensions simplify adoption of central updates, and joint contribution reviews allow useful improvements to benefit other teams without centralizing every application release.

## Practice Hub-and-Spoke Model in a full exam

Questions on Hub-and-Spoke Model in each practice exam, with every answer option and an explanation for each:

- [AIB-C01 (beta)](https://blowstack.com/practice-exams/aws-certified-ai-business-strategist): 7 questions

## What is Hub-and-Spoke Model

The hub-and-spoke model distributes responsibilities between a central enabling function and multiple delivery teams. In enterprise AI, the hub commonly takes the form of an AI center of excellence (COE), bringing together platform engineering, data science, security, risk, legal, and business leadership. The spokes are teams embedded in departments or product groups that understand local workflows, datasets, users, and business outcomes. The goal is to centralize capabilities that benefit from consistency while keeping domain-specific decisions close to the people accountable for results.

The hub establishes common foundations such as approved development environments, identity and access patterns, model evaluation requirements, data-handling standards, reusable deployment pipelines, and training. It can also coordinate scarce expertise, vendor assessment, and enterprise-wide AI investment priorities. Spokes identify use cases, prepare domain data, develop or configure solutions, validate business suitability, and operate their applications. Responsibilities must be explicit: a shared platform team might maintain deployment tooling, while the application team remains responsible for production performance and incident response for its workload.

In the cloud, this operating model often maps to a multi-account or multi-project environment. A central platform team supplies governed environments and reusable infrastructure templates, while separate workload environments provide isolation and cost attribution for individual spokes. Shared capabilities can include artifact repositories, model registries, observability, and approved data-access mechanisms. However, the hub does not need to own every dataset or host every model endpoint. Data residency, confidentiality, latency, and operational ownership may require resources to remain within a spoke's environment.

For example, a retailer might establish an AI COE that publishes evaluation templates, security controls, and deployment pipelines. An inventory team builds a demand-planning application, while a customer-service team develops a retrieval-based assistant. Both reuse the central foundations, but each defines its own acceptance criteria and measures its own business results. The assistant needs tests for grounded answers and inappropriate disclosure; the planning application needs forecast-quality checks and measures of inventory impact. Common governance should accommodate these differences rather than impose one universal model-quality threshold.

Cross-functional collaboration requires more than a central team name. Practical mechanisms include named representatives from each spoke, shared architecture reviews, office hours, reusable reference implementations, and a documented exception process. Risk-based review allows low-risk changes to proceed through automated checks while directing sensitive applications to appropriate human reviewers. Feedback from spokes should influence platform priorities so that standards evolve with real delivery needs.

The principal trade-off is consistency versus autonomy. Excessive central approval creates queues and turns the COE into a delivery bottleneck. Excessive independence duplicates tooling, fragments controls, and makes costs and risks harder to compare. A useful approach is to provide self-service approved patterns, clear decision rights, and measurable service expectations. Track adoption, deployment lead time, duplicated effort, policy exceptions, operating costs, and business outcomes rather than merely counting pilots.

A common misconception is that the hub must build every AI solution. That is a centralized delivery model, not the intended balance of centralized enablement and distributed execution. Another misconception is that this organizational model requires a particular network topology. Hub-and-spoke networking is a separate application of the same structural idea; adopting an AI COE does not require all application traffic or data to pass through a central network hub.

## Learn Hub-and-Spoke Model in lessons

1 short lesson on Hub-and-Spoke Model in 1 certification course.

- AIB-C01 (beta): Hub-and-Spoke Model: central enablement and team ownership (Premium), https://app.blowstack.com/lessons/hub-and-spoke-model-central-enablement-and-team-ownership-aib-c01
