I85PREP
⌘ K
EXIN SIAM Professional Bridge based on the Scopism SIAM BoK V3 study materials
EXIN SIAM Professional Bridge based on the Scopism SIAM BoK V3 study resources

EXIN SIAM Professional Bridge based on the Scopism SIAM BoK V3 practice questions

One question at a time. Build your EXIN SIAM Professional Bridge based on the Scopism SIAM BoK V3 understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Introduction to SIAM and the SIAM BoK

In SIAM terminology, what does the service integrator primarily provide to the enterprise?

  1. A replacement for every internal IT department in the organisation
  2. A single point of accountability for coordinating services from multiple providers Correct answer.
  3. An outsourced help desk that handles only end-user calls
  4. A hardware procurement service for data centre equipment

Explanation

The service integrator is the function that orchestrates and integrates services delivered by many providers, giving the enterprise one point of accountability for end-to-end outcomes. It does not replace internal capability wholesale, nor is it limited to procurement or service desk work.

Question 2Introduction to SIAM and the SIAM BoK

Which statement best describes the shift in sourcing that SIAM responds to?

  1. Enterprises consolidating all services into one internal team
  2. Enterprises moving from many suppliers back to one single outsourcer
  3. Enterprises moving from a single outsourcer to multiple specialised service providers Correct answer.
  4. Enterprises eliminating external suppliers entirely

Explanation

SIAM emerged because organisations increasingly use several specialised providers rather than one prime contractor, which creates coordination and accountability gaps. The framework addresses how to integrate those multi-supplier services.

Question 3Introduction to SIAM and the SIAM BoK

What is the SIAM BoK primarily intended to be?

  1. A software tool for monitoring service levels
  2. A body of knowledge capturing good practice for service integration and management Correct answer.
  3. A legally binding contract template for outsourcing
  4. A certification syllabus owned by a single vendor

Explanation

The SIAM BoK is a body of knowledge that gathers good practice, concepts, and guidance on service integration and management. It is vendor-neutral and is not a contract template or a monitoring product.

Question 4Introduction to SIAM and the SIAM BoK

In the SIAM structural model, which layer typically holds the service integrator function?

  1. The external audit layer
  2. The service integrator layer between the customer organisation and providers Correct answer.
  3. The technology vendor layer
  4. The service provider layer

Explanation

The SIAM model places the service integrator between the customer organisation and the service providers, so it can coordinate and assure end-to-end delivery. Providers sit below it and the customer organisation sits above it.

Question 5Introduction to SIAM and the SIAM BoK

Which pair correctly matches a SIAM role with its main responsibility?

  1. Process owner: approves the enterprise's annual IT budget
  2. Service desk analyst: negotiates contracts with providers
  3. Customer organisation: delivers technical fixes to users
  4. Service integrator: owns end-to-end coordination across providers Correct answer.

Explanation

The service integrator is accountable for coordinating and integrating services across multiple providers to deliver end-to-end outcomes. Budget approval, contract negotiation, and hands-on fixes belong to other roles.

Question 6Introduction to SIAM and the SIAM BoK

What does the term 'end-to-end service management' emphasise in a SIAM context?

  1. Managing only the technology infrastructure layer
  2. Managing the complete service across all providers as one integrated whole Correct answer.
  3. Managing services only during business hours
  4. Managing each provider's services in isolation

Explanation

End-to-end service management means the service is managed across all contributing providers as a single integrated whole, rather than provider by provider. This is the core promise of SIAM.

Question 7Introduction to SIAM and the SIAM BoK

An enterprise uses four providers for infrastructure, applications, security, and service desk. Users report that no one owns cross-provider incidents. Which SIAM concept most directly addresses this gap?

  1. Technology refresh of the monitoring platform
  2. Outsourcing the service desk to a fifth provider
  3. Vendor consolidation into a single contract
  4. Service integration with clear end-to-end accountability Correct answer.

Explanation

The described gap is a lack of end-to-end ownership across providers, which SIAM addresses through service integration and explicit accountability. Adding providers or buying tools does not by itself create cross-provider ownership.

