Using SELECT * in a Query Activity can cause which behavior regarding fields added after the query is saved?

Using SELECT * in a Query Activity can cause which behavior regarding fields added after the query is saved?

• A. It automatically includes newly added fields.
• B. It snapshots the fields in the data extension at save time, so new fields are not automatically included.
• C. It expands to include all fields every time the query runs.
• D. It returns a single aggregated value.

Answer: (B)

In a Query Activity, the fields that are selected are determined by what exists in the data extension at the moment you save the query. Using SELECT * captures a snapshot of those fields, so any new fields you add later aren’t included automatically. To include new fields, you’d need to edit the query and re-save (or explicitly list the fields you want in the SELECT). This behavior keeps the query stable across runs and avoids unexpected schema changes.

In a Query Activity, the fields that are selected are determined by what exists in the data extension at the moment you save the query. Using SELECT * captures a snapshot of those fields, so any new fields you add later aren’t included automatically. To include new fields, you’d need to edit the query and re-save (or explicitly list the fields you want in the SELECT). This behavior keeps the query stable across runs and avoids unexpected schema changes.