An organisation must keep certain regulated datasets inside its own data centre but wants elastic compute for analytics on non-regulated data. Which deployment approach for watsonx.data fits?
Select an answer to reveal the explanation.
Short Explanation
When regulated data has to stay put and other workloads need elastic compute, hybrid is the fit. You keep the regulated datasets in your own data centre and run the non-regulated analytics in the cloud. One governance model across both keeps it manageable.
Full Explanation
A hybrid deployment fits because a residency constraint applies to specific data, not to the entire platform. It lets the regulated data remain in the data centre under local control while other workloads use cloud compute, with a consistent governance model across both.
A cloud-only deployment that moves the regulated data with encryption in transit is incorrect because encryption in transit protects data on the wire; it does not change where the data comes to rest. A residency requirement is about location, and moving the data to the cloud violates it regardless of the encryption used.
An on-premises-only deployment is incorrect because it applies the strictest constraint to everything. Non-regulated workloads gain nothing from being confined and lose the elasticity the organisation asked for.
A separate independent deployment per dataset, with no shared governance between them, is incorrect because fragmenting into ungoverned islands sacrifices the unified policy and metadata that make the platform worth running.
For the exam, match deployment to the specific constraint - residency, latency, existing investment - rather than treating it as a single all-or-nothing choice.