Question 8Introduction to SIAM and the SIAM BoK

Which outcome is most characteristic of a mature SIAM ecosystem?

  1. Contracts are avoided in favour of informal agreements
  2. Providers collaborate within shared processes and integrated governance Correct answer.
  3. The customer organisation stops measuring service performance
  4. Each provider optimises only its own service level targets

Explanation

Mature SIAM depends on providers working within shared processes and integrated governance so end-to-end outcomes improve. Provider-centric optimisation alone can harm the overall service.

Question 9Introduction to SIAM and the SIAM BoK

What distinguishes the SIAM BoK from a prescriptive standard?

  1. It offers good practice and guidance that must be tailored to context Correct answer.
  2. It replaces the need for any other framework
  3. It mandates a single mandatory organisational structure
  4. It applies only to public sector organisations

Explanation

The BoK presents good practice and guidance that organisations adapt to their own context, rather than a rigid mandatory structure. It complements other frameworks rather than replacing them.

Question 10Introduction to SIAM and the SIAM BoK

In SIAM governance, what is the main purpose of the customer organisation retaining decision rights?

  1. To perform all day-to-day technical support tasks
  2. To avoid having to define service levels
  3. To remove the need for provider contracts
  4. To keep control of strategy, priorities, and end-to-end accountability Correct answer.

Explanation

The customer organisation retains decision rights over strategy, priorities, and accountability even when delivery is delegated. This keeps the enterprise in control of outcomes while providers execute.

Question 11Introduction to SIAM and the SIAM BoK

Which statement best captures the relationship between SIAM and ITIL in the BoK's view?

  1. SIAM uses and extends process good practice such as ITIL within a multi-provider context Correct answer.
  2. SIAM replaces ITIL entirely
  3. SIAM and ITIL are unrelated and cannot be combined
  4. ITIL forbids the use of multiple providers

Explanation

SIAM builds on established process good practice, including ITIL, and extends it to coordinate multiple providers. It is complementary rather than a replacement.

Question 12Introduction to SIAM and the SIAM BoK

A SIAM implementation is being planned. Which activity belongs to the 'discovery' or early assessment stage rather than to ongoing operations?

  1. Baselining the current multi-provider landscape and its pain points Correct answer.
  2. Running the daily incident bridge across providers
  3. Executing routine change assessments
  4. Producing the monthly end-to-end service report

Explanation

Early discovery work establishes the current state, including the provider landscape and its issues, before designing the target model. Incident bridges, reporting, and change assessment are ongoing operational activities.

Question 13Introduction to SIAM and the SIAM BoK

Why does SIAM place emphasis on a 'service integrator' being independent of the delivery providers in many models?

  1. To guarantee lower total cost of ownership
  2. To avoid documenting processes
  3. To reduce the risk of a provider favouring its own services when coordinating others Correct answer.
  4. To eliminate the need for service level agreements

Explanation

Independence helps the integrator coordinate fairly across providers without bias toward any one provider's services. It does not remove the need for agreements, documentation, or cost management.

Question 14Introduction to SIAM and the SIAM BoK

Which element is a typical component of the SIAM 'ecosystem' as described in the BoK?

  1. Only the customer's internal staff
  2. Only external auditors and regulators
  3. Only the technology vendors supplying hardware
  4. The customer organisation, the service integrator, and the service providers Correct answer.

Explanation

The SIAM ecosystem comprises the customer organisation, the service integrator, and the service providers working together. It is broader than any single group.

Question 15Introduction to SIAM and the SIAM BoK

In SIAM, what is the role of a 'service integrator' versus a 'prime contractor'?

  1. The integrator avoids any contractual relationship with providers
  2. The prime contractor never uses subcontractors
  3. The integrator coordinates multiple providers, while a prime contractor typically subcontracts and remains the single contractual interface Correct answer.
  4. Both are identical in every respect

Explanation

A prime contractor usually holds the main contract and subcontracts work, remaining the single commercial interface. A service integrator coordinates across multiple providers, which may each contract directly with the customer.

Question 16Introduction to SIAM and the SIAM BoK

