TRUNCATE does not generate much redo while still deleting all of the data in the table.
For example:
SQL> TRUNCATE table owner.tablename;
has the same effect as:
SQL> DELETE from owner.tablename;
SQL> COMMIT;
DELETE will generate large redo if the table is large - this is a DML transaction.
TRUNCATE will generate very little redo - this is a DDL transaction.
This is subject to TRUNCATE being configured for replication.
If TRUNCATE is not configured for replication then the Target table will need to be manually truncated if you wish to keep the Source and Target tables in sync.
