Explanation/Reference:
A: Fast Incremental backups is possible with Block change tracking, which is initially introduced from version 10.2 onwards, by this tool it's very useful to reduce the RMAN incremental backup duration.
If the changes are something around 20% then in this situation BCT helps a lot.
C: Exadata Storage Server offload capability combined with RMAN block change tracking will efficiently perform large I/Os at the storage-tier level, returning only individual changed blocks for incremental backups and increasing the backup performance of the system.
Note: Level 1 backup: A level 1 backup includes only those blocks that have been changed since the
"parent" backup was taken. Remember a parent backup may be either a level 0 or a level 1 backup.
Block change tracking allows indeed the highest benefit for databases where the changes are not so high, Level 0 backup: A level 0 incremental backup is physically identical to a full backup and it includes every data block in the file except empty blocks. The only difference is that the level 0 backup is recorded as an incremental backup in the RMAN repository, so it can be used as the parent for a level 1 backup.
References: http://www.dba-oracle.com/t_rman_backup_types.htm
http://www.oracle.com/technetwork/database/availability/maa-tech-wp-sundbm-backup-11202-183503.pdf
https://www.toadworld.com/platforms/oracle/w/wiki/11124.fast-incremental-backups-active-data-guard

Explanation/Reference:
Explanation:
D: With Exadata storage, database operations are handled much more efficiently. Queries that perform table scans can be processed within Exadata storage with only the required subset of data returned to the database server. Row filtering, column filtering and some join processing (among other functions) are performed within the Exadata storage cells. When this takes place only the relevant and required data is returned to the database server.
E: With Smart Scan processing, row filtering, column filtering, some join processing, and other functions are performed in the Exadata cells.
References: http://www.centroid.com/blog/exadata-smart-scan-processing

Explanation/Reference:
Step 1: 1. Create a new 12.1.0.2 Exadata -based database.
Step 2: 2. Export the source system metadata using transportable Tablespace (TTS).
Step 3: 3. Transfer the files to the Database Machine and use the RMAN CONVERT command to change them to the little endian format.
Step 4: 4. Import the metadata into the target database.
This method is often chosen when migrating between platforms with different endian formats, or in cases where physical re-organization is not necessary.
The transportable tablespace method is generally mu
References: https://docs.oracle.com/en/cloud/paas/exadata-cloud/csexa/mig-transportable- tablespace.html

Explanation/Reference:
AD: To schedule exachk, we can create a cron job or we can create a job in Enterprise Manager..
To add an Enterprise Manager job to execute Exachk on a periodic basis. Execute the following steps.
First go to
Enterprise, Job, Library. Then create a new OS Command job
E: exachk options include AUTORUN_SCHEDULE, which schedules recurring health checks using the AUTORUN_SCHEDULE daemon option.
References:
http://www.oracle.com/technetwork/database/availability/exadata-health-resource-usage-2021227.pdf
http://docs.oracle.com/cd/E68491_01/OEXUG/automated-daemon-mode-operation.htm Best practices: Execute the latest version of the exachk utility before and after planned maintenance activities and at least once every month