Which challenge most directly justifies SIAM's emphasis on integrated processes across providers?

  1. Each provider using its own disconnected incident and change processes Correct answer.
  2. Providers being located in different countries
  3. Providers using different brands of hardware
  4. Providers charging different prices

Explanation

Disconnected processes across providers create handoff failures and unclear ownership, which integrated processes are designed to resolve. Price, location, and hardware brand are secondary factors.

Question 17Introduction to SIAM and the SIAM BoK

An organisation wants one party accountable for end-to-end service performance while keeping separate contracts with each provider. Which SIAM arrangement fits best?

  1. A single prime contractor replacing all other contracts
  2. Letting each provider report only to itself
  3. An internally or externally appointed service integrator coordinating the separate providers Correct answer.
  4. Removing all service level agreements to simplify coordination

Explanation

A service integrator can hold end-to-end accountability while the customer keeps separate contracts with each provider. This preserves multi-sourcing while closing the accountability gap.

Question 18Introduction to SIAM and the SIAM BoK

Which statement about the SIAM BoK's treatment of 'culture and behaviour' is most accurate?

  1. It requires all providers to share one corporate culture
  2. It limits cultural concerns to internal staff only
  3. It recognises that collaborative behaviour across providers is essential to integration success Correct answer.
  4. It treats culture as irrelevant to service integration

Explanation

The BoK stresses that integration depends on collaborative behaviour and trust across organisational boundaries, not just process and tooling. Shared corporate culture is not required, but cooperative behaviour is.

Question 19Introduction to SIAM and the SIAM BoK

Which of these is the clearest example of the 'retained capability' the customer organisation keeps in a SIAM model?

  1. Owning service strategy and setting end-to-end service levels Correct answer.
  2. Patching servers in the data centre
  3. Writing application code for a provider's product
  4. Resetting user passwords at the service desk

Explanation

Retained capability covers the strategic and governance work the customer keeps, such as setting strategy and defining end-to-end service levels. Hands-on delivery tasks are typically delegated to providers.

Question 20Introduction to SIAM and the SIAM BoK

Why does SIAM recommend measuring service performance end to end rather than only per provider?

  1. End-to-end measures reveal the actual experience and outcomes that users and the business receive Correct answer.
  2. Per-provider metrics are illegal in outsourcing
  3. End-to-end measures remove the need for provider metrics entirely
  4. Provider-level metrics always understate cost

Explanation

End-to-end measurement captures the real service experience and business outcomes, which per-provider metrics can miss when handoffs fail. Provider metrics remain useful but are not sufficient on their own.

Question 21SIAM principles and the service integration mindset

In a SIAM ecosystem, what is the primary purpose of the service integrator role?

  1. To act as the single external vendor supplying all managed services
  2. To replace the service desk with an automated self-service portal
  3. To orchestrate and coordinate services delivered by multiple internal and external providers Correct answer.
  4. To own and operate every underpinning technology component directly

Explanation

The service integrator is the coordinating layer that brings together services from many providers and ensures they combine into coherent end-to-end outcomes for the business. It does not need to own or operate every component itself, because its value lies in orchestration, governance, and cross-provider accountability rather than direct delivery of all technology.

Question 22SIAM principles and the service integration mindset

Which statement best captures the shift in mindset that SIAM requires compared with traditional service management?

  1. The business moves from managing individual supplier contracts to governing an integrated set of outcomes Correct answer.
  2. Providers focus on optimizing their own contractual scope and service level targets
  3. The customer takes full operational control of every provider's internal processes
  4. Service levels are replaced entirely by informal trust relationships between providers

Explanation

SIAM shifts attention from managing separate supplier contracts and their individual targets toward governing end-to-end outcomes across the whole ecosystem. Providers still have contracts and targets, but the business and integrator focus on how the combined services deliver value rather than on isolated scope optimization.

Question 23SIAM principles and the service integration mindset

A large organization has four outsourced IT providers, each reporting separate service levels to a different business unit. Which SIAM principle most directly addresses the resulting fragmented accountability?

  1. Outsourcing governance to the largest of the four providers
  2. Establishing end-to-end service ownership across the provider ecosystem Correct answer.
  3. Reducing the number of providers to one to simplify contracts
  4. Adopting a single toolset for all providers regardless of their processes

