An engine is deleted and recreated after a configuration change. What is the effect on the team's ability to review executions from before the change?
Select an answer to reveal the explanation.
Short Explanation
The record outlives the engine. That matters, because engines get resized and replaced routinely, and you'd otherwise lose your troubleshooting evidence every time.
Full Explanation
The correct answer is the one saying the recorded history of past executions remains available for review and is not a property of a running engine. Execution records are retained by the platform independently of the compute that produced them, so replacing an engine does not erase the operational record. The claim that all past executions become unreadable because the engine that ran them no longer exists is incorrect because history would be nearly useless if it vanished with the ephemeral resource that produced it - engines are routinely resized and replaced. The claim that past executions must be replayed against the new engine before they can be reviewed is incorrect because there is no replay requirement; the record is read, not re-executed. The claim that history is retained only while the queries' tables remain registered is incorrect because retention is not conditional on the referenced tables still being registered. For the exam, treat compute as ephemeral and the operational record as durable.