A pilot deployment's policy was configured once during the initial demo and never revisited. What is the concern with treating that setup as final?
Select an answer to reveal the explanation.
Short Explanation
You don’t set policy once for a demo and call it done. Obligations, use cases, and risk profiles change, so you have to revisit the setup to keep it aligned.
Full Explanation
The correct choice is the one stating that policy setup is not a one-time demo task and needs revisiting as obligations, use cases, and risk profiles change. Regulatory requirements, business use cases, and asset risk profiles change, so a configuration frozen at demo time drifts out of alignment with what the organisation actually needs to govern.
The option saying there is no concern because a correctly configured policy remains accurate indefinitely is wrong: obligations are not static; they evolve with regulation, business direction, and assets governed.
The option saying the only concern is visual outdatedness versus newer platform versions is wrong: the issue is substantive misalignment with current obligations, not presentation.
The option limiting the concern to a major platform software update is wrong: obligations can change independently of the platform's release schedule.
For the exam, treat policy configuration as an ongoing responsibility, not a one-time setup step.