Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is planning a live migration from an on-premises Microsoft SQL Server environment to Cloud SQL for PostgreSQL using Google Cloud Database Migration Service (DMS) with continuous Change Data Capture (CDC).
During pre-production migration testing, the team encounters two critical issues on the destination database:
Which strategy should the cloud architect recommend to ensure data integrity and prevent migration job failures?
The max text repl size parameter in Microsoft SQL Server controls the maximum size (in bytes) of Large Object (LOB) data types (such as text, ntext, varchar(max), and image) that can be added to a replicated column in a single INSERT, UPDATE, or WRITETEXT statement. Modifying this setting allows larger LOB fields to pass through CDC.
The scenario specifically involved replication failures caused by Large Objects (varchar(max) or image data types) exceeding the default 65,536-byte CDC size threshold during source change capture.
Memory-optimized tables (In-Memory OLTP) and temporal tables (system-versioned tables) are specialized table architectures in relational database engines designed for high-throughput memory processing and historical data point-in-time tracking, respectively.
The objective was to design an on-premises database schema for real-time audit logging and high-speed in-memory transaction processing prior to considering cloud migration.
In Database Migration Service conversion workspaces, when a source table lacks an explicit primary key, DMS can automatically generate an md5_hash column based on all column values in each row to enable unique row identification and tracking during CDC replication.
md5_hash columns into the live production source database is unnecessary and disruptive, as DMS conversion workspaces handle key generation automatically only for tables lacking primary keys.md5_hash generation is an automated feature within the DMS conversion workspace for keyless tables, not a manual source modification technique.The primary problem was migrating tables that lacked primary keys, resulting in CDC replication failure or inability to track unique row updates.
During homogeneous and heterogeneous migrations using Database Migration Service (DMS), managing secondary database objects such as foreign keys and triggers on the target database is essential for smooth data replication. Disabling or dropping these constraints during the initial dump and continuous CDC replication ensures that dependencies and automated logic do not disrupt data movement.
REPLICATION role privilege) avoids these constraint validation errors.
REPLICATION attribute for the migration user.This approach directly targets the architectural mechanics of DMS, which streams table snapshots and log changes independently. By deferring foreign key validation and trigger execution until data transfer stabilizes, the migration pipeline completes reliably without data corruption.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated