1Z0-909 Sample Questions & Answers

This statement is true. The JSON_TABLE() function is a powerful feature in MySQL 8.0 that allows you to extract data from a JSON document and present it as a relational table with specified columns and data types. This resulting virtual table can be used in the FROM clause of a query and joined with other physical or virtual tables.

This is the optimal solution. Using the MySQL Document Store and XDevAPI directly addresses all requirements. It maintains schema flexibility (NoSQL model), provides high-performance filtering by allowing indexes on nested JSON fields, and offers a modern, fluent API (XDevAPI) for microservice development. While adding generated columns (Option B) solves the performance issue, it doesn't address the need for a modern API and ties the schema more tightly to relational concepts. The other options are significantly less performant and scalable.

MySQL Connector/Python is the official Oracle driver for Python. It is a pure Python implementation and provides support for both the classic MySQL protocol and the new X Protocol, which is required for interacting with the MySQL Document Store via the XDevAPI.

The WITH CHECK OPTION clause is used to enforce the conditions in the view's WHERE clause for any INSERT or UPDATE statements performed through the view. If the view is defined with WHERE total_order_value >= 0, adding WITH CHECK OPTION will cause any modification that violates this condition to fail. However, a view with aggregation (SUM) is not updatable, so this option would only work on an updatable view. In a non-updatable view scenario, a trigger would be the only way.

Processing the import in smaller batches reduces the size of each individual transaction. This prevents the UNDO log from growing excessively and reduces memory consumption per transaction.

Committing after each smaller batch finalizes that part of the work, allowing MySQL to reclaim the UNDO log space and other resources used by that transaction. This combination of batching and committing is a standard pattern for large data loads.

The question mark (?) is the standard positional placeholder used in prepared statements with MySQL connectors like Connector/J for Java. The values are then bound to these placeholders in the order they appear.

ST_Distance_Sphere() is the appropriate function for calculating the distance between two points on a spherical model of the Earth, which is ideal for geographic coordinates. It returns the distance in meters, so the result can be compared to 10,000 (10km) to find all stores within the radius. ST_Distance calculates Cartesian distance, which is incorrect for lat/lon. ST_Contains and ST_Within are for checking if one geometry is inside another, not for radius searches.

A BEFORE UPDATE trigger is the correct choice. It fires before the data modification occurs, allowing you to inspect the incoming new value (NEW.price) and compare it to the cost (NEW.cost). If the condition is not met, you can use SIGNAL to raise an error and prevent the update from happening. An AFTER UPDATE trigger would be too late, as the invalid data would have already been written.

To view a system variable for the current session, you can use SELECT @@SESSION.variable_name; or the alias SELECT @@variable_name;. Using SHOW SESSION VARIABLES LIKE 'sql_mode'; would also work. The GLOBAL keyword is used to view or set the global value that applies to new connections, not the current one.

In MySQL Shell's JavaScript and Python modes, the global db object represents the current schema (database). You access collections through this object, for example: db.myCollection.find('name = "test"'). The session object represents the connection itself, and shell provides access to shell-specific APIs.