What happens when a column is marked as Deprecated?

What happens when a column is marked as Deprecated?

• A. The column becomes read-only and cannot be queried.
• B. All data in the column will be deleted.
• C. No more data will be extracted into the column, although any data already there will not be deleted.
• D. The column is ignored during export but used in joins.

Answer: (C)

Deprecating a column signals that it should no longer be used for new data, while preserving what’s already stored. The key effect is that no new values will be written into that column, but any existing data remains in place and is not deleted. This lets you keep historical information intact while you migrate away from the column or plan its removal in a future release. That’s why the correct description is that no more data will be extracted into the column, although data already there will not be deleted. The other notions—that it becomes read-only, that data is deleted, or that it’s ignored in exports but still used in joins—don’t match how deprecation typically functions.

Deprecating a column signals that it should no longer be used for new data, while preserving what’s already stored. The key effect is that no new values will be written into that column, but any existing data remains in place and is not deleted. This lets you keep historical information intact while you migrate away from the column or plan its removal in a future release. That’s why the correct description is that no more data will be extracted into the column, although data already there will not be deleted. The other notions—that it becomes read-only, that data is deleted, or that it’s ignored in exports but still used in joins—don’t match how deprecation typically functions.