An administrator is troubleshooting a pilot deployment and wants the most appropriate next step. Which approach best demonstrates Infrastructure Manager in a IBM Certified watsonx Data Lakehouse Engineer environment?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Here's the deal: Infrastructure Manager in IBM watsonx.data is your engine room — the control plane where you provision Presto clusters, start and stop Spark instances, manage services, and monitor what's running. Think of it like the breaker panel in a data center: you don't run cables from there, but you absolutely need it to power everything else on or off correctly.
Full explanation below image
Full Explanation
IBM watsonx.data's Infrastructure Manager provides the administrative interface for provisioning and managing query engines (Presto, Spark), associating engines with catalogs, configuring engine resources, and monitoring engine status. It is the designated management surface for all compute resources within the platform, as opposed to the Data Manager (for data assets) or the Query Workspace (for SQL execution). Using query history to provision engines (Option B) confuses a diagnostic read-only tool with an administrative provisioning tool — query history records executions but cannot create or modify infrastructure. Editing raw object files to start services (Option C) is not a supported operation; watsonx.data services are managed through the platform API and UI, not by editing files in object storage. Creating BI dashboards to manage infrastructure (Option D) uses the wrong interface entirely — BI dashboard tools are for data visualization, not for starting, stopping, or configuring platform services. The certification expects candidates to know which management interface applies to which platform function, and Infrastructure Manager is specifically the engine and service lifecycle control plane.