Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization is planning a homogeneous migration of an on-premises SQL Server database to Cloud SQL for SQL Server during an approved 48-hour weekend maintenance window. Your team must satisfy the following technical requirements and constraints:
Which migration procedure should you implement to meet all requirements?
.bak backup file to a Cloud Storage bucket, and restore the file into Cloud SQL to migrate both the database objects and instance-level logins.A single-file native backup writes the entire SQL Server database—including all tables, indexes, stored procedures, and transaction state—into one monolithic .bak archive. While straightforward for smaller workloads, it relies on a single object in Cloud Storage and assumes database-level backups carry instance-wide security principals.
.bak file to Cloud Storage fails, and SQL Server best practices require striped backups once a database exceeds 5 TB..bak database backups only contain database-scoped objects and users. SQL Server logins, permissions, and server roles reside at the instance level (in system databases such as master) and are not restored automatically with a user database backup.The database backup size were 5 TB or less (making a single .bak file valid for Cloud Storage) and you also ran a separate PowerShell or DBAtools script to migrate instance-level logins, permissions, and server roles.
A common misconception is that a full database backup captures everything on a SQL Server instance. In practice, instance-level metadata must always be transferred alongside database backups during offline migrations.
.bak files in a Cloud Storage bucket, restore the backup into Cloud SQL, and transfer logins and server roles separately using PowerShell or DBAtools.A striped backup splits a single database backup operation across multiple .bak files simultaneously instead of writing everything into one monolithic file. Combined with Cloud Storage as an intermediate staging layer, this native backup-and-restore approach allows database administrators to perform large, scheduled maintenance migrations without maintaining a continuous replication link between source and target environments.
.bak files only capture database-level objects and data, instance-level logins, permissions, and server roles are exported and reapplied separately using PowerShell scripts or DBAtools.For a static or writable-halted 8 TB homogeneous SQL Server migration with an approved 48-hour outage window, native striped backups staged in Cloud Storage offer the fastest, lowest-complexity bulk transfer path while respecting platform file-size ceilings and preserving instance-level security metadata.
.bak files of 500 GB each for parallel throughput, upload them to Cloud Storage, and restore all 16 files simultaneously into Cloud SQL while transferring logins via DBAtools.This approach correctly recognizes the need to quiesce writes, divide the 8 TB database into smaller segments under Cloud Storage's 5 TB object limit, and migrate instance-level logins separately with DBAtools. By splitting the backup into 16 files of 500 GB each, it aims to maximize parallel I/O throughput during backup and restoration.
.bak files simultaneously exceeds the supported limit and causes the restore operation to fail.The 8 TB striped backup were divided into 10 or fewer .bak files (for example, eight 1 TB files or ten 800 GB files) rather than 16 files, keeping each file under 5 TB and within the simultaneous restore limit.
Administrators often assume adding more stripes always improves performance. However, exceeding the 10-file boundary breaks compatibility with the restore pipeline, making stripe count planning critical for multi-terabyte migrations.
bcp utility alongside schema scripts, stage the files in a Cloud Storage bucket, and import them into Cloud SQL.Using the bcp utility with Generate and Publish Scripts Wizard extracts schema definitions into SQL scripts and table rows into flat files (such as CSV or JSON). Staged in Cloud Storage, these files can then be imported sequentially or in batches into a target Cloud SQL database.
.bak backup and restore, risking an overrun of the 48-hour maintenance window.bcp data exports do not automatically migrate instance-level SQL Server logins, permissions, and server roles.You needed to transform, filter, or refactor a smaller subset of tables during migration, quiesced writes on the source database beforehand, and ran separate scripts to migrate instance-level logins and server roles.
When performing a 1:1 homogeneous migration of a multi-terabyte database during an extended outage window, built-in binary backup and restore is both faster and more reliable than flat-file utilities.
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 Validated