A proof of concept used one engine, one catalog and one bucket, all created by a single administrator working in the console. Moving to production, which platform capability becomes essential that the proof of concept did not exercise?
Select an answer to reveal the explanation.
Short Explanation
One person with admin rights is a perfectly workable proof of concept, but it won't hold up in production. You need governance: defined roles and policies so access is granted by rule, not by one administrator's account.
Full Explanation
The capability that becomes essential is governance: defined roles and policies, so access is granted by rule rather than by one administrator's account. The single-administrator proof of concept never tests entitlement, because there is only one identity and it can do everything. Production introduces many users with differing rights, which is precisely what the governance layer exists to express - roles, and policies attached to catalogs, schemas and tables.
The object-storage claim is incorrect because object storage was already in use; it is the storage layer at any scale, not a production-only component.
The catalog-optional claim is incorrect because the catalog is not optional. Without it there are no tables for an engine to query, regardless of how many engines exist.
The query-history claim is incorrect because query history is a diagnostic and review capability. It is genuinely valuable in production, but queries execute without it - it is not a prerequisite.
For the exam, associate the move from proof of concept to production with governance, not with new infrastructure.