Explanation

SIAM addresses fragmentation by establishing end-to-end ownership of services that spans all providers, so accountability is aligned to business outcomes rather than to individual contracts. This cross-provider ownership is the core mechanism that turns a set of suppliers into an integrated service ecosystem.

Question 24SIAM principles and the service integration mindset

Why does SIAM emphasize a culture of collaboration and transparency between competing providers?

  1. It allows the integrator to avoid defining any formal processes or service levels
  2. It removes the need for governance because providers will self-organize
  3. It enables providers to share information needed to resolve cross-provider incidents and improve end-to-end services Correct answer.
  4. It guarantees that each provider will exceed its contractual service level targets

Explanation

Cross-provider collaboration and transparency give providers the shared information they need to diagnose and resolve incidents that span organizational boundaries. Without that openness, each provider sees only its own slice and end-to-end service quality suffers, so SIAM builds collaborative behaviors alongside formal governance.

Question 25SIAM principles and the service integration mindset

What does the SIAM concept of 'end-to-end service' primarily mean?

  1. A service considered from the business outcome back through all contributing providers and components Correct answer.
  2. A service delivered entirely by one provider from design to retirement
  3. A service whose contract covers the full financial year
  4. A service that is monitored only at the network layer

Explanation

End-to-end thinking means looking at a service from the business outcome backward, tracing every provider and component that contributes to it. This perspective lets the integrator manage the whole chain rather than optimizing isolated segments, which is central to the SIAM mindset.

Question 26SIAM principles and the service integration mindset

Which behavior is most consistent with the service integration mindset when a provider discovers a problem that affects another provider's service?

  1. Wait for the affected provider to raise a ticket before sharing any information
  2. Escalate through the integrator so the cross-provider impact is assessed and coordinated Correct answer.
  3. Document it internally and close it once its own component is restored
  4. Resolve it silently within its own scope to avoid breaching its own service level

Explanation

The integration mindset favors early, transparent escalation through the integrator so cross-provider impacts are assessed and coordinated. Silently closing a local fix may restore one component while leaving the end-to-end service degraded, which undermines the shared outcome.

Question 27SIAM principles and the service integration mindset

In SIAM, what is the role of the service integrator with respect to service levels across multiple providers?

  1. It replaces all provider service levels with a single generic target
  2. It allows each provider to set service levels independently without coordination
  3. It removes service levels from contracts and relies on verbal commitments
  4. It negotiates and aligns provider service levels so they collectively support business outcomes Correct answer.

Explanation

The integrator aligns and, where needed, negotiates service levels so that the combined commitments of all providers add up to the business outcome. Individual targets that are internally sensible can still conflict at the seams, so coordination across providers is a defining integrator responsibility.

Question 28SIAM principles and the service integration mindset

An organization is designing its SIAM governance. Which principle should guide how decision rights are distributed?

  1. Decision rights should remain undocumented so they can flex organically
  2. All decisions should sit with the largest external provider to reduce meetings
  3. Decision rights should be clearly defined across the business, integrator, and providers Correct answer.
  4. Each provider should hold veto power over cross-provider changes

Explanation

SIAM governance depends on clearly defined decision rights so that the business, integrator, and providers each know what they own and where escalation belongs. Undefined or unbalanced rights cause delays and disputes at the very boundaries where integration is needed.

Question 29SIAM principles and the service integration mindset

Which outcome best demonstrates that a SIAM ecosystem is delivering integrated value rather than siloed delivery?

  1. Each provider meets its own service level while customers still report a fragmented experience
  2. The number of supplier contracts is reduced by half
  3. A customer request spanning three providers is resolved without repeated handoffs or re-explanation Correct answer.
  4. Each provider reports to a separate governance board

Explanation

Integrated value shows up when a customer need that crosses provider boundaries is handled seamlessly, without the customer having to re-explain or chase handoffs. Providers meeting their own targets while the overall experience remains fragmented is the classic symptom of siloed rather than integrated delivery.

