Marking a value sensitive controls its display in ordinary output. That mark alone still allows the value to be stored in state and plan artifacts. Ephemeral values have a different purpose: Terraform omits them from those artifacts and restricts where they can flow.
A supported write-only resource argument can receive a value without storing that argument in state or a plan. Check both the Terraform version and the provider schema before relying on this behavior. The external system still receives the value, so its own secret handling matters. This lesson checks those boundaries through scenarios; the lab provider doesn't implement ephemeral resources or secret rotation.
Inspect where a secret is stored as well as whether the console displays it.