The correct option is Establishing formal policies roles and procedures that enforce consistent and auditable architecture decisions.

Formal oversight frameworks create defined roles approval processes and documented procedures that make architecture decisions traceable and auditable. They ensure that decisions are evaluated against standards and business objectives and that responsibility is assigned for approvals and outcomes.

Mechanisms such as architecture review boards gate reviews and change control provide consistent checkpoints and evidence of compliance. That combination of policies roles and procedures is what enforces consistent and accountable decision making across the enterprise.

Allowing teams to make technology decisions independently is incorrect because independent decisions without governance lead to inconsistent architectures fragmented systems and unclear accountability. Such an approach often increases integration costs and technical debt.

Cloud Identity and Access Management is incorrect because it describes identity and access controls rather than an enterprise oversight framework. Identity and access management is a useful security control but it does not by itself establish enterprise wide decision making policies or audit processes for architecture.

Permitting informal ad hoc decision making to speed up project delivery is incorrect because ad hoc decisions sacrifice consistency and auditability even if they may accelerate delivery in the short term. This approach undermines long term maintainability governance and alignment with business goals.

Full AWS Practitioner Certification Question