Question 30SIAM principles and the service integration mindset

What is the significance of a 'service integration and management ecosystem' compared with a simple supply chain?

  1. It describes only the contractual hierarchy of prime and sub-contractors
  2. It removes the need for any central coordination function
  3. It recognizes interdependent providers, including internal teams, that co-create value around shared outcomes Correct answer.
  4. It applies exclusively to cloud providers and excludes internal IT

Explanation

An ecosystem framing recognizes that value is co-created by interdependent parties, including internal teams and multiple external providers, around shared business outcomes. This is broader than a linear supply chain and explains why orchestration and relationship management matter as much as contracts.

Question 31SIAM principles and the service integration mindset

A provider in a SIAM ecosystem is reluctant to share its incident data with other providers. Which SIAM principle is being most directly undermined?

  1. Standardization of technology platforms
  2. Transparency and information sharing across the ecosystem Correct answer.
  3. Continuous improvement through benchmarking
  4. Financial chargeback to business units

Explanation

SIAM depends on transparency and information sharing so providers can coordinate across boundaries and the integrator can see the true end-to-end state. Withholding incident data breaks that shared visibility and makes cross-provider resolution and improvement far harder.

Question 32SIAM principles and the service integration mindset

Why does SIAM place strong emphasis on measuring end-to-end service performance in addition to provider-level metrics?

  1. Provider metrics can look healthy while the combined customer experience is poor Correct answer.
  2. End-to-end metrics are cheaper to collect than provider metrics
  3. End-to-end metrics eliminate the need for provider contracts
  4. Provider metrics are always inaccurate and should be ignored

Explanation

Each provider can meet its own targets while the seams between them cause delays and poor customer experience, so end-to-end measurement is needed to reveal those gaps. Provider metrics remain useful, but they must be read alongside integrated outcome measures rather than in isolation.

Question 33SIAM principles and the service integration mindset

Which statement best describes the SIAM principle of 'one team' culture across organizational boundaries?

  1. Team membership is limited to staff employed by the integrator
  2. Each provider must adopt identical internal processes and tools
  3. People across business, integrator, and providers behave as a unified team focused on shared outcomes Correct answer.
  4. All providers must merge into a single legal entity

Explanation

The 'one team' principle is about behavior and shared purpose across organizational boundaries, not about legal or structural mergers. People from the business, the integrator, and providers collaborate as if they were one team focused on the same outcomes, even while remaining separate organizations.

Question 34SIAM principles and the service integration mindset

A business unit wants a new capability that requires changes from three providers. How should the service integration mindset frame the request?

  1. As a single business outcome to be planned and coordinated across the contributing providers Correct answer.
  2. As a procurement exercise to select a fourth provider to own the outcome
  3. As a request to be deferred until the next contract renewal cycle
  4. As three separate change requests, each optimized to the receiving provider's process

Explanation

Framing the need as a single business outcome lets the integrator plan and coordinate the contributions of all three providers toward that outcome. Splitting it into isolated change requests optimizes each provider's process but risks delivering an incomplete or poorly integrated result.

Question 35SIAM principles and the service integration mindset

What distinguishes the SIAM integrator's accountability from that of a traditional service delivery manager?

  1. The integrator holds no accountability because providers are self-managing
  2. The integrator is accountable only for the performance of internal staff
  3. The integrator is accountable for how provider services combine into business outcomes, not for running every component Correct answer.
  4. The integrator is accountable only for contract administration and invoicing

Explanation

The integrator is accountable for the integration itself: how the services of many providers combine to deliver business outcomes. It does not need to run every component, but it owns the coordination, assurance, and governance that make the combined service work.

Question 36SIAM principles and the service integration mindset

Which practice best reflects the SIAM principle of continuous improvement across a multi-provider ecosystem?

  1. Improvement is deferred until a new provider is onboarded
  2. Only the integrator is permitted to propose any improvement
  3. Providers and the integrator jointly review end-to-end performance and agree cross-provider improvements Correct answer.
  4. Each provider improves its own processes in isolation and reports the results separately

Explanation

Continuous improvement in SIAM is a joint activity: the integrator and providers review end-to-end performance together and agree on improvements that may cross organizational boundaries. Isolated improvements can optimize one segment while leaving the overall service unchanged or worse.

Question 37SIAM principles and the service integration mindset

A SIAM ecosystem is being designed. Why should the business retain ownership of the service integration function rather than delegating it entirely to a provider?

  1. To reduce the number of contracts to a single agreement
  2. To avoid having to define business requirements
  3. To keep control of how outcomes are governed and avoid a provider marking its own work Correct answer.
  4. To eliminate the need for provider service levels

Explanation

Retaining integration ownership keeps the business in control of governance and outcomes and avoids a provider being both deliverer and judge of its own performance. It also preserves the business's ability to balance and direct competing providers in line with its own priorities.

Question 38SIAM principles and the service integration mindset

Which tension is inherent in a SIAM ecosystem, and how does the integration mindset manage it?

  1. The business must stop measuring provider performance entirely
  2. Internal IT must be excluded to avoid conflicts of interest
  3. Providers must merge their finances to avoid any competition
  4. Providers compete commercially yet must collaborate operationally, so the integrator balances competition with shared outcomes Correct answer.

Explanation

Providers often compete for business while needing to collaborate closely on day-to-day operations, and the integrator manages this tension by aligning incentives and shared outcomes. Ignoring the tension or forcing mergers does not resolve it; explicit governance and collaborative behaviors do.

Question 39SIAM principles and the service integration mindset

What is the primary reason SIAM defines shared processes and common data standards across providers?

  1. To force every provider to use identical software licenses
  2. To enable consistent information flow and coordinated handling of cross-provider activities Correct answer.
  3. To transfer all process ownership to the largest provider
  4. To reduce the number of providers in the ecosystem

Explanation

Shared processes and common data standards let information flow consistently between providers and allow cross-provider activities such as incident and change handling to be coordinated. They create the interoperability that integration depends on, without requiring identical tools or ownership transfers.

Question 40SIAM principles and the service integration mindset

An integrator notices that providers consistently blame each other for cross-boundary delays. Which action best reflects the SIAM mindset?

  1. Escalate to the largest provider and ask it to impose order on the others
  2. Record the disputes and leave resolution to the next contract negotiation
  3. Introduce penalties for every provider involved until blame stops
  4. Facilitate a joint review of the end-to-end flow to find systemic causes and agree shared fixes Correct answer.

Explanation

The SIAM mindset treats recurring cross-boundary problems as systemic and addresses them through joint review of the end-to-end flow and agreed shared fixes. Blaming individuals or providers, or deferring to contract negotiations, leaves the underlying integration weakness in place.

Question 41SIAM structural elements: service integrator, service providers, and retained capabilities

In a SIAM ecosystem, which role is accountable for coordinating multiple internal and external service providers and for end-to-end service performance across them?

  1. The service integrator Correct answer.
  2. The enterprise service desk analyst
  3. The single external service provider
  4. The retained capability owner

Explanation

The service integrator is the function that orchestrates and coordinates the contributions of many service providers so that end-to-end services are delivered coherently. Accountability for cross-provider integration and overall service performance sits with this integrating role rather than with any individual provider.

Question 42SIAM structural elements: service integrator, service providers, and retained capabilities

Which statement best describes a service provider in the SIAM structural model?

  1. An entity that delivers one or more services to the customer or to other providers under agreed terms Correct answer.
  2. An entity that permanently absorbs the customer's retained capabilities
  3. An entity that audits the service integrator's contractual compliance
  4. An entity that owns the customer's IT strategy and governance decisions

Explanation

Service providers are the delivery entities in the ecosystem, supplying services against agreed terms to the customer or to other providers. They may be internal or external, and their scope is defined by the services they supply rather than by governance ownership.

Question 43SIAM structural elements: service integrator, service providers, and retained capabilities

What is meant by 'retained capabilities' in a SIAM operating model?

  1. The skills, processes, and accountabilities the customer keeps in-house to govern and direct the ecosystem Correct answer.
  2. The backlog of incidents retained for later resolution
  3. The tooling hosted in the service integrator's data centre
  4. The services the customer outsources to the lowest-cost provider

