If the origin volume is moved to a different volume or location, what is the effect on the related FlexCache blocks?

• A. Origin move operation invalidates affected cache blocks.
• B. Origin move has no impact on cache.
• C. Cache blocks are migrated automatically.
• D. Origin move triggers full reinitialization.

Answer: (A)

When the origin volume is moved, the blocks in the FlexCache that refer to that origin become invalid. FlexCache stores data blocks from the origin to speed up access, but those blocks are tied to the origin’s location and identity. If the origin is relocated, the cached data can no longer be guaranteed to map correctly to the origin’s current state, so the system marks the affected cache blocks as invalid to prevent serving potentially stale or mismatched data. Subsequent access will fetch fresh data from the origin and repopulate the cache as needed.

This aligns with the behavior of avoiding stale data after a topology change. The other options imply no impact, automatic migration, or a full restart, none of which reflect how FlexCache maintains data integrity when the origin’s location changes.