During a refresh, which aspect of materialized views is replicated to the secondary database?

• A. Definitions and data
• B. Only definitions
• C. Only data
• D. Neither

Answer: (B)

When thinking about how materialized views behave in a replication or DR scenario, the important idea is that the saved, precomputed results are not moved around with every refresh. A materialized view is a cached result set built from a query, and keeping the secondary in sync focuses on the object’s definition rather than its cached data. The definition—essentially the SQL that creates the MV and its metadata—needs to exist on the secondary so the MV can be managed and refreshed there, but the actual data that the MV stores is tied to the primary location and is refreshed there. In practice, this means only the MV’s definition is replicated to the secondary; the materialized data itself is not transferred during the refresh process.