If you modify a component, you should expect that change to affect all contracts and applications where that component is used.

If you modify a component, you should expect that change to affect all contracts and applications where that component is used.

• A. It will only affect the current contract.
• B. It will affect all contracts and applications where that component is used.
• C. It has no effect until you propagate manually.
• D. It only affects new claims.

Answer: (B)

When a component is shared across many contracts and applications, it acts as a single source of behavior and data that all dependents rely on. If you modify that component, every contract or application that uses it will experience the change. That ripple effect is why such components require careful versioning, compatibility planning, and broad testing: you need to validate how the change affects all consumers and manage updates across the board. In practice, this means changes aren’t isolated to one contract; you typically introduce a new version of the component and update dependent contracts and apps to reference that version, ensuring you can test and control the rollout. The idea that only the current contract would be affected, or that there’s no effect until you propagate manually, or that only new claims would be affected, doesn’t fit how shared components work.

When a component is shared across many contracts and applications, it acts as a single source of behavior and data that all dependents rely on. If you modify that component, every contract or application that uses it will experience the change. That ripple effect is why such components require careful versioning, compatibility planning, and broad testing: you need to validate how the change affects all consumers and manage updates across the board.

In practice, this means changes aren’t isolated to one contract; you typically introduce a new version of the component and update dependent contracts and apps to reference that version, ensuring you can test and control the rollout. The idea that only the current contract would be affected, or that there’s no effect until you propagate manually, or that only new claims would be affected, doesn’t fit how shared components work.