1Z0-060 · Question #223
Which three statements are true about the use of the In-Database Archiving and Temporal Validity features of Oracle Database 12c? (Choose three.)
The correct answer is A. Both Transaction Time and Temporal Validity time dimensions may be used as filters in the same D. Temporal Validity time is based on the times specified by the application. E. Inactive rows that have been archived are always invisible. Oracle 12c In-Database Archiving and Temporal Validity are distinct features with separate time dimension semantics and database-enforced visibility behaviors.
Question
Which three statements are true about the use of the In-Database Archiving and Temporal Validity features of Oracle Database 12c? (Choose three.)
Options
- ABoth Transaction Time and Temporal Validity time dimensions may be used as filters in the same
- BTemporal Validity spans the time between a row insert and a subsequent update or delete for the
- CIn-Database Archiving is based on application-managed setting of the life-cycle state.
- DTemporal Validity time is based on the times specified by the application.
- EInactive rows that have been archived are always invisible.
How the community answered
(28 responses)- A82% (23)
- B11% (3)
- C7% (2)
Why each option
Oracle 12c In-Database Archiving and Temporal Validity are distinct features with separate time dimension semantics and database-enforced visibility behaviors.
Oracle 12c allows queries to filter rows using both Transaction Time (system-managed) and Valid Time (application-defined Temporal Validity) dimensions as predicates simultaneously in the same query using AS OF PERIOD FOR and VERSIONS PERIOD FOR clauses.
The period from row insert to a subsequent update or delete describes Transaction Time, which is system-managed; Temporal Validity is an application-specified valid-time period that is independent of when DML operations occur.
In-Database Archiving visibility is enforced by the database through the ROW ARCHIVAL VISIBILITY session parameter and the ORA_ARCHIVE_STATE column, making it a database-controlled feature rather than a purely application-managed lifecycle mechanism.
Temporal Validity (Valid Time) records a period that is explicitly supplied by the application through designated start and end timestamp columns, making the valid-time range entirely application-controlled rather than derived from DML event timestamps.
By default, rows marked as archived via In-Database Archiving (ORA_ARCHIVE_STATE set to a non-zero value) are always invisible to standard queries unless the session explicitly sets ROW ARCHIVAL VISIBILITY = ALL.
Concept tested: Oracle 12c Temporal Validity and In-Database Archiving time dimensions
Source: https://docs.oracle.com/en/database/oracle/oracle-database/12.2/adfns/temporal_validity_in-database_archiving.html
Topics
Community Discussion
No community discussion yet for this question.