A DMS task continuously copies RDS changes to S3.
Large LOB columns containing image metadata must arrive without truncation.
Which LOB setting is most appropriate?
Use DMS full LOB mode and plan for the resulting transfer volume and task performance.
Detailed explanation
Full LOB mode transfers the entire value, but it increases data volume and processing time.
Full LOB mode transfers the entire value, but it increases data volume and processing time.
Values larger than the limit can be truncated, so the copy is not complete.
Values larger than the limit can be truncated, so the copy is not complete.
Object retention does not change which LOB bytes DMS transfers.
Object retention does not change which LOB bytes DMS transfers.
Ignoring LOB values excludes data and cannot satisfy the complete-replication requirement.
Ignoring LOB values excludes data and cannot satisfy the complete-replication requirement.
Check official documentation
Compare the following points with the official documentation.
AWS DMSのLOBモード、完全LOB、限定LOBの公式説明を確認する。
What to confirm
完全性と転送コスト・性能のトレードオフを説明できる。
Key points
- AWS DMS
- LOB
- Full LOB mode
- Transfer volume
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Completeness trade-off
Ignoring or truncating LOBs reduces work but changes the data semantics.
Performance planning
LOB size and task parallelism affect network, memory, and target-write performance.