Explanation

Retained capabilities are the competencies and decision rights the customer deliberately keeps rather than delegates, such as strategy, governance, architecture, and commercial management. They enable the customer to direct and control the multi-provider ecosystem.

Question 44SIAM structural elements: service integrator, service providers, and retained capabilities

A customer decides to keep enterprise architecture and commercial contract management in-house while outsourcing all run and change delivery. Which SIAM structural element does this describe?

  1. Provider federation
  2. Service catalogue federation
  3. Service integrator delegation
  4. Retained capabilities Correct answer.

Explanation

Capabilities the customer chooses not to delegate remain with the customer as retained capabilities. Enterprise architecture and commercial management are classic examples because they preserve direction and control over providers.

Question 45SIAM structural elements: service integrator, service providers, and retained capabilities

Which arrangement is a recognised SIAM structural option for the service integrator?

  1. Only a single external integrator
  2. An internal integrator, an external integrator, or a hybrid of both Correct answer.
  3. Only a consortium of all providers jointly integrating
  4. Only the customer's service desk acting as integrator

Explanation

SIAM recognises that the integration role can be performed internally by the customer, externally by a dedicated integrator provider, or through a hybrid arrangement. The choice depends on capability, risk appetite, and sourcing strategy.

Question 46SIAM structural elements: service integrator, service providers, and retained capabilities

Which capability is most likely to remain retained by the customer rather than delegated to the service integrator?

  1. Running day-to-day incident coordination across providers
  2. Managing the provider performance reporting cycle
  3. Setting the enterprise IT strategy and risk appetite Correct answer.
  4. Operating the shared service management toolset

Explanation

Strategy setting and risk appetite define the customer's direction and tolerance, so they are normally retained to preserve control. Operational coordination, tooling, and performance reporting can be delegated to the integrator.

Question 47SIAM structural elements: service integrator, service providers, and retained capabilities

Why does SIAM insist that the customer retains certain capabilities even when using an external service integrator?

  1. To avoid the need for service level agreements
  2. To allow the integrator to set the customer's risk appetite
  3. To reduce the number of service providers in the ecosystem
  4. To preserve direction, control, and accountability for outcomes that cannot be outsourced Correct answer.

Explanation

Some accountabilities, such as governance, strategy, and setting risk tolerance, belong to the customer and cannot be transferred to a provider. Retaining them keeps the customer in control of the ecosystem it commissions.

Question 48SIAM structural elements: service integrator, service providers, and retained capabilities

In SIAM terminology, what distinguishes an internal service provider from an external one?

  1. Whether the provider uses ITIL or another framework
  2. Whether the provider sits inside the customer organisation or is contracted from outside it Correct answer.
  3. Whether the provider delivers services at all
  4. Whether the provider reports to the service integrator

Explanation

The internal versus external distinction concerns organisational boundary and contractual relationship, not framework adoption or reporting lines. Both types can deliver services and be coordinated by the integrator.

Question 49SIAM structural elements: service integrator, service providers, and retained capabilities

A customer retains governance and strategy but delegates cross-provider coordination to a dedicated external integrator. Which two structural elements are being combined?

  1. An internal service integrator and a service desk
  2. Retained capabilities and a provider federation
  3. Retained capabilities and an external service integrator Correct answer.
  4. A single provider and a service catalogue

Explanation

The customer keeps governance and strategy as retained capabilities while an external integrator performs the coordination role. This is a common hybrid pattern combining both structural elements.

Question 50SIAM structural elements: service integrator, service providers, and retained capabilities

Which activity should be performed by the service integrator rather than by an individual service provider?

  1. Delivering the technical components of its own contracted service
  2. Resolving incidents within its own domain of responsibility
  3. Managing its own staff rosters and training
  4. Maintaining the end-to-end view of cross-provider dependencies and interfaces Correct answer.

Explanation

The integrator owns the cross-provider, end-to-end perspective, including dependencies and interfaces between providers. Each provider remains responsible for delivering and managing its own contracted service.