Materialized View orTemporary Tables in SQL — Learn free

Self-check

Questions 1–10 of 10

1. What is a temporary table in SQL?
Question 1A. A table that stores a refreshed query snapshot until explicitly droppedB. A table created within a database session and available only during the lifetime of that sessionC. A read-only copy of a production tableD. A view that dynamically fetches rows from base tablesE. A table stored in external cloud storage
2. What happens to a temporary table when the database session ends?
Question 2A. It is refreshed with the latest dataB. It is converted into a permanent tableC. It is automatically discarded, as if DROP TABLE had been runD. It is archived to external storageE. It becomes a materialised view
3. Which two characteristics distinguish temporary tables?
Question 3A. Encrypted and compressedB. Partitioned and indexedC. Replicated and versionedD. Session-specific and volatileE. Persistent and scheduled
4. What kind of data are temporary tables designed to store?
Question 4A. Long-term compliance archivesB. Top-rated product lists for a websiteC. Master reference dataD. Pre-aggregated reporting figuresE. Intermediate results, results of window functions for complex calculations and massive data manipulations
5. How does a materialised view differ from a temporary table in terms of persistence?
Question 5A. A materialised view is stored in the database until explicitly dropped, whereas a temporary table is discarded at session endB. A materialised view disappears at session end, whereas a temporary table persistsC. Both are discarded at the end of the sessionD. Both persist until the database is restartedE. A materialised view exists only in memory
6. How can a materialised view be refreshed?
Question 6A. Only automatically on every insertB. On a schedule or on a manual basisC. Only when the session restartsD. Only by dropping and recreating itE. It can never be refreshed
7. For which type of workload do materialised views significantly improve performance?
Question 7A. Write-heavy transactional insertsB. Schema migrationsC. Read-heavy operations, by precomputing and storing the query resultD. Session-specific personalisationE. Backup and restore jobs
8. In a data warehousing project, how are materialised views and temporary tables typically divided?
Question 8A. Materialised views hold raw source extracts; temporary tables hold final reportsB. Both are used only for backupsC. Temporary tables replace the ETL process entirelyD. Materialised views pre-aggregate data for reporting tools, while temporary tables handle intermediate manipulation during ETLE. Materialised views are used only in web applications
9. In a web application, which construct would store frequently accessed data such as top-rated products?
Question 9A. A temporary tableB. A session variableC. A window functionD. A cursorE. A materialised view
10. Which statement about temporary tables is NOT correct?
Question 10A. They remain in the database until explicitly dropped by a commandB. They are visible only within the session that created themC. They help avoid repeated calculations or data retrieval operationsD. They are useful for holding data without affecting the main database tablesE. They are supported by most modern RDBMS such as PostgreSQL, MySQL, Oracle and SQL Server