After connecting to Lakehouse1's SQL endpoint, what can you do?

Connecting to Lakehouse1's SQL endpoint allows you to perform various operations on the data stored within that system. The reason reading Table3 is the correct choice relates to the common functionality of SQL endpoints in data lakehouses. Typically, SQL endpoints are primarily designed for querying and reading data rather than for modifying or updating it.

In this context, reading from tables is generally supported, and you can leverage SQL commands to retrieve data efficiently. It’s likely that Table3 is structured in a way that allows for straightforward data access, making it readily available for querying through the SQL endpoint.

The other options involve updating tables, which can introduce complexities related to permissions, data integrity, and locking mechanisms. Often, SQL endpoints may restrict write permissions to prevent accidental data loss or corruption. Thus, while reading from Table3 is a straightforward and typically supported operation via SQL endpoints, updating tables would usually require additional privileges or might not be allowed at all.