A warehouse team will retire a legacy permits table in ninety days, but consumers still discover it as if it were fully supported. What catalog action should accompany the technical deprecation?
Select an answer to reveal the explanation.
Short Explanation
Deprecation without a catalog notice is like closing a bridge with no detour signs. Mark the permits table deprecated, show the retirement date, and point people to the successor. Surprises on cutover day are how dashboards break.
Full Explanation
Technical lifecycle metadata should announce deprecation and retirement dates in the catalog so consumers can migrate before removal. Clear successor guidance reduces incident risk and supports orderly cutovers. Immediate silent deletion of catalog entries or unmarked surprises both fail change management. Nightly renames without governed deprecation metadata create chaos rather than controlled retirement.