IBM Certified watsonx Data Lakehouse Engineer v1 - Associate practice questions
IBM · C1000-190 · 300 questions
Original practice questions for the IBM C1000-190 watsonx Data Lakehouse Engineer certification exam.
This course contains the use of artificial intelligence.
About the C1000-190 exam
- Exam fee
- $200 USD
- Time allowed
- 1 hour 30 minutes
- Questions
- 62
- Passing score
- 41 of 62 correct
- Languages
- English
- Format
- Proctored exam booked through Pearson VUE; an optional Assessment Exam, Sample Test and Study Guide PDF are published alongside it
Exam details published by the vendor, checked 25 August 2026. Vendors change fees and formats without notice — confirm on the vendor's own page before you book.
Practice Quizzes
Test your knowledge with standard 20-question practice sets.
Quiz 1
Quiz 2
Quiz 3
Quiz 4
Quiz 5
Quiz 6
Quiz 7
Quiz 8
Quiz 9
Quiz 10
Quiz 11
Quiz 12
Quiz 13
Quiz 14
Quiz 15
Browse by Domain
Study specific topics at your own pace.
Domain 1: Data Lakehouse Fundamentals · 67 questions
- Which characteristic most clearly distinguishes a data lakehouse from a traditional data warehouse?
- What capability does a data lakehouse provide that a traditional data lake typically lacks?
- In a data lakehouse architecture; what does separating storage from compute primarily enable?
- Which feature of Apache Iceberg enables querying historical versions of a table without duplicating data?
- How does Apache Iceberg provide ACID transaction support on object storage?
- What does schema evolution in Apache Iceberg allow you to do safely?
- Which statement best describes a key differentiator of Delta Lake compared to plain Parquet files on object storage?
- Apache Hudi is particularly well-suited for which data ingestion pattern?
- A team needs to query their data lake tables from multiple query engines including Presto; Spark; and Trino. Which open table format provides the broadest multi-engine support?
- Why is Apache Parquet the predominant file format for analytical workloads in data lakehouses?
- In which scenario might Apache ORC be preferred over Apache Parquet?
- For which use case is Apache Avro most commonly chosen over Parquet?
- What is the primary design goal of the Presto distributed SQL query engine?
- What role does Apache Spark most commonly play in a data lakehouse architecture?
- What is the primary function of the Hive Metastore in a data lakehouse?
- What role does MinIO play in a data lakehouse architecture?
- In the medallion architecture; what type of data is stored in the Bronze layer?
- What transformation occurs when data moves from the Bronze layer to the Silver layer in the medallion architecture?
- What characterizes data in the Gold layer of the medallion architecture?
- What is the primary purpose of a data catalog in a lakehouse environment?
- Why is data lineage tracking important in a data lakehouse?
- Which approach best implements column-level security in a data lakehouse?
- What does partition evolution in Apache Iceberg allow without breaking existing queries?
- What is the purpose of expiring snapshots in an Apache Iceberg table?
- Which statement accurately compares transaction models of Apache Iceberg and Delta Lake?
- How does a data lakehouse typically reduce total cost of ownership compared to a traditional data warehouse?
- Why is file compaction important in a data lakehouse using Apache Iceberg?
- How do column-level min/max statistics in Parquet files help query engines?
- In a data lakehouse; which component ensures that multiple query engines see a consistent view of table schemas and file locations?
- Which property of ACID transactions in a data lakehouse prevents a query from reading a partially written table?
- Which limitation of a traditional data lake is directly addressed by the data lakehouse architecture?
- What is the advantage of Apache Iceberg's hidden partitioning compared to Hive-style partitioning?
- A team migrating from a NAS-based data platform assumes they can keep their existing pattern of appending to files in place and renaming directories to reorganise data. Why does this assumption fail on object storage?
- An organisation runs a proprietary warehouse and is evaluating a lakehouse. Leadership asks what they gain architecturally by moving to open table formats on object storage. What is the strongest answer?
- A team writing directly to object storage relies on file naming - a final suffix - to signal that a batch is complete. What does an open table format provide instead?
- A lakehouse holds seven years of transaction history, of which only the last quarter is queried regularly. How should the data be placed?
- An architect asks why watsonx.data uses object storage as its primary storage layer rather than a high-performance shared filesystem. What is the strongest justification?
- A team stores its data as raw Parquet files in a bucket with no table metadata, and queries them by listing paths. What capability do they lose compared with using an open table format?
- A source system adds a new column and the downstream team needs it in the lakehouse table without rebuilding history. Which table-format capability addresses this?
- Why is keeping all historical data on the fastest available storage tier a poor default?
- A developer proposes encoding the database password into the object key prefix so that ingestion scripts can read it back at runtime without a separate configuration store. How should this be handled?
- A proposal creates a separate data mart for each query engine so that every engine has data laid out optimally for it. What is the objection?
- What problem arises if each query engine is allowed to rewrite the underlying files of a shared table independently?
- A cost-reduction exercise moves the tables underpinning daily operational dashboards to cold archival storage. What is the likely outcome?
- A stakeholder objects that object storage cannot be used for a SQL platform because SQL requires a database. What is the correct response?
- Which layering correctly describes a data lakehouse?
- A team proposes disabling metadata tracking on their tables to reduce write overhead. What do they lose?
- Why is choosing storage tiers based on file extension unsound?
- A design places lakehouse data on object storage and states that access will be controlled entirely through bucket permissions granted to each analyst. What is the flaw?
- A customer asks whether adopting a lakehouse means abandoning SQL and BI tooling in favour of a file-based workflow. What is the correct response?
- Which set of properties is the reason a lakehouse uses an open table format rather than plain files on object storage?
- Which requirement most directly forces data to be retained even though it is almost never queried?
- Which combination correctly describes how lakehouse data on object storage is made usable and safe?
- Why is a catalog necessary in a lakehouse when the data files themselves already contain schema information?
- While a long analytical query is running, a pipeline commits new rows to the same table. What does the table format guarantee for the running query?
- Which set of factors should drive storage tier decisions in a lakehouse?
- A team is deciding how to organise objects within a lakehouse bucket. Which consideration is most relevant to query performance?
- A team asks whether it is acceptable to keep some data in the lakehouse and continue running an existing warehouse for other workloads. How should this be assessed?
- What is the practical consequence of relying on a naming convention such as a date suffix instead of table-format partitioning and metadata?
- When older partitions of a table are moved to a lower-cost tier, what happens to queries that reference them?
- During a review, someone notes that object storage offers eleven nines of durability and concludes that no backup or retention strategy is needed for lakehouse tables. Is this reasoning sound?
- What does storing lakehouse data in an open table format most directly protect an organisation against?
- A batch load fails halfway through writing to a table managed by an open table format. What do readers see?
- Which statement about storage tiering in a lakehouse is correct?
- Which statement best describes the role of object storage in a watsonx.data deployment?
- Which combination best describes the lakehouse approach to serving multiple analytical workloads?
- Which statement about table formats in a lakehouse is correct?
Domain 2: watsonx.data Fundamentals · 64 questions
- What is the core architectural principle of IBM watsonx.data?
- What is the primary function of Infrastructure Manager in watsonx.data?
- In watsonx.data; when should you choose Spark over Presto for a workload?
- Which statement about Presto in IBM watsonx.data is correct?
- What is the role of the IBM Hive Metastore built into watsonx.data?
- When would you connect an external Hive Metastore to watsonx.data instead of using the built-in one?
- What is IBM Cloud Object Storage (COS) used for in a watsonx.data deployment?
- Why is watsonx.data compatible with AWS S3 storage?
- Through which watsonx.data component would you register a new object storage bucket for use as a lakehouse data store?
- How are Apache Iceberg tables typically created and managed in watsonx.data?
- What does the data catalog in watsonx.data provide to end users?
- How does IBM Cloud Pak for Data integrate with watsonx.data?
- What capability in watsonx.data allows different types of SQL queries to be automatically directed to the most appropriate engine?
- What key benefit does watsonx.data's shared metadata layer provide when multiple engines query the same table?
- On which platforms can IBM watsonx.data be deployed?
- Before a Presto engine in watsonx.data can query a table; what must be done first?
- Which data formats does watsonx.data natively support for data stored in object storage?
- How does IBM Knowledge Catalog complement watsonx.data?
- What is the relationship between IBM watsonx.data and IBM watsonx.ai?
- What happens to data in watsonx.data when a Presto or Spark engine is paused?
- Which catalog types can be registered in IBM watsonx.data?
- What mechanism does Presto use in watsonx.data to query different data sources like Db2; PostgreSQL; and object storage?
- When you run CREATE SCHEMA in watsonx.data's Presto engine; where is the schema definition stored?
- Which UI section in IBM watsonx.data would you use to browse tables and preview data?
- How does a Spark engine in watsonx.data access tables managed by the IBM Hive Metastore?
- How does IBM watsonx.data's pricing model differ from traditional data warehouse pricing?
- Which open specification does IBM watsonx.data use to enable interoperability of Iceberg tables with external engines?
- A watsonx.data administrator wants to add a second Presto engine dedicated to ETL workloads. What is the correct tool to use?
- After registering a new object storage bucket in watsonx.data; what additional step is required before a Presto engine can query tables stored in that bucket?
- An architect is describing the watsonx.data architecture to a new team. Which statement correctly characterises the relationship between the storage layer and the query engines?
- 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?
- A finance team asks to control who can read a sensitive table in the lakehouse. Where should that control be applied?
- An organisation runs both interactive BI queries and long-running batch transformations against the same lakehouse tables. What is the recommended design?
- A team lists the components involved when an analyst runs a query in watsonx.data. Which sequence reflects how the platform actually satisfies the request?
- A pilot ran on a single-node local install and worked well. The team proposes the same topology for production, serving several hundred analysts. What should the review raise?
- Why is it a poor practice for analysts to manage access by copying data into CSV extracts they share among themselves?
- What is the main drawback of running every workload on a single engine regardless of fit?
- A team proposes managing table permissions inside their BI tool rather than in watsonx.data, arguing that all reporting goes through that tool anyway. Why is this a weak design?
- A deployment plan for watsonx.data covers sizing, storage and engine topology but does not mention how users will authenticate or how the platform reaches existing systems on the corporate network. Why does this matter?
- Which capability lets a governance team answer the question "where did this table's data come from and what transformed it?"
- A team proposes giving each engine its own private copy of the data so engines never interfere. What is wrong with this?
- During a capacity review, a team asks whether adding a second query engine to watsonx.data will require duplicating the data those queries read. What is the correct answer?
- Which factor should most directly drive the choice between deploying watsonx.data on-premises, in the cloud, or as a hybrid?
- A team proposes dropping formal schema definitions so their tables can "stay flexible" as requirements change. What is the main problem with this?
- When a user switches from one engine to another to run the same query, what happens to the governance controls on the data?
- A stakeholder asks what distinguishes watsonx.data from simply keeping Parquet files in a bucket and pointing a query tool at them. Which answer best captures the difference?
- An organisation with substantial existing on-premises data infrastructure wants to adopt watsonx.data without decommissioning those systems. Which characteristic of the platform most supports this?
- An organisation governs only the dashboards its executives see, leaving the underlying tables uncontrolled. What risk does this create?
- Which factor should primarily drive the choice of engine for a given workload?
- A design document for a new watsonx.data deployment lists buckets, catalogs and engines, together with how they will be associated, but says nothing about who may access which tables. What is missing?
- A customer's compliance team requires that a specific dataset never leave a designated jurisdiction, while analysts in another region need to run reports that include aggregates from it. Which design satisfies both?
- A proof of concept is being promoted to production. Which governance work is required before data is opened to a wider audience?
- Interactive dashboard queries have become slow since a nightly transformation job was moved onto the same engine. What is the appropriate remedy?
- Which description best fits the role of the catalog in watsonx.data?
- A team is choosing between a managed cloud deployment and a self-operated installation. Which consideration most favours the managed option?
- What is the role of metadata in keeping lakehouse data trustworthy?
- What is the architectural benefit of supporting multiple query engines over one shared set of governed data?
- 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?
- After deploying watsonx.data, analysts can sign in but every one of them sees only an empty catalog list, while the administrator sees all catalogs. What is the most likely cause?
- An auditor asks who has been able to read a regulated table over the past quarter. Which combination answers the question?
- Which statement about engine selection in watsonx.data is correct?
- In watsonx.data, which two components must both be correct before a user can successfully read rows from a specific table?
- Which statement best reflects how deployment choices should be made for watsonx.data?
- Which statement best summarises how watsonx.data keeps lakehouse data trustworthy?
Domain 3: Operation · 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?
Domain 4: Data Integration · 55 questions
- Which method would be most appropriate for ingesting a large historical dataset from an on-premises relational database into watsonx.data?
- What does data virtualization in watsonx.data enable that traditional ETL does not?
- To query a PostgreSQL database from Presto in watsonx.data without moving data; what must be configured?
- Which external databases can be connected to IBM watsonx.data for data virtualization through JDBC connectors?
- How does IBM DataStage integrate with watsonx.data for data pipeline workflows?
- How would you ingest real-time event streams from Apache Kafka into watsonx.data?
- What PySpark API would you use to write a transformed DataFrame as an Iceberg table in watsonx.data?
- When ingesting JSON files with unknown structure into watsonx.data using Spark; what does schema inference do?
- When connecting an external PostgreSQL database to watsonx.data; what determines how PostgreSQL data types are mapped to Presto types?
- When creating an Iceberg table in watsonx.data to store daily transaction data; what partitioning strategy would most improve query performance for date-range queries?
- What is the primary use case for IBM Data Replication in the context of watsonx.data?
- When running a federated query that joins a large Iceberg table in watsonx.data with an external PostgreSQL table; what technique improves performance?
- After a streaming Spark job writes thousands of small Parquet files to an Iceberg table in watsonx.data; what operation should be run periodically?
- When configuring a JDBC connection to an external database in watsonx.data; why is setting appropriate connection pool limits important?
- When ingesting data into watsonx.data for analytics; which target file format is recommended for new tables to maximize query performance?
- What Spark code pattern is used to read data from an external JDBC database into a DataFrame for ingestion into watsonx.data?
- What is an advantage of using watermark-based incremental loading over full table refreshes when ingesting from a source database into watsonx.data?
- Which Spark Structured Streaming write mode would you use to continuously append new Kafka events to an Iceberg table?
- For a use case where a data scientist needs to run occasional ad-hoc queries joining watsonx.data tables with a live IBM Db2 operational database; which integration approach is most appropriate?
- A Presto query filters on WHERE eventdate = '2025-01-15' on an Iceberg table partitioned by eventdate. What performance optimization occurs?
- A reporting team needs to join lakehouse order tables against a customer table that lives in an operational PostgreSQL database. The customer table changes constantly and the join runs a few times a day. What is the appropriate approach in watsonx.data?
- An analyst has a notebook that cleans and reshapes raw ingest data, and three teams now depend on running it themselves before reporting. What should change?
- An organisation needs to bring data from a transactional database, a SaaS application and an existing data warehouse into its lakehouse. What is the correct approach?
- A new ingestion pipeline is being designed for a source that feeds regulatory reporting. Which requirement should the design satisfy?
- A team federates a legacy reporting database that takes about ninety seconds to answer a typical aggregate query. They are surprised the federated version is no faster. Why?
- A finance team maintains a monthly revenue restatement by exporting a lakehouse table to a spreadsheet, applying adjustments by hand, and uploading the result. What is the principal risk?
- A source system is queried infrequently, is subject to strict residency rules, and its owners will not permit copies. Which integration pattern fits?
- What is the consequence of loading data without validating its structure?
- A team argues that federating a source is a way to give analysts access to data that governance would otherwise restrict, because the data is never stored in the lakehouse. How should this be assessed?
- A transformation job completes with no SQL errors, but downstream users report that a revenue column is now null for most rows. What does this indicate about the pipeline's design?
- A dashboard must reflect operational data within a few seconds of it changing. What does this requirement imply for the integration design?
- Why should metadata be captured as part of ingestion rather than added once the pipeline reaches production?
- An architect proposes copying every federated source into the lakehouse first, then federating those copies, to guarantee consistent performance. What is wrong with this plan?
- What most clearly distinguishes a controlled transformation pipeline from ad hoc transformation work?
- Why is federation an unsuitable choice for a workload that repeatedly runs heavy aggregations over a large source table?
- A team proposes ingesting only the aggregated totals their current dashboard shows, rather than the underlying detail. What risk does this create?
- Which requirement most strongly indicates that federation is the right choice rather than ingestion?
- A pipeline produces a table that several reporting teams consume. What should accompany the table so consumers can use it correctly?
- A newly configured connector authenticates successfully but returns no rows for a table the source team confirms has data. What should be checked first?
- A daily load occasionally contains records with an unexpected extra field. Which handling approach best preserves both data quality and continuity?
- A federated query against a remote warehouse is slow, and monitoring shows a very large volume of data being read across the network for a query whose result is a few hundred rows. What should be examined first?
- A team plans to run transformation logic directly against production tables, overwriting them in place with each run. What is the main objection?
- What is the primary factor in deciding between ingesting a source into the lakehouse and federating queries to it?
- Which combination describes a production-ready ingestion pattern?
- A team plans to query three systems - an operational database, an existing warehouse, and lakehouse tables - in a single report. What does federation in watsonx.data provide here?
- Two teams report different totals for the same metric. Investigation shows each maintains its own transformation deriving the metric from the same raw tables. What is the appropriate fix?
- A team wants to replace their brittle collection of hand-run export scripts with a supportable integration into watsonx.data. What should they adopt?
- Data quality problems in a governed table are consistently discovered by business users reading reports. What does this indicate about the ingestion design?
- After six months, a federated connection to a partner's reporting database is generating enough load that the partner asks the team to reduce it. The queries are dashboard refreshes over largely historical data. What is the right change?
- A pipeline's source system adds two columns and renames a third. The pipeline continues to run successfully but the renamed column's data disappears from the output. What practice would have caught this before consumers noticed?
- Which risk is introduced by transferring source data as manually prepared files rather than through a supported connector?
- Which statement about ingestion into a governed lakehouse is correct?
- Which statement about federation in watsonx.data is accurate?
- Why is testing a transformation important even when the SQL executes without error against production data?
- Which statement about connecting disparate sources to watsonx.data is correct?
Domain 5: Consumption · 56 questions
- Which interface provides an interactive SQL editor for running Presto queries in IBM watsonx.data?
- How does IBM Cognos Analytics consume data from watsonx.data?
- How would a data scientist connect a Jupyter Notebook to watsonx.data to query Iceberg tables?
- What does watsonx.data's REST API enable for application developers?
- A BI developer wants to connect a third-party SQL client (DBeaver) to watsonx.data. What is the recommended approach?
- How does the cost-based optimizer (CBO) in Presto improve query performance in watsonx.data?
- A data analyst queries a large sales table partitioned by region and year. Which query pattern enables partition pruning?
- How would IBM SPSS Modeler access data stored in watsonx.data for predictive modeling?
- What benefit does result set caching provide in watsonx.data query workloads?
- What is the advantage of using materialized views in watsonx.data for frequently executed aggregate queries?
- A business user in the Finance department should only see finance-related tables in watsonx.data. How is this implemented?
- A data analyst has run a complex aggregation query in watsonx.data and needs to share the results with a stakeholder who does not have watsonx.data access. What is the appropriate approach?
- What additional information does EXPLAIN ANALYZE provide compared to EXPLAIN in Presto?
- How can a data analyst writing Presto queries in watsonx.data reduce the amount of data scanned from Parquet files?
- In watsonx.data; a BI analyst role requires read-only access to Gold-layer tables for reporting. Which privilege assignment is correct?
- What Python library would a developer use to submit SQL queries to watsonx.data Presto programmatically?
- Which statement about integrating watsonx.data with downstream analytics tools is correct?
- What does the Query History feature in watsonx.data provide to users?
- A data analyst needs to compare current sales figures with sales as they appeared 30 days ago. Which Iceberg feature enables this comparison?
- An executive dashboard powered by watsonx.data Presto shows slow load times due to expensive aggregate queries. What is the most effective architectural solution?
- A business intelligence team needs to build dashboards over curated Iceberg tables held in watsonx.data. They ask the platform team how their BI tool should reach the data. What is the appropriate answer?
- An analyst has been asked to find out why returns rose last quarter. There is no defined target variable and no hypothesis yet. Which analytic approach fits?
- An application team needs their service to read governed lakehouse tables as part of a nightly process. What is the appropriate integration approach?
- A user's query against a lakehouse table returns a permission error. What is the correct interpretation?
- An analyst has been granted access to a governed catalog in watsonx.data and wants to explore its tables and run ad hoc SQL without installing any client software. What should they use?
- A team wants to forecast next month's support ticket volume per product line. They have three years of daily history. Which approach is appropriate?
- A BI platform must connect to watsonx.data to run its scheduled reports. Which interface is intended for this?
- A query fails immediately with a message pointing at a specific position in the statement. Which cause should be investigated first?
- A department has been emailing spreadsheet extracts of lakehouse tables to its stakeholders because it finds that easier than granting platform access. A governance review flags the practice. What is the core problem?
- A dashboard applies a filter for high-value customers in a specific region and shows the resulting revenue. A manager describes this as the team's predictive model. Why is that mischaracterisation a problem?
- A developer's integration works when they run it under their own account but must now run unattended in production. What should change?
- A federated query fails while queries against native lakehouse tables succeed. What is the most likely cause?
- Two teams report different totals for the same monthly revenue figure. Investigation shows one team queries the governed lakehouse table through a Presto engine and the other maintains its own copy loaded into a departmental database. What is the sustainable fix?
- A team wants to predict which customers will churn but has never recorded whether a customer churned. What must happen before a predictive model can be built?
- Why is scraping the watsonx.data web interface an unsuitable integration strategy for an application?
- Why is increasing storage capacity before reading a query's error message an unsound response to a failure?
- An application team requests a connection to watsonx.data for a reporting tool. The platform team must supply the connection details. Which set is required for a JDBC connection to a Presto engine?
- Which statement correctly distinguishes exploratory from predictive analytics?
- An application requires programmatic access to watsonx.data and the team asks how governance applies to it. What is the correct answer?
- A query succeeds on one engine and fails on another with a function-related error. What should be examined?
- A data science team wants to read a large governed lakehouse table into notebooks for feature engineering. They ask whether they should copy the table to a local disk first for speed. What guidance fits the watsonx.data consumption model?
- A team plans to skip exploratory work and begin modelling immediately, arguing that the algorithm will find whatever matters. What is the practical risk?
- An application's queries against watsonx.data begin failing with permission errors after a governance review, though the application code has not changed. What is the most likely explanation?
- Which sequence best describes a systematic approach to a failed query?
- A dashboard built on a watsonx.data table returns no rows for one group of users while working correctly for another, and both groups run the identical query against the same engine. What is the most likely explanation?
- A manager asks whether predictive analytics can tell them which of two marketing designs to run next quarter, given that no such campaign has been run before. What is the appropriate advice?
- Which practice best supports maintainable programmatic access to watsonx.data over time?
- Why is it wrong to treat every failed query as an indication that data has been lost?
- An organization wants business users to explore lakehouse data without writing SQL, while keeping every access subject to the same governance as engineered queries. Which approach is consistent with the platform's consumption model?
- In a governed lakehouse, what is a practical advantage of doing both exploratory and predictive work against the platform's own tables rather than on extracted copies?
- A team wants an application to trigger administrative operations, such as creating a catalog association, as part of an automated deployment. What is the appropriate mechanism?
- A query worked yesterday and now returns an object-not-found error, with no infrastructure changes. What is the most likely cause?
- A platform team is defining how downstream consumers should reach curated lakehouse tables. Which principle should the standard be built on?
- A team has an exploratory finding that two product categories show markedly different return rates. What is the appropriate next step if they want to act on it operationally at scale?
- Which statement about programmatic access to watsonx.data is correct?
- Which statement best summarises query troubleshooting in watsonx.data?
These questions are original practice material and are NOT actual exam questions or brain-dump content. All vendor marks are trademarks of their respective owners. This site is not affiliated with, endorsed by, or sponsored by the exam vendor.