When a Component is released to shared pool, Which of the following statements hold true.
-
It becomes Obsolete
-
It becomes Frozen
-
It is still available for Modeling
-
None of above
When a component is released to a shared pool, it becomes frozen, meaning its version is locked and it cannot be modified. Other users can fetch and use this frozen version, but changes require creating a new version. It does not become obsolete (still useful), and it's no longer available for modeling changes (that happens before release). Freezing ensures everyone works with consistent, unchanging component versions.
In a repository/modeling tool's component lifecycle, releasing a component to the shared pool marks it as a stable, published version — it becomes Frozen, meaning its definition can no longer be modified in place (further changes require creating a new version). It doesn't become 'Obsolete' (that's a distinct later lifecycle state for retired components), and it's specifically no longer available for ad-hoc modeling/editing once frozen, contradicting option C. 'None of the above' is wrong since Frozen is a documented, correct state transition.