Domain 3: Operation
IBM Certified watsonx Data Lakehouse Engineer v1 - Associate · 58 questions
- What is the first step when provisioning IBM watsonx.data on IBM Cloud?
- Which IBM Cloud IAM role grants a user the ability to administer watsonx.data resources including creating engines and catalogs?
- What is the primary operational reason for pausing a Presto engine in watsonx.data when it is not in use?
- Where in watsonx.data can an administrator monitor the status and resource usage of currently running Presto queries?
- How can administrators monitor running Spark jobs in IBM watsonx.data?
- What is the purpose of resource groups in IBM watsonx.data?
- How would you increase the processing capacity of a Presto engine in watsonx.data to handle a spike in query load?
- In watsonx.data; what is the recommended approach for protecting Iceberg table data against accidental deletion?
- A data engineer accidentally overwrites critical data in an Iceberg table. What operational procedure can restore the table to its previous state?
- A Presto query in watsonx.data is running significantly slower than expected on an Iceberg table. Which diagnostic step should be taken first?
- A Presto engine in watsonx.data fails with 'metastore connection failed' errors. What is the most likely cause?
- Which combination of practices most effectively reduces watsonx.data operational costs?
- In watsonx.data; which access control model governs who can query specific tables?
- A workload consists of short interactive BI queries that run frequently. Which Presto engine configuration is most appropriate?
- How are user identities managed in IBM watsonx.data on IBM Cloud?
- A Presto query fails with an 'Out of memory' error in watsonx.data. What is the most appropriate first response?
- Why is it important to collect table statistics for Iceberg tables in watsonx.data?
- Where would you look to diagnose a failed Presto query that returned an ambiguous error message in watsonx.data?
- In a watsonx.data deployment with both Presto and Spark engines; how is access control enforced consistently across both engines?
- What mechanism in watsonx.data/Iceberg would you configure to automatically remove data older than 90 days from a table?
- How would you upgrade the Presto engine version in a production watsonx.data environment with minimal disruption?
- An Iceberg table's object storage size has grown excessively over six months due to retained snapshots. What operation should be run?
- In watsonx.data; what happens when multiple users submit queries simultaneously and the engine reaches its concurrency limit?
- A data engineering team has provisioned watsonx.data and added a Presto engine. They now have a governed catalog of Iceberg tables that analysts need to query through that engine, but the tables do not appear when analysts connect. In Infrastructure Manager, what still has to be done?
- A team has loaded a set of Iceberg tables into a bucket but analysts cannot find them in watsonx.data. Which interface is used to browse and register lakehouse data assets so they become discoverable?
- An analyst wants to write and run ad hoc SQL against lakehouse tables from within watsonx.data. Which interface should they use?
- A new analyst joins a team and needs to read three specific schemas. What is the correct way to provision their access?
- An organization runs a Presto engine in watsonx.data that is heavily used during business hours and idle overnight. They want to reduce compute cost without losing the engine's configuration, its catalog associations, or the data it serves. What action in Infrastructure Manager fits that requirement?
- A team decides not to register newly landed data in the catalog, reasoning that leaving it unregistered keeps it flexible until the schema settles. What is the consequence?
- A query that succeeded last week now runs far longer, and the team wants to compare the two executions. Which feature supports this?
- Why is granting broad administrator rights "for convenience" a governance failure?
- A watsonx.data administrator needs to make a new Amazon S3 bucket of Iceberg data available for querying. They have added the bucket in Infrastructure Manager and supplied valid credentials, but no tables are queryable yet. What is the missing step?
- Which set of tasks is Data manager the appropriate tool for?
- Why is trying to diagnose a failed SQL statement from the storage bill an unsound approach?
- A team relies on obscure table names to keep sensitive data from being found. Why is this inadequate?
- Analysts report that a watsonx.data Presto engine returns results acceptably for small queries but times out on large joins that scan several months of Iceberg data. The engine has been running on its original small configuration since the pilot. Which change in Infrastructure Manager addresses the cause?
- An analyst asks how to find out which columns a governed table contains and what types they are, without running a query against it. What is the appropriate route?
- A team suggests deleting query history to improve platform performance. What is wrong with this?
- A pipeline's service identity currently holds broad write access across all catalogs, but the pipeline writes to only one schema. What should be done?
- An enterprise already operates a Presto cluster outside watsonx.data and does not want to migrate those workloads. They still want watsonx.data to govern the metadata and expose the same tables. What does Infrastructure Manager let them do?
- A process document says table metadata changes are requested by emailing the data platform team, who apply them manually. What is the weakness of this approach?
- An analyst reports that a query "just does not work" without further detail. What is the most efficient first step for the administrator?
- Which statement about permissions and engines in watsonx.data is correct?
- A team is adding a similarity-search feature to an application and needs watsonx.data to store and query vector embeddings alongside its existing lakehouse tables. Which service should the administrator add in Infrastructure Manager?
- What does registering a data asset in watsonx.data accomplish?
- What information does query history provide that supports both troubleshooting and capacity planning?
- A column contains data that only a small compliance team may see, while the rest of the table is widely useful. What is the appropriate control?
- During a review of a watsonx.data deployment, an architect wants to confirm which catalogs each engine is currently serving and which buckets those catalogs sit on, before approving a change. Where is that relationship shown?
- A growing lakehouse now holds several hundred tables and analysts increasingly cannot tell which table to use. Which practice, supported through Data manager, most directly addresses this?
- Which pairing of interface to task is correct?
- During an access review, a group is found to hold permissions it no longer needs after a reorganisation. What is the correct action?
- A watsonx.data administrator is decommissioning a Presto engine that was created for a project that has ended. Another team's catalog is still associated with that engine. What should the administrator do before deleting it?
- After a table is registered in Data manager, an analyst still cannot query it through the engine they use. What should be checked first?
- An engine is deleted and recreated after a configuration change. What is the effect on the team's ability to review executions from before the change?
- Which statement best summarises how permissions should be set in watsonx.data?
- A data engineering group needs to run heavy batch transformation jobs that write curated Iceberg tables, while analysts continue to run interactive SQL against those same tables. Which approach uses Infrastructure Manager correctly?
- Which statement best summarises the role of Data manager in watsonx.data?
- Which statement correctly describes the operational role of the query workspace and query history?