Knowledge + Practice

CCNA Deployment and Migration Questions

75 of 341 questions · Page 1/5 · Deployment and Migration · Answers revealed

Practice these questions Domain overview All questions

1

MCQhard

A company is migrating a 10 TB Oracle Data Warehouse to Amazon Redshift. The source database runs on premises with limited bandwidth (100 Mbps). The migration must complete within 5 days. Which approach is most cost-effective and meets the timeline?

A.Use AWS DMS over the internet to migrate data.

B.Use AWS Snowball Edge to transfer the initial full load, then AWS DMS for ongoing changes.

C.Use AWS Schema Conversion Tool (SCT) to convert and then upload to S3.

D.Use AWS DMS with AWS Direct Connect at 1 Gbps.

AnswerB

Snowball is fast and cost-effective for large data transfer.

Why this answer

The 10 TB dataset over a 100 Mbps link would take approximately 10 days (10 TB * 8 / 100 Mbps / 86400 seconds/day) for a full load, exceeding the 5-day window. AWS Snowball Edge provides a physical, high-bandwidth transfer for the initial full load, bypassing network constraints, and AWS DMS then captures and applies ongoing changes (CDC) to keep the target in sync. This combination is the most cost-effective as it avoids expensive Direct Connect and meets the timeline.

Exam trap

The trap here is that candidates often overlook the bandwidth calculation and assume DMS over Direct Connect is always the fastest and most cost-effective, but the question explicitly asks for the most cost-effective solution that meets the timeline, and Snowball Edge avoids the high recurring costs of Direct Connect for a one-time migration.

How to eliminate wrong answers

Option A is wrong because AWS DMS over the internet at 100 Mbps would take over 10 days for the full 10 TB load, failing the 5-day requirement, and is not cost-effective due to potential data transfer costs and instability over the public internet. Option C is wrong because AWS Schema Conversion Tool (SCT) is used for schema conversion and can upload data to S3, but it does not handle ongoing replication (CDC) and relies on network transfer for the full load, which still faces the bandwidth bottleneck. Option D is wrong because while AWS DMS with AWS Direct Connect at 1 Gbps could theoretically transfer 10 TB in under 2 days, the cost of provisioning and maintaining a 1 Gbps Direct Connect connection for a one-time migration is significantly higher than using Snowball Edge, making it not the most cost-effective.

Practice this question →

2

MCQmedium

Refer to the exhibit. An IAM policy is attached to a user who will manage AWS DMS tasks. When the user tries to start a replication task, they receive an access denied error. What is the most likely cause?

A.The policy does not allow rds:DescribeDBInstances

B.The policy does not allow the dms:StartReplicationTask action

C.The policy is missing permissions to describe endpoints and connections

D.The policy does not allow dms:CreateReplicationTask

AnswerC

To start a replication task, DMS needs to describe endpoints and connections; these actions are missing from the policy.

Why this answer

The DMS API requires that a user have permissions to describe endpoints and connections before starting a replication task. Even if the policy grants dms:StartReplicationTask, the service internally calls dms:DescribeEndpoints and dms:DescribeConnections to validate the source and target endpoints. Without those describe permissions, the API call fails with an access denied error, even though the start action itself is allowed.

Exam trap

The trap here is that candidates assume the error is due to a missing start action (Option B) when the policy actually includes it, but they overlook that DMS requires additional describe permissions for endpoints and connections as a prerequisite to starting a task.

How to eliminate wrong answers

Option A is wrong because rds:DescribeDBInstances is not required to start a DMS replication task; DMS uses its own endpoints and connections, not direct RDS instance descriptions. Option B is wrong because the policy explicitly includes dms:StartReplicationTask (as shown in the exhibit), so the error is not due to a missing start action. Option D is wrong because dms:CreateReplicationTask is only needed to create a new task, not to start an existing one; the user is attempting to start an already created task.

Practice this question →

3

MCQhard

A company is migrating a 500 GB PostgreSQL database from on-premises to Amazon Aurora PostgreSQL. The migration must have a recovery point objective (RPO) of less than 5 minutes and a recovery time objective (RTO) of less than 30 minutes. Which migration strategy should the company use?

A.Create a read replica of the on-premises database and promote it.

B.Use AWS DMS with full load and ongoing replication.

C.Take a full backup using pg_basebackup and restore to Aurora.

D.Use pg_dump to export the database and import into Aurora.

AnswerB

Ongoing replication achieves low RPO.

Why this answer

AWS DMS with full load and ongoing replication is the correct strategy because it supports continuous change data capture (CDC) from the on-premises PostgreSQL source to Amazon Aurora PostgreSQL, enabling an RPO of less than 5 minutes. The full load phase migrates the initial 500 GB, and ongoing replication keeps the target synchronized with minimal lag, while Aurora’s automated failover and fast recovery help achieve an RTO under 30 minutes.

Exam trap

The trap here is that candidates often assume pg_basebackup or pg_dump can meet low RPO/RTO by combining with manual log shipping, but they overlook that these methods lack built-in continuous replication and automated failover, which are essential for the stated recovery objectives.

How to eliminate wrong answers

Option A is wrong because creating a read replica of the on-premises database and promoting it is not supported for cross-platform migration from on-premises to Aurora; PostgreSQL read replicas require a primary instance within the same environment or a compatible cloud service, and Aurora does not support direct replication from an external PostgreSQL instance. Option C is wrong because taking a full backup using pg_basebackup and restoring to Aurora provides only a point-in-time snapshot without ongoing replication, resulting in an RPO equal to the backup interval (often hours) and failing to meet the sub-5-minute requirement. Option D is wrong because using pg_dump to export and import into Aurora is a one-time logical dump that does not support continuous replication, leading to significant data loss between the dump and cutover, which violates the RPO requirement.

Practice this question →

4

MCQmedium

A company is migrating a 2 TB on-premises Oracle database to Amazon RDS for Oracle. The migration must have minimal downtime and support ongoing replication. Which AWS service should be used to accomplish this?

A.AWS Schema Conversion Tool (AWS SCT)

B.AWS DataSync

C.AWS Glue

D.AWS Database Migration Service (AWS DMS)

AnswerD

AWS DMS supports minimal-downtime migrations and ongoing replication.

Why this answer

AWS DMS is the correct choice because it supports homogeneous migrations (Oracle to Oracle) with minimal downtime through ongoing replication using change data capture (CDC). It can handle a 2 TB database by using a large enough replication instance and enabling task logging for validation, ensuring data consistency during the migration.

Exam trap

The trap here is that candidates might confuse AWS DMS with AWS SCT, assuming schema conversion is needed for an Oracle-to-Oracle migration, but DMS handles both schema and data migration natively for homogeneous migrations without requiring SCT.

How to eliminate wrong answers

Option A is wrong because AWS SCT is used for schema conversion when migrating between heterogeneous database engines (e.g., Oracle to Aurora PostgreSQL), not for ongoing replication or minimal-downtime migration within the same engine. Option B is wrong because AWS DataSync is designed for transferring large files over NFS/SMB to Amazon S3 or EFS, not for database-level replication or CDC. Option C is wrong because AWS Glue is an ETL service for data preparation and analytics, not for live database migration with ongoing replication.

Practice this question →

5

MCQmedium

Refer to the exhibit. An IAM policy is attached to a user. The user attempts to create an RDS DB instance named 'new-prod-db' with Oracle Standard Edition Two engine. What will happen?

A.The request will fail because the Deny condition matches the engine.

B.The request will fail because there is no Allow for 'new-prod-db'.

C.The request will succeed because the Allow matches the name pattern.

D.The request will succeed because the Deny is not effective for 'new-prod-db'.

AnswerA

Explicit Deny for Oracle denies the action.

Why this answer

The IAM policy includes an explicit Deny for the `rds:CreateDBInstance` action when the engine is `oracle-se2`, which matches the Oracle Standard Edition Two engine. Since explicit Deny statements override any Allow statements, the request fails regardless of the name pattern match. AWS IAM evaluates Deny statements first, making the Deny effective and blocking the operation.

Exam trap

The trap here is that candidates assume a matching Allow on the resource name will override a Deny, but AWS IAM's explicit Deny always takes precedence, making the engine-specific Deny the decisive factor.

How to eliminate wrong answers

Option B is wrong because an explicit Deny overrides the absence of an Allow; the Deny on the engine causes failure, not the lack of an Allow for the name. Option C is wrong because while the Allow matches the name pattern 'new-prod-db', the explicit Deny on the engine takes precedence and blocks the request. Option D is wrong because the Deny is effective for 'new-prod-db' since the engine condition matches 'oracle-se2', and Deny statements are always evaluated before Allow statements.

Practice this question →

6

Matchingmedium

Match each database engine to its default port number.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

3306

5432

1521

1433

3306

Why these pairings

The default ports are: MySQL on 3306, PostgreSQL on 5432, Oracle on 1521, and SQL Server on 1433. Common confusions include swapping MySQL and PostgreSQL ports.

Practice this question →

7

MCQmedium

A company is migrating a 2 TB SQL Server database to Amazon RDS for SQL Server. They need to minimize downtime and are using AWS DMS with CDC. The migration is taking longer than expected during the full load phase. Which change would most likely improve the full load performance?

A.Disable CDC to focus on full load only

B.Use AWS Schema Conversion Tool to optimize schema

C.Use a larger RDS instance class for the target

D.Increase the number of parallel load tasks in the DMS task settings

AnswerD

More parallel tasks can load data faster.

Why this answer

Increasing the number of parallel load tasks in the DMS task settings allows the full load to be split into multiple concurrent threads, each handling a subset of tables or partitions. This directly improves throughput by utilizing more of the available source and target resources, which is the most effective way to accelerate a slow full load phase when using AWS DMS with CDC.

Exam trap

The trap here is that candidates often assume a larger target instance (Option C) is the universal performance fix, but AWS DMS full load performance is more commonly limited by the parallelism of the load tasks, not the target instance size, especially when the target can keep up with writes.

How to eliminate wrong answers

Option A is wrong because disabling CDC would stop capturing ongoing changes, potentially increasing downtime when CDC is re-enabled later, and it does not address the root cause of slow full load performance. Option B is wrong because the AWS Schema Conversion Tool (SCT) is used for converting database schemas between different engines (e.g., Oracle to SQL Server), not for optimizing performance of an existing SQL Server migration to RDS for SQL Server. Option C is wrong because while a larger RDS instance class can improve target write performance, the bottleneck during full load is often the DMS replication instance or the source database's ability to export data, not the target instance size alone; increasing parallel load tasks is a more direct and effective tuning parameter.

Practice this question →

8

MCQeasy

A company is deploying a new web application that uses Amazon RDS for PostgreSQL. The database must be highly available with automatic failover across two Availability Zones. Which deployment option meets this requirement?

A.Deploy RDS PostgreSQL in a cross-region replication setup.

B.Deploy RDS PostgreSQL with Multi-AZ configuration.

C.Deploy RDS PostgreSQL in a single Availability Zone.

D.Deploy RDS PostgreSQL with a read replica in another AZ.

AnswerB

Multi-AZ provides automatic failover.

Why this answer

Amazon RDS Multi-AZ deployment automatically provisions and maintains a synchronous standby replica in a different Availability Zone. If the primary DB instance fails, Amazon RDS automatically fails over to the standby, providing high availability with automatic failover across two AZs. This meets the requirement without manual intervention or application changes.

Exam trap

The trap here is confusing a read replica in another AZ with Multi-AZ, as both involve a second AZ, but only Multi-AZ provides automatic synchronous failover without data loss or manual intervention.

How to eliminate wrong answers

Option A is wrong because cross-region replication is designed for disaster recovery and read scaling, not automatic failover within the same region; it requires manual promotion and does not provide synchronous replication. Option C is wrong because a single-AZ deployment has no standby replica and cannot provide automatic failover across Availability Zones. Option D is wrong because a read replica in another AZ is an asynchronous copy used for read scaling, not for automatic failover; promoting a read replica requires manual action and may lose data.

Practice this question →

9

Drag & Dropmedium

Arrange the steps to enable automated backups for an Amazon RDS for PostgreSQL DB instance in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

Automated backups are enabled by adjusting the backup retention period in the instance settings and applying the change.

Practice this question →

10

MCQeasy

A company is migrating a 10 GB MySQL database to Amazon RDS for MySQL. They have a 1 Gbps connection to AWS. The migration must be completed in the least amount of time with minimal manual effort. Which tool should be used?

A.AWS Schema Conversion Tool (SCT).

B.AWS Snowball Edge.

C.mysqldump and mysql command-line tools.

D.AWS Database Migration Service (DMS).

AnswerD

DMS automates the migration process and can complete quickly over high bandwidth.

Why this answer

AWS Database Migration Service (DMS) is the correct choice because it can perform a live, continuous migration of a 10 GB MySQL database to Amazon RDS for MySQL with minimal downtime and manual effort. DMS handles schema conversion (if needed), data replication, and ongoing changes via Change Data Capture (CDC), allowing the migration to complete in the least amount of time while automatically managing the full load and sync process over the 1 Gbps connection.

Exam trap

The trap here is that candidates often choose mysqldump (Option C) because it is familiar and free, but they overlook the requirement for minimal manual effort and the need for continuous replication, which DMS provides automatically.

How to eliminate wrong answers

Option A is wrong because AWS Schema Conversion Tool (SCT) is designed for heterogeneous migrations (e.g., Oracle to MySQL) and does not perform the actual data transfer; it only converts schema objects, so it cannot complete the migration alone. Option B is wrong because AWS Snowball Edge is intended for large-scale offline data transfers (typically >10 TB or over slow/unstable networks) and would introduce unnecessary shipping delays and manual effort for a 10 GB database that can easily be migrated online. Option C is wrong because mysqldump and mysql command-line tools require manual execution, do not support continuous replication or CDC, and would cause significant downtime during the dump and restore process, making it slower and more error-prone than DMS.

Practice this question →

11

MCQmedium

A company is migrating a 500 GB Oracle database to Amazon RDS for Oracle. They want to minimize downtime and use AWS DMS for ongoing replication. The source database is in a corporate data center behind a firewall. What is the recommended network setup for the DMS replication instance?

A.Deploy the DMS replication instance in a VPC that has a VPN or AWS Direct Connect connection to the corporate data center.

B.Launch the DMS replication instance with a public IP address and allow inbound traffic from the corporate firewall.

C.Create a VPC endpoint for the DMS service and route traffic through it.

D.Install the DMS replication software on a server in the corporate data center to connect directly to the source.

AnswerA

This provides a private network path for DMS to access the source database.

Why this answer

AWS DMS requires network connectivity between the replication instance and both the source and target databases. Since the source Oracle database is behind a corporate firewall, the DMS replication instance must be deployed in a VPC that has a VPN or AWS Direct Connect connection to the corporate data center. This establishes a private, secure, and low-latency network path for ongoing replication, minimizing downtime during migration.

Exam trap

The trap here is that candidates often assume DMS can use a public IP address or VPC endpoints for source connectivity, but DMS replication instances require direct network layer connectivity (Layer 3) to the source, which is only achieved via VPN or Direct Connect for on-premises sources.

How to eliminate wrong answers

Option B is wrong because assigning a public IP address to the DMS replication instance and allowing inbound traffic from the corporate firewall exposes the instance to the internet, which is a security risk and not recommended for sensitive database migrations; DMS does not natively support direct public IP connectivity for source databases behind firewalls without additional tunneling. Option C is wrong because a VPC endpoint for DMS is used to privately connect to the DMS service API, not to route replication traffic between the replication instance and the source database; it does not provide connectivity to an on-premises source. Option D is wrong because DMS replication software cannot be installed on a customer-managed server; AWS DMS is a fully managed service that runs only on AWS infrastructure, and the replication instance must be an AWS resource.

Practice this question →

12

MCQhard

A company is deploying a new application that requires low-latency reads from a relational database across multiple AWS Regions. The application is read-heavy and can tolerate eventual consistency. Which deployment option meets these requirements?

A.Deploy Amazon RDS for PostgreSQL with Multi-AZ and read replicas in the same Region.

B.Deploy a single Amazon RDS for MySQL instance with cross-Region read replicas.

C.Deploy Amazon Aurora Global Database with a primary Region and read replicas in secondary Regions.

D.Deploy Amazon DynamoDB Global Tables in multiple Regions.

AnswerC

Aurora Global Database provides low-latency reads in secondary Regions with eventual consistency.

Why this answer

Amazon Aurora Global Database is designed for low-latency global reads and disaster recovery, allowing up to five secondary Regions with dedicated read replicas that replicate data with a typical latency of under one second. This meets the requirement for low-latency reads across multiple Regions while tolerating eventual consistency, as reads from secondary Regions are eventually consistent with the primary.

Exam trap

The trap here is that candidates may confuse cross-Region read replicas in standard RDS with Aurora Global Database, not realizing that Aurora's dedicated global replication provides lower latency and better performance for multi-Region reads, or they may overlook the requirement for a relational database and choose DynamoDB Global Tables.

How to eliminate wrong answers

Option A is wrong because Multi-AZ and read replicas in the same Region do not provide cross-Region read capability, failing the requirement for low-latency reads across multiple AWS Regions. Option B is wrong because a single Amazon RDS for MySQL instance with cross-Region read replicas uses asynchronous replication that can introduce higher latency and does not offer the optimized global replication infrastructure of Aurora Global Database, making it less suitable for low-latency multi-Region reads. Option D is wrong because Amazon DynamoDB Global Tables is a NoSQL database, not a relational database, and the question explicitly requires a relational database.

Practice this question →

13

Multi-Selecthard

A company is planning to migrate a 2 TB Oracle database to Amazon Aurora PostgreSQL. The database contains large objects (LOBs) and uses stored procedures. Which TWO steps should the company take as part of the migration? (Choose two.)

Select 2 answers

A.Set up AWS DMS ongoing replication to keep the target in sync after migration.

B.Use AWS Schema Conversion Tool (SCT) to convert the Oracle schema and stored procedures to PostgreSQL-compatible format.

C.Configure AWS DMS with full LOB mode to migrate large objects.

D.Use AWS DMS native Oracle to PostgreSQL endpoint to migrate data without schema conversion.

E.Enable RDS Proxy to reduce connection overhead during migration.

AnswersB, C

SCT converts schema and code objects like stored procedures.

Why this answer

The AWS Schema Conversion Tool (SCT) is specifically designed to convert Oracle schema objects, including stored procedures, to PostgreSQL-compatible format. Since the migration involves stored procedures, SCT is necessary to handle the syntax and logic differences between Oracle PL/SQL and PostgreSQL PL/pgSQL, ensuring the target database schema is ready for migration.

Exam trap

AWS often tests the misconception that DMS can handle schema conversion automatically, but DMS only migrates data; schema conversion requires a separate tool like SCT.

Practice this question →

14

MCQhard

A company is migrating a 3 TB PostgreSQL database from on-premises to Amazon RDS for PostgreSQL. The migration must have minimal downtime. The on-premises network bandwidth to AWS is 1 Gbps. The database supports a critical application that cannot be stopped for more than 30 minutes. The migration team has set up AWS DMS with ongoing replication using CDC. The initial full load is expected to take 8 hours. During the migration, the DMS task fails with an error indicating that the source database's transaction log is being cleaned before DMS can capture changes. The source database has a transaction log retention period of 24 hours. The migration team notices that the CDC phase falls behind during peak hours. What should the team do to complete the migration successfully within the downtime window?

A.Use AWS Snowball to transfer the full database and then use DMS for CDC

B.Increase the network bandwidth using AWS Direct Connect

C.Increase the transaction log retention period on the source database and use a larger DMS replication instance

D.Decrease the transaction log retention period to free up space

AnswerC

Longer log retention prevents cleanup before DMS captures changes; larger instance boosts CDC throughput.

Why this answer

The issue is that DMS cannot keep up with changes during peak hours, causing the transaction logs to be cleaned before DMS reads them. Increasing the source database's transaction log retention period gives DMS more time to catch up. Using a larger DMS replication instance will increase processing capacity.

Option C is the best combination. Option A (Snowball) would take too long. Option B (Direct Connect) doesn't solve the log retention issue.

Option D (decrease retention) makes the problem worse.

Practice this question →

15

MCQhard

A company is migrating a 2 TB Oracle database to Amazon RDS for Oracle. The database has a large number of stored procedures, triggers, and functions. The company wants to minimize changes to the application code. Which AWS service should be used to assess and convert the database schema?

A.AWS Schema Conversion Tool (SCT)

B.AWS Database Migration Service (DMS)

C.AWS CloudEndure Migration

D.AWS CodeCommit

AnswerA

SCT assesses and converts schema objects to the target database.

Why this answer

AWS Schema Conversion Tool (SCT) is designed specifically to convert database schemas from one engine to another, including Oracle to Amazon RDS for Oracle. It assesses the source schema, identifies incompatibilities, and automatically converts stored procedures, triggers, and functions to minimize application code changes. SCT also provides action items for any manual remediation needed, ensuring a smooth migration with minimal code rewrites.

Exam trap

The trap here is that candidates confuse AWS DMS with schema conversion, but DMS only migrates data and ongoing replication, not schema objects like stored procedures, triggers, or functions.

How to eliminate wrong answers

Option B (AWS DMS) is wrong because DMS handles data migration (moving rows and tables), not schema conversion or assessment of stored procedures, triggers, or functions. Option C (AWS CloudEndure Migration) is wrong because it is used for lift-and-shift migration of entire servers (block-level replication), not for database schema assessment or conversion. Option D (AWS CodeCommit) is wrong because it is a source control service for storing code, not a database schema assessment or conversion tool.

Practice this question →

16

MCQmedium

A company is migrating a 1 TB Microsoft SQL Server database from on-premises to Amazon RDS for SQL Server. The on-premises database uses TDE for encryption. The company must ensure that the migrated database in RDS also uses TDE. Which solution meets this requirement?

A.Export the on-premises database with TDE certificates and import them into RDS.

B.Take a native backup of the on-premises database with TDE, upload to S3, and restore to RDS.

C.Use AWS SCT to convert the database to Amazon Aurora and enable encryption.

D.Use AWS DMS with ongoing replication to an RDS instance that has TDE enabled.

AnswerD

DMS can migrate data to an RDS instance with TDE enabled, and the data will be encrypted at rest.

Why this answer

AWS DMS can migrate data from an on-premises SQL Server database with TDE enabled to an Amazon RDS for SQL Server instance that has TDE enabled. DMS reads the decrypted data from the source (since TDE is transparent to applications) and writes it to the target, which can then encrypt the data at rest using RDS's built-in TDE support. This approach avoids the need to transfer TDE certificates or perform a native backup/restore, which are not supported for TDE-enabled databases in RDS.

Exam trap

The trap here is that candidates assume native backup/restore (Option B) is the simplest approach for TDE databases, but they overlook that RDS does not support restoring TDE-encrypted backups because the required certificates cannot be imported, making DMS the only viable migration path for preserving encryption at rest.

How to eliminate wrong answers

Option A is wrong because you cannot export TDE certificates from an on-premises SQL Server and import them into Amazon RDS for SQL Server; RDS does not allow direct access to the certificate store or the ability to manage TDE certificates manually. Option B is wrong because native backup/restore of a TDE-enabled database to RDS is not supported; RDS for SQL Server cannot restore a TDE-encrypted backup without the original certificates, and the backup file itself remains encrypted and unreadable. Option C is wrong because AWS SCT is a schema conversion tool, not a data migration tool, and converting to Amazon Aurora does not preserve TDE; Aurora uses its own encryption mechanism (KMS) and does not support SQL Server TDE.

Practice this question →

17

MCQeasy

A developer is deploying an application that uses Amazon DynamoDB as its database. The application experiences sudden spikes in traffic. Which DynamoDB feature should the developer use to handle the spikes without manual intervention?

A.DynamoDB Accelerator (DAX)

B.DynamoDB on-demand capacity mode

C.DynamoDB auto scaling

D.DynamoDB global tables

AnswerC

Auto scaling adjusts read/write capacity automatically based on traffic.

Why this answer

DynamoDB auto scaling (option C) is the correct choice because it automatically adjusts the provisioned read and write capacity based on actual traffic patterns using the AWS Application Auto Scaling service. This allows the application to handle sudden spikes in traffic without manual intervention by increasing capacity when utilization rises and decreasing it when traffic subsides, all while maintaining a target utilization percentage.

Exam trap

The trap here is that candidates often confuse DynamoDB on-demand capacity mode (option B) with a feature that handles spikes without manual intervention, but the question specifically asks for a 'feature' that adjusts provisioned capacity, and on-demand is a capacity mode that eliminates the need for provisioning altogether, not a feature that handles spikes within a provisioned model.

How to eliminate wrong answers

Option A is wrong because DynamoDB Accelerator (DAX) is an in-memory caching layer that improves read latency but does not handle write capacity spikes or automatically adjust throughput provisioning. Option B is wrong because DynamoDB on-demand capacity mode handles spikes by scaling instantly, but it is not a feature that requires manual intervention—it is a capacity mode, not a feature that the developer 'uses' to handle spikes without manual intervention; the question asks for a feature that handles spikes without manual intervention, and on-demand is a billing and capacity mode that does this automatically, but the exam context often distinguishes auto scaling as the feature for provisioned capacity, and on-demand is a separate mode, not a feature that adjusts provisioned capacity. Option D is wrong because DynamoDB global tables provide multi-region replication for disaster recovery and low-latency reads, but they do not handle sudden traffic spikes by adjusting capacity.

Practice this question →

18

MCQeasy

A company is migrating a PostgreSQL database to Amazon RDS for PostgreSQL. They want to automate the deployment of the RDS instance using infrastructure as code. Which AWS service should they use?

A.Amazon EC2 Auto Scaling.

B.AWS Management Console.

C.AWS CloudFormation.

D.AWS Command Line Interface (CLI).

AnswerC

CloudFormation enables declarative provisioning of RDS instances.

Why this answer

AWS CloudFormation is the correct service for automating the deployment of an RDS for PostgreSQL instance using infrastructure as code. It allows you to define the entire RDS instance configuration—including DB instance class, storage, backup retention, and security groups—in a declarative JSON or YAML template, which can be version-controlled and reused for consistent, repeatable deployments.

Exam trap

The trap here is that candidates often confuse the AWS CLI (a scripting tool) with infrastructure as code, but the CLI lacks the declarative, state-management, and drift-detection capabilities that define true IaC services like CloudFormation.

How to eliminate wrong answers

Option A is wrong because Amazon EC2 Auto Scaling is designed to automatically adjust the number of EC2 instances based on demand, not to provision or manage RDS instances; it cannot create or configure a PostgreSQL database. Option B is wrong because the AWS Management Console is a manual, point-and-click interface that does not support infrastructure as code or automation; it is not suitable for repeatable, version-controlled deployments. Option D is wrong because the AWS Command Line Interface (CLI) is a scripting tool that can automate RDS creation via commands, but it is not an infrastructure-as-code service—it lacks declarative templates, drift detection, and stack management capabilities that CloudFormation provides.

Practice this question →

19

MCQhard

A company is migrating a 500 GB database from Amazon RDS for MySQL to Amazon Aurora MySQL. The migration must be completed with minimal downtime and no data loss. The RDS instance is Multi-AZ. Which approach should be used?

A.Use AWS DMS with ongoing replication from RDS to Aurora

B.Take a snapshot of the RDS instance and restore to Aurora

C.Set up native MySQL replication from the RDS Multi-AZ standby to Aurora

D.Create an Aurora MySQL read replica from the RDS MySQL instance, then promote it

AnswerD

Aurora MySQL supports creating a read replica from RDS MySQL, allowing minimal downtime.

Why this answer

Creating an Aurora MySQL read replica from the RDS MySQL instance uses the native MySQL binary log (binlog) replication to keep the Aurora cluster synchronized with minimal downtime. Once the replica lag reaches zero, you promote the Aurora cluster to make it the primary database, ensuring no data loss and a very short cutover window.

Exam trap

The trap here is that candidates may assume AWS DMS is always the best choice for minimal-downtime migrations, but for MySQL-to-Aurora migrations, native MySQL replication is simpler, faster, and avoids the overhead of an additional DMS instance.

How to eliminate wrong answers

Option A is wrong because AWS DMS with ongoing replication requires a full load plus change data capture (CDC), which introduces additional latency and complexity, and is not the most efficient method for a 500 GB database when native MySQL replication is available. Option B is wrong because taking a snapshot and restoring to Aurora is a one-time, offline migration that does not support ongoing replication, resulting in significant downtime while the snapshot is taken and restored. Option C is wrong because you cannot set up native MySQL replication from the RDS Multi-AZ standby to Aurora; the standby is not directly accessible for replication, and MySQL replication must originate from the primary instance's binlog.

Practice this question →

20

MCQmedium

A company is migrating an on-premises Oracle database to Amazon RDS for Oracle. They want to use Oracle GoldenGate for replication. Which AWS service can be used to simplify the setup of GoldenGate on AWS?

A.AWS DMS

B.Amazon RDS for Oracle with GoldenGate enabled

C.AWS CloudFormation

D.AWS Marketplace

AnswerD

Marketplace offers pre-configured GoldenGate AMIs for EC2.

Why this answer

AWS Marketplace offers pre-configured Oracle GoldenGate AMIs that simplify the setup and deployment of GoldenGate on EC2, reducing the manual installation and configuration effort. This is the correct choice because the question asks for a service that simplifies the setup of GoldenGate itself, not the migration tool or infrastructure orchestration.

Exam trap

The trap here is that candidates often confuse AWS DMS (a managed migration service) with Oracle GoldenGate, or assume that Amazon RDS for Oracle natively supports GoldenGate as a feature, when in fact GoldenGate must be run on a separate EC2 instance or on-premises.

How to eliminate wrong answers

Option A is wrong because AWS DMS is a managed migration service that can perform homogenous and heterogeneous migrations, but it does not simplify the setup of Oracle GoldenGate; DMS and GoldenGate are separate replication technologies. Option B is wrong because Amazon RDS for Oracle does not have a 'GoldenGate enabled' feature; GoldenGate must be installed on a separate EC2 instance or on-premises, and RDS does not allow direct installation of custom software like GoldenGate. Option C is wrong because AWS CloudFormation can automate the deployment of infrastructure, including EC2 instances for GoldenGate, but it does not simplify the setup of GoldenGate itself—it only automates the provisioning of resources, not the configuration of the GoldenGate software.

Practice this question →

21

MCQhard

A team is deploying a new Amazon Aurora MySQL database and needs to load 5 TB of data from an existing Amazon RDS for MySQL database with minimal downtime. The data is stored in InnoDB tables. Which approach is MOST efficient?

A.Take a snapshot of the RDS for MySQL instance and restore to Aurora

B.Use AWS DMS with full load and ongoing replication

C.Use mysqldump to export the database and import into Aurora

D.Create an Aurora read replica from the RDS for MySQL instance using binlog replication

AnswerD

This method minimizes downtime by replicating data continuously.

Why this answer

Creating an Aurora read replica from an RDS for MySQL instance using binlog replication allows the Aurora cluster to synchronize with the source database in near real-time. Once the replica lag reaches zero, you can promote the Aurora cluster to become the primary database, achieving minimal downtime. This approach leverages the native MySQL binlog replication, which is efficient for large datasets like 5 TB and avoids the overhead of exporting or snapshotting the entire database.

Exam trap

The trap here is that candidates often assume AWS DMS is the best tool for all migrations, but for homogeneous MySQL-to-Aurora migrations with large datasets and minimal downtime, native binlog replication is more efficient because it avoids the overhead of DMS's change data capture (CDC) and schema conversion layers.

How to eliminate wrong answers

Option A is wrong because taking a snapshot of the RDS for MySQL instance and restoring it to Aurora requires a significant downtime window to ensure data consistency, and the snapshot does not capture ongoing changes, so it cannot achieve minimal downtime. Option B is wrong because AWS DMS with full load and ongoing replication can be used, but it is less efficient for a 5 TB dataset compared to binlog replication due to the overhead of the DMS transformation engine and the need to handle schema conversion; additionally, DMS may introduce additional latency and complexity for a homogeneous MySQL-to-Aurora migration. Option C is wrong because using mysqldump to export and import 5 TB of data would require a prolonged downtime period, as the export locks tables or requires a consistent snapshot, and the import process is slow, making it unsuitable for minimal downtime.

Practice this question →

22

MCQmedium

A company is migrating a 5 TB Oracle database to Amazon Aurora PostgreSQL. The database has a 4-hour maintenance window weekly. Which migration approach minimizes downtime?

A.Use Oracle Data Pump to export and pg_restore to import.

B.Use AWS Database Migration Service (DMS) with change data capture (CDC).

C.Use AWS Schema Conversion Tool (SCT) to convert schema and then copy data.

D.Use AWS DMS full load only and then manually sync.

AnswerB

DMS with CDC provides near-zero downtime.

Why this answer

AWS DMS with CDC allows you to perform an initial full load of the 5 TB database and then continuously replicate ongoing changes from the source Oracle database to the target Aurora PostgreSQL. This minimizes downtime because you can keep the source database fully operational during the migration and only perform a brief cutover to switch applications to the new database, well within the 4-hour maintenance window.

Exam trap

The trap here is that candidates often assume a full load plus manual sync (Option D) is sufficient, but they overlook the fact that for a 5 TB database, the manual sync window would be too long to fit within the 4-hour maintenance window, whereas CDC enables a near-zero-downtime cutover.

How to eliminate wrong answers

Option A is wrong because Oracle Data Pump export and pg_restore import require the source database to be offline or in a restricted state for the entire duration of the export and import, which for a 5 TB database would far exceed the 4-hour maintenance window. Option C is wrong because the AWS Schema Conversion Tool (SCT) only converts the schema and does not handle data migration; you would still need a separate data copy step that would cause significant downtime. Option D is wrong because AWS DMS full load only copies a snapshot of the data at a point in time, and then you would need to manually sync any changes made during the load, which is error-prone and would require a longer downtime window to ensure consistency.

Practice this question →

23

MCQmedium

A company is deploying a new application that requires a relational database with automatic failover and cross-Region disaster recovery. The application is read-heavy and expects up to 10 GB of data. Which combination of AWS services should be used?

A.Amazon RDS for MySQL with Multi-AZ and a read replica in another Region

B.Amazon S3 with AWS Glue and Amazon Athena

C.Amazon Aurora with Multi-AZ and an Aurora global database

D.Amazon DynamoDB with global tables

AnswerC

Aurora global database provides cross-Region replication and fast failover.

Why this answer

Amazon Aurora with Multi-AZ provides high availability within a single Region, while Aurora Global Database enables cross-Region disaster recovery with typical replication latency of under one second. Aurora is optimized for read-heavy workloads and scales automatically, making it ideal for the 10 GB dataset and the application's requirements.

Exam trap

The trap here is that candidates often confuse Multi-AZ with cross-Region disaster recovery, assuming a read replica in another Region provides automatic failover, but in RDS MySQL, read replicas require manual promotion and do not support automatic cross-Region failover.

How to eliminate wrong answers

Option A is wrong because Amazon RDS for MySQL with Multi-AZ provides automatic failover within a single Region, but a read replica in another Region does not support automatic cross-Region failover for disaster recovery; you would need to manually promote the read replica, which does not meet the automatic failover requirement. Option B is wrong because Amazon S3 with AWS Glue and Athena is a serverless analytics and query service, not a relational database; it lacks transactional consistency, automatic failover, and relational database features required by the application. Option D is wrong because Amazon DynamoDB with global tables is a NoSQL key-value and document database, not a relational database; it does not support SQL queries, joins, or relational constraints, which the application explicitly requires.

Practice this question →

24

Multi-Selecteasy

Which TWO options are valid methods for migrating an on-premises SQL Server database to Amazon RDS for SQL Server with minimal downtime? (Choose TWO.)

Select 2 answers

A.Use AWS CloudEndure to replicate the entire server.

B.Copy the database files to Amazon S3 and restore to RDS.

C.Use SQL Server Import/Export Wizard.

D.Use AWS DMS with ongoing replication from the source.

E.Use native backup and restore with log shipping to RDS.

AnswersD, E

DMS can perform continuous replication to keep the target in sync.

Why this answer

AWS DMS with ongoing replication (change data capture, CDC) is a valid method for migrating to Amazon RDS for SQL Server with minimal downtime because it allows you to perform a full load of the database and then continuously replicate incremental changes from the source until you cut over. This keeps the target nearly in sync, reducing the downtime window to seconds or minutes.

Exam trap

The trap here is that candidates often confuse 'native backup and restore with log shipping' (Option E) as a valid minimal-downtime method, but while log shipping can reduce downtime, it requires manual setup of a secondary database and is not natively supported by Amazon RDS for SQL Server without using AWS DMS or other tools; however, in this question, Option E is actually correct because you can use native backup/restore to seed the RDS instance and then use log shipping (via AWS DMS or manual T-SQL) to apply transaction log backups, achieving minimal downtime.

Practice this question →

25

MCQhard

A company wants to migrate a 2 TB PostgreSQL database from on-premises to Amazon Aurora PostgreSQL. The database has high write throughput and the migration must have minimal impact on source performance. Which solution is MOST appropriate?

A.Create a read replica of the on-premises database and promote it to Aurora.

B.Use AWS DMS with ongoing replication from the source to Aurora.

C.Use pglogical to set up logical replication from the source to Aurora.

D.Set up native PostgreSQL streaming replication from on-premises to Aurora.

AnswerC

pglogical provides logical replication with minimal overhead on the source.

Why this answer

Pglogical is a PostgreSQL extension that provides logical replication with minimal overhead on the source, making it ideal for high-write-throughput databases. It allows selective table replication and does not require physical changes to the source, thus avoiding performance impact. AWS DMS (Option B) can also perform ongoing replication but introduces additional overhead and complexity, and it is not as tightly integrated with PostgreSQL's native replication mechanisms as pglogical.

Exam trap

The trap here is that candidates often assume AWS DMS is always the best choice for minimal-impact migrations, but for PostgreSQL-to-Aurora migrations, native logical replication via pglogical is more efficient and less intrusive on high-write-throughput sources.

How to eliminate wrong answers

Option A is wrong because creating a read replica of an on-premises database and promoting it to Aurora is not a supported migration path; read replicas are a feature of Amazon RDS/Aurora, not on-premises PostgreSQL. Option B is wrong because AWS DMS with ongoing replication can be used but it adds extra load on the source due to its change data capture (CDC) mechanism, which can impact high-write-throughput workloads, and it is less efficient than native logical replication. Option D is wrong because native PostgreSQL streaming replication (physical replication) cannot be set up from on-premises to Aurora as Aurora does not accept physical WAL streaming from external sources; it only supports logical replication via pglogical or DMS.

Practice this question →

26

MCQhard

A media company is migrating a 5 TB MongoDB database to Amazon DocumentDB. The migration must have minimal downtime. The source MongoDB uses sharding across 10 shards. Which migration strategy is MOST appropriate?

A.Use native MongoDB replication to sync to DocumentDB

B.Use AWS DMS with MongoDB as source and DocumentDB as target, enabling CDC

C.Export data to S3 and use AWS Glue to load into DocumentDB

D.Use mongoexport to export data and mongoimport to import into DocumentDB

AnswerB

DMS supports MongoDB to DocumentDB migration with CDC for minimal downtime.

Why this answer

AWS DMS with CDC (Change Data Capture) is the most appropriate strategy because it supports ongoing replication from a sharded MongoDB source to Amazon DocumentDB, enabling near-zero downtime migration. DMS can handle the 5 TB dataset and 10 shards by using the MongoDB oplog to capture changes after the initial full load, ensuring minimal interruption to the media company's operations.

Exam trap

The trap here is that candidates assume native MongoDB replication (Option A) works because DocumentDB claims MongoDB compatibility, but DocumentDB does not implement the MongoDB replication protocol, making DMS with CDC the only viable near-zero downtime option.

How to eliminate wrong answers

Option A is wrong because native MongoDB replication uses the MongoDB replication protocol to sync data between MongoDB instances, but Amazon DocumentDB does not support the MongoDB replication protocol as a replica set member, so direct replication is not possible. Option C is wrong because exporting data to S3 and using AWS Glue to load into DocumentDB is a batch-oriented approach that does not support CDC, resulting in significant downtime during the migration of a 5 TB dataset. Option D is wrong because mongoexport and mongoimport are offline tools that export/import data in JSON or CSV format, requiring the source database to be quiesced or taken offline, which does not meet the minimal downtime requirement.

Practice this question →

27

MCQeasy

A company wants to migrate a 500 GB SQL Server database to Amazon RDS for SQL Server with the least amount of downtime. The on-premises network has a 1 Gbps connection to AWS. Which approach should be used?

A.Use AWS DMS with ongoing replication from on-premises to RDS

B.Use AWS Snowball to transfer the database backup, then restore to RDS

C.Copy database files to S3 and then use RDS import

D.Use native SQL Server backup to S3, then restore to RDS

AnswerA

DMS with CDC minimizes downtime by synchronizing changes until cutover.

Why this answer

AWS DMS with ongoing replication (change data capture, CDC) allows you to perform a full load of the 500 GB database while continuously replicating ongoing changes from the on-premises SQL Server to Amazon RDS for SQL Server. This minimizes downtime to a brief cutover window when you stop writes on the source and redirect traffic to the target. The 1 Gbps connection is sufficient for the initial load and ongoing replication, making this the most effective approach for minimal downtime.

Exam trap

The trap here is that candidates often choose native backup/restore (Option D) thinking it is the fastest because it is familiar, but they overlook that it requires a full backup (causing downtime) and lacks ongoing replication, whereas DMS with CDC provides near-zero downtime by replicating changes continuously.

How to eliminate wrong answers

Option B is wrong because AWS Snowball is designed for offline data transfer of large datasets (typically >10 TB or over slow networks) and introduces significant logistical delays (shipping, processing), which does not achieve the least amount of downtime for a 500 GB database over a 1 Gbps connection. Option C is wrong because copying database files to S3 and then using RDS import is not a supported method for SQL Server; RDS for SQL Server does not support importing from raw database files in S3—you must use native backup/restore or DMS. Option D is wrong because native SQL Server backup to S3 and restore to RDS requires taking a full backup, which locks the database and incurs downtime during the backup process, and does not provide ongoing replication to minimize the cutover window.

Practice this question →

28

MCQeasy

A company is migrating an on-premises DynamoDB table to Amazon DynamoDB in another AWS region. What is the most efficient method to migrate the data?

A.Use DynamoDB global tables to replicate data across regions.

B.Export the table to S3 using AWS Data Pipeline, then import into DynamoDB in the target region.

C.Set up DynamoDB Streams and write a custom consumer to replicate data to the target region.

D.Use AWS DMS to replicate data from on-premises to DynamoDB.

AnswerA

Global tables automatically replicate data across regions, simplifying migration.

Why this answer

DynamoDB global tables provide a fully managed, multi-region, multi-master replication solution that automatically replicates data across AWS regions with low latency. This eliminates the need for custom code or external tools, making it the most efficient method for migrating an on-premises DynamoDB table to another region, as it handles ongoing replication and conflict resolution natively.

Exam trap

The trap here is that candidates often confuse DynamoDB global tables with DynamoDB Streams or AWS DMS, assuming that manual replication or database migration services are necessary, when in fact global tables are the simplest and most efficient solution for cross-region migration of DynamoDB tables.

How to eliminate wrong answers

Option B is wrong because exporting to S3 via AWS Data Pipeline and then importing is a batch-oriented approach that requires manual orchestration, does not support continuous replication, and introduces additional latency and complexity compared to the native replication of global tables. Option C is wrong because setting up DynamoDB Streams with a custom consumer requires developing, deploying, and maintaining custom code to handle replication, which is less efficient and more error-prone than using the built-in global tables feature. Option D is wrong because AWS DMS is designed for migrating relational databases and does not support DynamoDB as a source or target for replication; it cannot be used to migrate data from an on-premises DynamoDB table to DynamoDB in another region.

Practice this question →

29

MCQmedium

A company is planning to migrate a MongoDB database to Amazon DocumentDB. The database has several sharded collections. Which migration strategy should be used?

A.Set up MongoDB replica set to replicate directly to DocumentDB.

B.Use AWS DMS with MongoDB as source and DocumentDB as target, enabling ongoing replication.

C.Use AWS Schema Conversion Tool (SCT) to convert the schema, then manually migrate data.

D.Export data using mongodump and import using mongorestore.

AnswerB

DMS supports homogeneous migration with minimal downtime.

Why this answer

AWS DMS supports MongoDB as a source and Amazon DocumentDB as a target, and it can perform ongoing replication (change data capture) to keep the target synchronized with the source during migration. This is essential for sharded MongoDB collections because it minimizes downtime by allowing the source to remain operational while data is migrated and changes are continuously applied.

Exam trap

The trap here is that candidates may assume a simple dump-and-restore (Option D) is sufficient for sharded collections, overlooking the need for minimal downtime and ongoing replication that AWS DMS provides.

How to eliminate wrong answers

Option A is wrong because MongoDB replica sets cannot replicate directly to DocumentDB; DocumentDB uses its own replication protocol and is not a MongoDB replica set member. Option C is wrong because AWS Schema Conversion Tool (SCT) is designed for schema conversion of relational databases, not for NoSQL databases like MongoDB or DocumentDB, and it does not handle data migration. Option D is wrong because mongodump and mongorestore perform a one-time, offline export/import, which does not support ongoing replication and would require significant downtime, especially for sharded collections.

Practice this question →

30

MCQhard

An e-commerce company is migrating its PostgreSQL database to Amazon RDS for PostgreSQL. The database has multiple large tables (over 500 GB each) and the migration window is only 2 hours. Which strategy would be MOST effective to meet the time constraint?

A.Use a single DMS task with full LOB mode.

B.Use AWS DMS with parallel load by splitting tables into multiple tasks.

C.Increase the RDS instance size and use pg_dump.

D.Use AWS SCT to optimize schema and then one DMS task.

AnswerB

Parallel load accelerates migration.

Why this answer

AWS DMS with parallel load by splitting tables into multiple tasks allows concurrent data transfer across multiple threads, maximizing throughput for large tables. This approach directly addresses the 2-hour migration window by distributing the workload, whereas a single task would be bottlenecked by sequential processing. Parallel load is specifically designed for high-volume migrations where time is critical.

Exam trap

The trap here is that candidates assume a single DMS task with full LOB mode is sufficient for large tables, underestimating the severe performance penalty of sequential LOB processing, and overlook the parallel load feature designed specifically for this scenario.

How to eliminate wrong answers

Option A is wrong because a single DMS task with full LOB mode processes LOB data sequentially and can be extremely slow for large tables, often failing to meet tight migration windows due to single-threaded LOB handling. Option C is wrong because increasing the RDS instance size and using pg_dump still relies on a single-threaded dump process, which cannot parallelize across multiple tables or partitions, and the migration window is too short for 500 GB+ tables. Option D is wrong because AWS SCT optimizes schema but does not accelerate data transfer; using one DMS task afterward still suffers from the same single-task bottleneck as option A.

Practice this question →

31

MCQhard

A company is migrating a 5 TB Microsoft SQL Server database to Amazon RDS for SQL Server. The migration must have minimal downtime. The source database is hosted on an EC2 instance. Which combination of steps should be taken?

A.Take a native backup of the source, upload to S3, and restore to RDS

B.Use AWS DMS with full load and ongoing replication

C.Create an RDS read replica from the EC2-hosted database

D.Use the SQL Server Import and Export Wizard

AnswerA

Native backup/restore is efficient for large databases and supports minimal downtime.

Why this answer

Native backup and restore to Amazon RDS for SQL Server is the fastest and most reliable method for migrating a large database like 5 TB with minimal downtime. By taking a full backup, uploading it to Amazon S3, and restoring it to RDS, you avoid the overhead of ongoing replication setup and can schedule the final cutover during a brief maintenance window. This approach leverages RDS's native support for restoring from S3, ensuring data integrity and minimizing the migration window.

Exam trap

The trap here is that candidates often assume AWS DMS is always the best choice for minimal downtime migrations, but for large SQL Server databases, native backup and restore to RDS is simpler, faster, and more reliable, especially when the source is on EC2 and the target is RDS.

How to eliminate wrong answers

Option B is wrong because AWS DMS with full load and ongoing replication, while capable of minimal downtime, introduces additional complexity and potential performance bottlenecks for a 5 TB database, and the ongoing replication requires continuous change data capture (CDC) which may not be supported or optimal for SQL Server in all scenarios. Option C is wrong because RDS read replicas cannot be created from an EC2-hosted database; read replicas are only supported between RDS instances, not from external sources. Option D is wrong because the SQL Server Import and Export Wizard is a row-by-row data movement tool that is extremely slow for large databases and does not support ongoing replication, making it unsuitable for a 5 TB migration with minimal downtime requirements.

Practice this question →

32

MCQmedium

A company is migrating a 2 TB on-premises PostgreSQL database to Amazon RDS for PostgreSQL. The migration must have minimal downtime and support ongoing replication. Which AWS service should be used?

A.AWS DMS

B.AWS Snowball Edge

C.AWS S3

D.RDS native PostgreSQL logical replication

AnswerA

DMS supports ongoing replication from on-premises to RDS, minimizing downtime.

Why this answer

AWS DMS (Database Migration Service) is the correct choice because it supports both full-load migration and ongoing change data capture (CDC) replication from an on-premises PostgreSQL source to Amazon RDS for PostgreSQL, enabling minimal downtime. DMS uses logical replication slots to capture incremental changes, allowing the target database to stay synchronized during the cutover window.

Exam trap

The trap here is that candidates may assume native PostgreSQL logical replication (Option D) is always the best choice for minimal-downtime migrations, but they overlook that DMS provides a fully managed, AWS-integrated solution that handles schema conversion, monitoring, and automatic failover, which is essential for a 2 TB database migration with ongoing replication.

How to eliminate wrong answers

Option B (AWS Snowball Edge) is wrong because it is designed for offline, bulk data transfer of large datasets over physical devices, not for live, ongoing replication with minimal downtime. Option C (AWS S3) is wrong because it is an object storage service and cannot perform database replication or CDC; it would require additional tools to extract and load data, introducing significant downtime. Option D (RDS native PostgreSQL logical replication) is wrong because while it can replicate data, it requires the source database to be an RDS instance or have specific configurations (e.g., wal_level = logical) that may not be feasible or supported for an on-premises PostgreSQL source, and it does not provide the managed, automated migration and monitoring features of DMS.

Practice this question →

33

MCQhard

A company is migrating a 5 TB Oracle database to Amazon Aurora PostgreSQL. The migration must be completed within a weekend. The on-premises network has a 1 Gbps connection to AWS. What is the MOST efficient migration strategy?

A.Use AWS S3 Transfer Acceleration to upload the database dump to S3 and then load into Aurora

B.Use AWS DMS with direct connect to export the Oracle database directly to Aurora

C.Use AWS DMS with change data capture over the existing network connection

D.Use AWS Snowball Edge to transfer the data and then load into Aurora

AnswerB

Correct. AWS DMS with Direct Connect leverages a dedicated, high-bandwidth connection to migrate the database directly to Aurora, making it the most efficient strategy for a 5 TB migration within a weekend.

Why this answer

With a 1 Gbps connection, the theoretical maximum transfer rate is ~450 GB/hour, so transferring 5 TB would take about 11 hours, well within a weekend. AWS DMS with Direct Connect provides a dedicated, high-bandwidth path for the migration, making it the most efficient strategy. Snowball Edge (Option D) requires ordering, loading, shipping (1-2 days), and importing, which cannot complete within a weekend.

Options A and C are less efficient: S3 Transfer Acceleration adds unnecessary steps, and DMS with CDC is designed for ongoing replication, not initial load.

Exam trap

The trap is that candidates assume Snowball is always faster for large data volumes, ignoring the shipping delays and the fact that a 1 Gbps link can transfer 5 TB in about 11 hours, well within a weekend. Network-based tools like DMS can be more efficient when the connection is adequate.

How to eliminate wrong answers

Option A is wrong because AWS S3 Transfer Acceleration only optimizes the path over the public internet but does not increase the available bandwidth of the 1 Gbps link; the total transfer time for 5 TB would still exceed the weekend window when factoring in export/import overhead. Option B is wrong because AWS DMS with Direct Connect still operates over the same 1 Gbps network connection, and the initial full load of 5 TB would take too long; Direct Connect does not increase bandwidth beyond the provisioned link speed. Option C is wrong because AWS DMS with change data capture (CDC) is designed for ongoing replication, not for the initial bulk load of 5 TB; the initial load still requires transferring the full dataset over the network, which is not feasible within a weekend on a 1 Gbps link.

Practice this question →

34

MCQeasy

Refer to the exhibit. A company is migrating from an on-premises MySQL database to Amazon RDS for MySQL. The DBA wants to connect to the RDS instance using the endpoint shown. What additional step is required to allow the DBA's client to connect?

A.Modify the security group to allow inbound traffic on port 3306 from the client IP

B.Create a Route 53 record for the endpoint

C.Create a MySQL user that matches the client's IP

D.Change the RDS instance to be publicly accessible

AnswerA

Security group rules control inbound traffic; port 3306 must be open.

Why this answer

Amazon RDS security groups act as a virtual firewall controlling inbound and outbound traffic. By default, no inbound traffic is allowed on port 3306 (MySQL). To permit the DBA's client to connect, you must modify the security group associated with the RDS instance to add an inbound rule that allows TCP traffic on port 3306 from the client's IP address (or a range that includes it).

Without this rule, the connection is blocked at the network level regardless of other configurations.

Exam trap

The DBS-C01 exam often tests the misconception that making an RDS instance publicly accessible alone is sufficient for connectivity, but the security group rule is the actual gatekeeper; public accessibility only assigns a public IP, while the security group still blocks traffic without an explicit inbound rule.

How to eliminate wrong answers

Option B is wrong because creating a Route 53 record for the endpoint is unnecessary; the RDS endpoint is already a DNS name that resolves to the instance's IP address, and Route 53 is not required for connectivity. Option C is wrong because MySQL user accounts are authenticated by username and password, not by client IP address (unless the user is explicitly created with a host restriction, but that is not a required step for basic connectivity). Option D is wrong because making the RDS instance publicly accessible is not required if the DBA's client is connecting from within the same VPC or via a VPN/Direct Connect; the security group rule alone controls inbound access, and public accessibility is only needed for connections from outside the VPC.

Practice this question →

35

MCQmedium

A company is migrating a 500 GB PostgreSQL database from on-premises to Amazon Aurora PostgreSQL. The migration must be completed within 6 hours with minimal downtime. The on-premises network bandwidth is 500 Mbps. The team decides to use AWS DMS. During initial full load, DMS reports a 'Target metadata error: cannot write to Aurora' for a specific table. Investigation shows that the table has a trigger that tries to insert into an external web service. What should the team do to resolve this issue?

A.Disable the trigger on the target Aurora database during migration.

B.Increase the DMS replication instance size.

C.Upgrade the DMS replication instance engine version.

D.Disable the trigger on the source database.

AnswerA

This is correct. Disabling the trigger on the target database during migration stops the external web service call, resolving the error.

Why this answer

Disabling the trigger on the target Aurora PostgreSQL database during migration prevents the trigger from firing, which was causing the 'Target metadata error: cannot write to Aurora' error. The trigger's attempt to insert into an external web service is not compatible with DMS loading data. Option B is incorrect because increasing the DMS replication instance size does not address the trigger issue.

Option C is incorrect because upgrading the DMS replication instance engine version does not address the trigger issue. Option D is incorrect because disabling the trigger on the source database does not prevent the trigger on the target from firing when DMS writes data; the error occurs on the target.

Practice this question →

36

MCQmedium

A company is deploying a new application that uses Amazon RDS for PostgreSQL. The application must be highly available with automatic failover in the event of a database failure. Which configuration should be used?

A.Deploy a Multi-AZ RDS instance with a standby in a different Availability Zone

B.Use a read replica in a different Availability Zone

C.Deploy the RDS instance in a single Availability Zone with automated backups

D.Deploy the RDS instance in a Cross-Region replication configuration

AnswerA

Multi-AZ provides automatic failover for high availability.

Why this answer

Multi-AZ RDS for PostgreSQL provides synchronous replication to a standby instance in a different Availability Zone, ensuring automatic failover with minimal data loss. This configuration meets the requirement for high availability and automatic failover without manual intervention, as the RDS service handles the DNS change and standby promotion.

Exam trap

The trap here is that candidates often confuse read replicas with Multi-AZ, assuming a read replica can serve as a failover target, but AWS explicitly requires manual promotion for read replicas and does not provide automatic failover.

How to eliminate wrong answers

Option B is wrong because a read replica is designed for read scaling and does not support automatic failover; promoting a read replica requires manual action and can result in data loss if replication lag exists. Option C is wrong because a single-AZ deployment lacks a standby instance, so any database failure leads to downtime until a new instance is restored from backups, which is not automatic failover. Option D is wrong because Cross-Region replication is for disaster recovery across AWS regions, not for automatic failover within a region, and it involves asynchronous replication with potential data loss and higher latency.

Practice this question →

37

MCQmedium

A company is deploying a new application on Amazon RDS for PostgreSQL. The application requires a database with a specific parameter group that sets 'max_connections' to 500 and 'shared_buffers' to 25% of the instance memory. The company uses CloudFormation to deploy the RDS instance. The CloudFormation template creates a DBInstance with a DBParameterGroup. The deployment fails because the parameter group cannot be associated with the DB instance. What is the most likely cause?

A.The parameter group uses an invalid value for 'shared_buffers' because it must be an integer, not a percentage.

B.The 'max_connections' value of 500 exceeds the allowed maximum for the instance class.

C.The CloudFormation template does not include a DependsOn clause linking the DBParameterGroup to the DBInstance.

D.The DBParameterGroup is not in the same region as the DBInstance.

AnswerA

RDS requires absolute values for 'shared_buffers', not percentages.

Why this answer

In Amazon RDS for PostgreSQL, the 'shared_buffers' parameter must be specified as an integer value (in 8 KB blocks) or a string ending with 'kB', 'MB', or 'GB', not as a percentage of instance memory. Using a percentage like '25%' is invalid and causes the parameter group association to fail. Option B is incorrect because 'max_connections' can be set to 500 as long as it does not exceed the instance class limits, but that is not the issue here.

Option C is incorrect because CloudFormation automatically handles dependencies when resources are referenced; explicit DependsOn is not required. Option D is incorrect because CloudFormation templates can reference resources across regions only if explicitly designed, but the region mismatch would cause a different error, not parameter group association failure.

Practice this question →

38

MCQmedium

A company is deploying an Amazon RDS for MySQL database in a VPC. The database must be accessible only from a specific set of application servers in the same VPC. Which configuration provides the most secure access?

A.Set the security group inbound rule to allow all traffic from the VPC CIDR

B.Place the RDS instance in a separate subnet group

C.Set the RDS instance to publicly accessible

D.Set the security group inbound rule to reference the security group of the application servers

AnswerD

Restricts access to resources with that security group.

Why this answer

Referencing the application servers' security group as the source in the RDS inbound rule allows traffic only from those specific instances, regardless of IP changes. This follows the AWS security best practice of using security group IDs for fine-grained, stateful access control within a VPC, eliminating reliance on static IP addresses or CIDR ranges.

Exam trap

The trap here is that candidates often confuse subnet placement (Option B) with access control, mistakenly thinking a separate subnet inherently restricts traffic, when in fact security groups are the primary mechanism for instance-level firewall rules in a VPC.

How to eliminate wrong answers

Option A is wrong because allowing all traffic from the VPC CIDR grants access to every resource in the VPC, including unauthorized instances or services, violating the principle of least privilege. Option B is wrong because placing the RDS instance in a separate subnet group does not restrict access; it only affects network segmentation and routing, not security group rules or connectivity. Option C is wrong because setting the RDS instance to publicly accessible assigns a public IP and opens it to the internet, which is insecure and contradicts the requirement for VPC-only access.

Practice this question →

39

MCQmedium

A company is migrating an on-premises PostgreSQL database to Amazon RDS for PostgreSQL. The database is 2 TB in size and has a high write workload. The company needs to minimize downtime during the migration. Which AWS service or feature should the company use to achieve this?

A.Use pg_dump and pg_restore to export and import the database.

B.Use AWS Database Migration Service (AWS DMS) with ongoing replication.

C.Use the AWS Schema Conversion Tool (AWS SCT) to convert the schema and migrate data.

D.Use AWS DataSync to replicate the database files.

AnswerB

AWS DMS supports ongoing replication via change data capture, minimizing downtime.

Why this answer

AWS DMS with ongoing replication (change data capture, CDC) is the correct choice because it allows continuous synchronization of the source PostgreSQL database with the target RDS for PostgreSQL instance after an initial full load. This minimizes downtime by enabling the target to stay up-to-date with changes until the cutover, which is critical for a 2 TB database with a high write workload.

Exam trap

The trap here is that candidates often confuse AWS DMS with AWS SCT, assuming SCT is needed for same-engine migrations, but SCT is only required for heterogeneous migrations, not for PostgreSQL to RDS PostgreSQL.

How to eliminate wrong answers

Option A is wrong because pg_dump and pg_restore are logical backup and restore tools that require the source database to be quiesced or taken offline during the export, causing significant downtime, and they do not support ongoing replication for a near-zero-downtime migration. Option C is wrong because AWS SCT is used for schema conversion when migrating between different database engines (e.g., Oracle to PostgreSQL), not for migrating within the same engine (PostgreSQL to RDS PostgreSQL), and it does not handle data migration or ongoing replication. Option D is wrong because AWS DataSync is designed for file-based data transfers (e.g., NFS, SMB) and cannot replicate live PostgreSQL database files or support transactional consistency and ongoing change capture for a relational database.

Practice this question →

40

MCQmedium

A company is migrating an on-premises Oracle database to Amazon RDS for Oracle. The database is 5 TB in size and has a daily change rate of 2%. The migration must have minimal downtime. Which migration strategy should be used?

A.Use AWS Schema Conversion Tool (SCT) to convert the schema, then use AWS DMS for full load only.

B.Create an RDS read replica in the same region and promote it.

C.Use AWS Database Migration Service (DMS) with ongoing replication from the source database.

D.Export the database to a dump file using Oracle Data Pump, upload to S3, and restore to RDS.

AnswerC

DMS with ongoing replication enables continuous sync and minimal downtime.

Why this answer

AWS DMS with ongoing replication (change data capture, CDC) allows a full load of the 5 TB database followed by continuous replication of the 2% daily changes, minimizing downtime by keeping the target RDS instance nearly synchronized until cutover. This approach handles large databases and high change rates without requiring a lengthy final export/import window.

Exam trap

The trap here is that candidates may confuse RDS read replicas (which are only for RDS-to-RDS replication) with cross-database replication, or assume that a full load plus manual catch-up is sufficient for minimal downtime, ignoring the need for continuous CDC to handle ongoing changes.

How to eliminate wrong answers

Option A is wrong because AWS SCT only converts schema, not data, and DMS full load alone would require a long downtime window to capture all changes after the load completes, failing to meet minimal downtime. Option B is wrong because RDS read replicas are only supported for RDS instances, not for on-premises Oracle databases, and cannot be created from an external source. Option D is wrong because exporting a 5 TB database with Oracle Data Pump, uploading to S3, and restoring to RDS would involve significant downtime for the export and restore processes, and does not provide ongoing replication to handle the 2% daily change rate with minimal interruption.

Practice this question →

41

MCQmedium

A company is migrating a 500 GB MySQL database from an on-premises server to Amazon RDS for MySQL. The company uses AWS DMS with ongoing replication. The initial full load completes successfully, and the target RDS instance is in sync. However, after a few hours, the replication task fails with an error: 'Last Error: Error executing source loop; The table 'orders' has a row size larger than the maximum payload size of the target endpoint.' The target RDS instance is configured with db.r5.large and the default parameter group. The company has already verified that the table does not have any BLOB or TEXT columns. What is the MOST likely cause of this error?

A.The DMS task is using a low-memory instance.

B.The source table has a row that exceeds the MySQL row size limit.

C.The target RDS instance's max_allowed_packet parameter is set too low.

D.The target RDS instance does not have enough storage allocated.

AnswerB

MySQL enforces a row size limit; DMS cannot insert rows exceeding it.

Why this answer

RDS for MySQL has a maximum row size limit (65,535 bytes). DMS attempts to insert a row that exceeds this limit. Increasing the instance size does not change the row size limit.

Using a different storage engine might help, but InnoDB is default. Enabling compression reduces row size but is not a direct solution for the DMS error.

Practice this question →

42

Multi-Selecthard

A company is migrating a 500 GB Oracle database to Amazon RDS for Oracle. They need to validate the migration and ensure data consistency. Which TWO methods should they use?

Select 2 answers

A.Use Amazon S3 inventory reports on the exported data.

B.Use AWS DMS data validation feature.

C.Run random SELECT queries on a subset of tables.

D.Compare row counts and checksums on both databases.

E.Use Amazon CloudWatch Logs to compare database logs.

AnswersB, D

DMS validation compares source and target data automatically.

Why this answer

AWS DMS data validation (Option B) is a built-in feature that automatically compares source and target records by computing checksums on each row, ensuring end-to-end data consistency without manual effort. Comparing row counts and checksums (Option D) is a standard manual validation technique that provides a reliable, independent verification of data completeness and integrity. Together, these two methods cover both automated and manual validation, which is critical for a 500 GB migration where manual inspection of every row is impractical.

Exam trap

The trap here is that candidates often choose Option C (random SELECT queries) thinking it is sufficient for validation, but the exam expects you to recognize that sampling is not statistically reliable for a 500 GB database and that AWS DMS provides a purpose-built, automated validation feature.

Practice this question →

43

MCQhard

A company is migrating a 3 TB Oracle database from on-premises to Amazon RDS for Oracle. The migration must have zero downtime. The on-premises server uses Oracle Data Guard for disaster recovery. The network bandwidth is 200 Mbps. The team plans to use AWS DMS with CDC from Oracle redo logs. During the initial full load, DMS reports that the source table 'ORDERS' has a table-level supplemental log missing. The migration fails. What should the team do first to resolve this issue?

A.Switch to Oracle GoldenGate for migration.

B.Use AWS SCT to convert the schema and then use a native export/import.

C.Enable supplemental logging on the Oracle source database for the 'ORDERS' table.

D.Recreate the DMS task with 'full load only' to bypass CDC.

AnswerC

Required for DMS CDC to capture changes.

Why this answer

AWS DMS requires supplemental logging on the source Oracle tables to capture change data for CDC. Without it, DMS cannot track changes. Option A is incorrect because switching to Oracle GoldenGate would not address the root cause and adds complexity.

Option B is incorrect because using AWS SCT and native export/import does not provide zero-downtime migration. Option D is incorrect because recreating the task with 'full load only' would lose the CDC requirement, causing downtime for ongoing changes.

Practice this question →

44

MCQeasy

A company is migrating an on-premises MySQL database to Amazon RDS for MySQL. The database uses InnoDB tables and is 500 GB in size. The migration must be completed within a 2-hour maintenance window. Which approach is MOST likely to meet the requirement?

A.Create a read replica of the on-premises database and promote it to RDS.

B.Use mysqldump to export the database and then import it into RDS.

C.Use AWS DMS with a full load task.

D.Take a physical backup of the data directory and copy it to RDS.

AnswerB

mysqldump with --single-transaction provides a consistent export without locking.

Why this answer

B is correct because mysqldump creates a logical backup that can be imported into Amazon RDS for MySQL within the 2-hour window for a 500 GB database, assuming sufficient network bandwidth and parallel import optimizations. The migration must complete within a fixed maintenance window, and mysqldump allows direct control over the export and import process, making it predictable for a single-shot migration.

Exam trap

The trap here is that candidates often choose AWS DMS (Option C) assuming it is the fastest migration tool, but for a one-time migration within a strict 2-hour window, mysqldump's simplicity and direct control often outperform DMS's overhead, especially when CDC is not required.

How to eliminate wrong answers

Option A is wrong because creating a read replica of an on-premises database and promoting it to RDS is not supported; MySQL read replicas require a source instance that is either an RDS instance or an external MySQL instance configured with binary log replication, but the promotion process does not apply to on-premises sources and would not complete within 2 hours due to initial sync overhead. Option C is wrong because AWS DMS with a full load task typically requires a change data capture (CDC) phase for ongoing replication, and the full load alone for 500 GB may exceed 2 hours depending on network throughput and target instance performance, plus DMS adds complexity and potential latency. Option D is wrong because taking a physical backup of the data directory (e.g., raw InnoDB files) and copying it to RDS is not supported; RDS does not allow direct file-level restoration of physical backups from on-premises, as it requires a compatible backup format like XtraBackup or mysqldump, and the copy would not be importable without additional conversion steps.

Practice this question →

45

MCQhard

A company is migrating a 500 GB Oracle database to Amazon Aurora PostgreSQL. They need to convert the schema and migrate the data. The application uses Oracle-specific features like hierarchical queries and stored procedures. Which combination of services should they use?

A.Use AWS Snowball Edge to transfer the database files and then use SCT to convert the schema.

B.Use AWS Schema Conversion Tool (SCT) to convert the schema and AWS Database Migration Service (DMS) to migrate the data.

C.Use AWS Database Migration Service (DMS) with the Oracle as source and Aurora PostgreSQL as target.

D.Use AWS Schema Conversion Tool (SCT) to convert the schema and then manually export/import data.

AnswerB

SCT converts the schema including Oracle-specific features, and DMS migrates the data efficiently.

Why this answer

AWS SCT converts Oracle-specific schema objects (including hierarchical queries and stored procedures) to PostgreSQL-compatible code, while AWS DMS handles the ongoing data migration with minimal downtime. This combination is the standard AWS approach for heterogeneous database migrations, as SCT addresses schema conversion and DMS handles data transfer.

Exam trap

The trap here is that candidates assume DMS alone can handle schema conversion, but DMS only migrates data and requires SCT for schema transformation, especially when Oracle-specific features like hierarchical queries are involved.

How to eliminate wrong answers

Option A is wrong because AWS Snowball Edge is designed for large-scale offline data transfer, not for schema conversion; SCT can convert the schema, but Snowball Edge does not facilitate the conversion process and is unnecessary for a 500 GB database. Option C is wrong because DMS alone cannot convert Oracle-specific schema features like hierarchical queries and stored procedures; it only migrates data, not schema objects. Option D is wrong because manually exporting/importing data is error-prone, time-consuming, and does not leverage DMS's ability to perform continuous replication or handle large volumes efficiently, making it unsuitable for a production migration.

Practice this question →

46

MCQhard

A company is deploying a globally distributed application that requires a low-latency, highly available database with multi-region write support. The application needs to handle conflicts automatically. Which AWS database solution meets these requirements?

A.Amazon Aurora Global Database

B.Amazon ElastiCache for Redis global datastore

C.Amazon DynamoDB global tables

D.Amazon RDS Multi-AZ with cross-region read replicas

AnswerC

DynamoDB global tables provide multi-region, multi-master writes with automatic conflict resolution.

Why this answer

Amazon DynamoDB global tables provide a fully managed, multi-region, multi-active database solution that automatically replicates data across AWS Regions, supports low-latency reads and writes from any region, and uses conflict resolution based on 'last writer wins' (LWW) with a timestamp vector clock. This meets the requirement for a globally distributed application needing automatic conflict handling without custom code.

Exam trap

The trap here is that candidates often confuse 'global database' (Aurora Global Database) with 'multi-region write support', not realizing Aurora Global Database is active-passive and cannot handle concurrent writes from multiple regions, while DynamoDB global tables are truly multi-active with built-in conflict resolution.

How to eliminate wrong answers

Option A is wrong because Amazon Aurora Global Database is designed for primary-secondary (active-passive) replication, not multi-region write support; writes can only occur in the primary region, and failover to a secondary region is manual or requires an RTO of minutes, not automatic conflict resolution. Option B is wrong because Amazon ElastiCache for Redis global datastore is an in-memory cache, not a durable database; it supports cross-region replication but does not provide automatic conflict resolution for writes, and data loss can occur on failover. Option D is wrong because Amazon RDS Multi-AZ with cross-region read replicas is an active-passive setup where writes are only allowed in the primary region; cross-region replicas are read-only and cannot handle multi-region writes or automatic conflict resolution.

Practice this question →

47

MCQmedium

A company is migrating an on-premises SQL Server database to Amazon RDS for SQL Server. They need to minimize downtime and have a limited network bandwidth of 50 Mbps. The database size is 1 TB. What is the MOST effective approach?

A.Use AWS DMS with CDC over the network.

B.Use AWS SCT to compress data before transfer.

C.Use AWS Snowball Edge to transfer initial load, then DMS for CDC.

D.Use native SQL Server backup and restore to Amazon S3.

AnswerC

Snowball accelerates initial transfer, CDC handles changes.

Why this answer

The 1 TB database size combined with a 50 Mbps network bandwidth would require over 46 hours for the initial load, making a full network transfer impractical. AWS Snowball Edge allows you to transfer the initial 1 TB seed data offline via a physical appliance, bypassing bandwidth constraints. After the seed is loaded into RDS, AWS DMS with Change Data Capture (CDC) can then replicate ongoing changes over the network, minimizing downtime to only the final cutover window.

Exam trap

The trap here is that candidates assume DMS with CDC alone can handle the full migration, underestimating the time required for the initial load over limited bandwidth, and overlook the offline seeding option provided by Snowball Edge.

How to eliminate wrong answers

Option A is wrong because using AWS DMS with CDC over the network for the full 1 TB initial load at 50 Mbps would take approximately 46+ hours, causing unacceptable downtime and risk of failure due to bandwidth limitations. Option B is wrong because AWS SCT compresses schema and code objects, not the actual data payload; it cannot compress the 1 TB database files for transfer, so it does not solve the bandwidth bottleneck. Option D is wrong because native SQL Server backup and restore to Amazon S3 requires uploading the full 1 TB backup file over the 50 Mbps network, which would take the same prohibitive amount of time as any other network-based approach, and it does not provide a CDC mechanism to minimize downtime.

Practice this question →

48

Multi-Selectmedium

A company is migrating an on-premises PostgreSQL database to Amazon RDS for PostgreSQL. The migration must have minimal downtime. Which TWO AWS services should be used together to achieve this?

Select 2 answers

A.AWS DataSync

B.AWS CloudEndure Migration

C.AWS Database Migration Service (AWS DMS)

D.AWS Direct Connect

E.AWS Schema Conversion Tool (AWS SCT)

AnswersC, E

DMS provides ongoing replication for minimal downtime.

Why this answer

AWS Database Migration Service (DMS) is used for the actual data migration with minimal downtime, supporting ongoing replication via change data capture (CDC) from the on-premises PostgreSQL database to Amazon RDS for PostgreSQL. AWS Schema Conversion Tool (SCT) is required to convert the source database schema and code to match the target RDS for PostgreSQL, identifying and resolving any compatibility issues. Together, SCT pre-processes the schema and DMS performs the data migration with replication, enabling a near-zero downtime migration.

Exam trap

The trap here is that candidates often confuse AWS DataSync or CloudEndure Migration as viable for database migration, but neither supports the logical replication and schema conversion required for minimal-downtime PostgreSQL to RDS migration, while DMS and SCT are the only services that directly address both schema conversion and ongoing data replication.

Practice this question →

49

MCQmedium

A company is migrating an on-premises PostgreSQL database to Amazon RDS for PostgreSQL. The database is 2 TB in size and has a sustained write rate of 50 MB/s. The migration must have minimal downtime. Which migration approach should be used?

A.Create an RDS read replica from the on-premises database

B.Use pg_dump and pg_restore

C.Use AWS DMS with a full-load task only

D.Use AWS DMS with ongoing replication (change data capture)

AnswerD

Ongoing replication allows minimal downtime by continuously synchronizing changes.

Why this answer

AWS DMS with ongoing replication (change data capture) is the correct approach because it allows a full load of the 2 TB database followed by continuous replication of changes from the on-premises PostgreSQL source to the RDS for PostgreSQL target, minimizing downtime to a brief cutover window. The sustained 50 MB/s write rate indicates a high-volume transactional workload that cannot be captured by a single full-load task, making CDC essential for near-zero downtime migration.

Exam trap

The trap here is that candidates often choose pg_dump/pg_restore (Option B) because they are familiar with it for smaller databases, but they fail to account for the downtime required by a 2 TB database with a high write rate, or they mistakenly think AWS DMS full-load (Option C) can handle ongoing writes without CDC.

How to eliminate wrong answers

Option A is wrong because RDS read replicas can only be created from an existing RDS DB instance, not from an on-premises database; they are a feature for scaling read traffic within AWS, not for migrating external databases. Option B is wrong because pg_dump and pg_restore are logical backup and restore tools that require the source database to be quiesced or taken offline during the dump, resulting in significant downtime for a 2 TB database with a 50 MB/s write rate. Option C is wrong because a full-load task only copies the current state of the database at the start of the task and does not capture ongoing changes, so any writes during the migration will be lost, leading to data inconsistency and extended downtime.

Practice this question →

50

Multi-Selecthard

A company is migrating a 500 GB Oracle database to Amazon Aurora PostgreSQL. Which THREE steps should be part of the migration plan?

Select 3 answers

A.Use AWS Snowball to transfer the database files.

B.Set up AWS Direct Connect between on-premises and AWS.

C.Use AWS DMS to perform a full load and ongoing replication from Oracle to Aurora.

D.Use AWS SCT to convert the Oracle schema to PostgreSQL-compatible schema.

E.Validate the migrated data and test the application against the new database.

AnswersC, D, E

DMS supports Oracle as source and Aurora PostgreSQL as target.

Why this answer

AWS DMS supports heterogeneous migrations from Oracle to Aurora PostgreSQL, performing a full load followed by ongoing change data capture (CDC) using Oracle's redo logs to replicate changes with minimal downtime. This makes it the correct service for both the initial data transfer and continuous replication during migration.

Exam trap

The trap here is that candidates confuse network connectivity tools (Direct Connect) or offline transfer methods (Snowball) with actual migration services, overlooking that DMS and SCT are the core services for heterogeneous database migrations, while Direct Connect is an optional optimization, not a required step.

Practice this question →

51

MCQeasy

A company is planning to deploy an Amazon RDS for PostgreSQL instance. Which of the following is a required step to enable automated backups?

A.Set the backup retention period to a value greater than 0.

B.Set a preferred maintenance window.

C.Enable encryption at rest.

D.Configure a Multi-AZ deployment.

AnswerA

Automated backups require a retention period > 0; default is 7 days.

Why this answer

Automated backups in Amazon RDS for PostgreSQL are enabled by setting a backup retention period greater than 0 days. By default, the retention period is 0, which disables automated backups. Once set to a value between 1 and 35 days, RDS automatically takes daily snapshots and retains transaction logs for point-in-time recovery within that window.

Exam trap

The trap here is that candidates often confuse enabling automated backups with configuring a maintenance window or Multi-AZ, but the only required step is setting the backup retention period to a non-zero value.

How to eliminate wrong answers

Option B is wrong because a preferred maintenance window is optional and only controls when system updates occur, not whether backups are enabled. Option C is wrong because encryption at rest is a security feature that protects data on disk but has no effect on backup configuration. Option D is wrong because Multi-AZ deployment provides high availability and automatic failover, but automated backups can be enabled independently of Multi-AZ.

Practice this question →

52

MCQhard

A company is migrating a 500 GB MySQL database to Amazon Aurora MySQL. The migration must have minimal downtime and the source database is already using binary logging. Which migration approach should be used?

A.Take a snapshot of the source database and restore to Aurora

B.Use AWS DMS with full load only

C.Set up binary log replication from the source to an Aurora MySQL cluster

D.Use mysqldump to export the data and import into Aurora

AnswerC

Binary log replication allows minimal downtime by continuously replicating changes.

Why this answer

MySQL native binary log replication can be set up directly from a source MySQL database to an Amazon Aurora MySQL cluster. Since binary logging is already enabled, the Aurora cluster can act as a replica, synchronizing continuously with minimal downtime. This approach allows a full load followed by ongoing replication, meeting the requirement for near-zero downtime migration.

Exam trap

The trap here is that candidates often choose mysqldump or snapshot because they are familiar backup methods, but they fail to recognize that these approaches require the source database to be offline or locked, which contradicts the minimal downtime requirement.

How to eliminate wrong answers

Option A is wrong because taking a snapshot of the source database and restoring to Aurora is a one-time, offline operation that requires the source to be stopped or locked, causing significant downtime. Option B is wrong because AWS DMS with full load only transfers the existing data but does not capture ongoing changes, so any writes during the migration would be lost, requiring an application downtime window. Option D is wrong because mysqldump exports data as SQL statements, which is a slow, single-threaded process that locks tables during export and requires the target to be offline during import, resulting in substantial downtime.

Practice this question →

53

MCQmedium

A company is migrating a 10 TB Oracle database to Amazon RDS for Oracle. The migration window is limited to 24 hours. The source database is running on-premises with a 500 Mbps network connection. Which migration approach should be used?

A.Use AWS DMS with full load and ongoing replication

B.Create an RDS read replica from the on-premises database

C.Take a physical backup of the source database and restore to RDS

D.Use Oracle Data Pump to export and import the database

AnswerA

DMS supports large data volumes and ongoing replication to minimize downtime.

Why this answer

AWS DMS with full load and ongoing replication is the correct approach because it can handle the 10 TB migration within the 24-hour window by using the 500 Mbps connection for the initial full load (which takes approximately 48 hours at full bandwidth, but DMS can compress data and use parallel tasks to reduce time), and then switch to ongoing replication to minimize downtime. The ongoing replication captures changes via Oracle LogMiner or binary logs, allowing the source to remain operational during the migration.

Exam trap

The trap here is that candidates often assume Oracle Data Pump or physical backups are faster for large databases, but they overlook the network bandwidth constraint and the need for ongoing replication to meet the 24-hour window, while DMS's ability to compress and replicate changes makes it the only viable option.

How to eliminate wrong answers

Option B is wrong because Amazon RDS for Oracle does not support creating a read replica from an on-premises database; read replicas are only available within RDS itself, typically for cross-Region or cross-AZ replication, not for external sources. Option C is wrong because taking a physical backup of the source database and restoring to RDS requires transferring the entire 10 TB backup file over the 500 Mbps link, which would take over 48 hours (10 TB * 8 / 500 Mbps = 160,000 seconds ≈ 44.4 hours) and exceed the 24-hour window, plus RDS does not support native physical restore from on-premises backups without additional tools like AWS Backup or S3. Option D is wrong because Oracle Data Pump export/import is a logical dump that would require transferring the entire 10 TB export file over the network, taking similar time as the physical backup, and does not support ongoing replication to minimize downtime, making it unsuitable for the tight 24-hour window.

Practice this question →

54

Multi-Selectmedium

A company is migrating a MySQL database to Amazon Aurora MySQL. The migration must be completed with minimal downtime. Which TWO methods can achieve this? (Choose two.)

Select 2 answers

A.Create an Aurora MySQL read replica from the external MySQL instance using binlog replication

B.Take a physical backup of the source database and restore to Aurora

C.Create an Aurora clone from the source database

D.Use AWS Database Migration Service (AWS DMS) with ongoing replication

E.Enable binlog replication on the source MySQL instance

AnswersA, D

This allows near-zero downtime replication.

Why this answer

You can set up an external MySQL instance as a replication source for an Amazon Aurora MySQL read replica using binary log (binlog) replication. This allows the Aurora cluster to stay synchronized with the source database with minimal downtime, as you only need to stop writes on the source and promote the Aurora replica when ready. Option D is correct because AWS Database Migration Service (AWS DMS) supports ongoing replication using change data capture (CDC) to keep the target Aurora database continuously synchronized with the source MySQL database, enabling a migration with minimal downtime.

Options B, C, and E are incorrect: taking a physical backup and restoring (B) or creating an Aurora clone from the source (C) would require downtime; enabling binlog replication alone (E) is not sufficient—it must be used with a replication setup or a service like DMS.

Exam trap

The trap here is that candidates may think enabling binlog replication alone (Option E) is sufficient for migration, but it is only a prerequisite; the actual migration requires a replication channel or a service like DMS to consume the binlog stream.

Practice this question →

55

MCQmedium

An administrator is deploying an Amazon RDS for MySQL DB instance and needs to ensure that all connections use SSL. Which parameter should be set on the RDS DB instance?

A.Set ssl_cipher in the DB parameter group

B.Set require_secure_transport=ON in the DB parameter group

C.Set tls_version in the DB parameter group

D.Set rds.force_ssl=1 in the DB parameter group

AnswerB

This parameter forces all connections to use SSL/TLS.

Why this answer

Setting `require_secure_transport=ON` in the DB parameter group enforces that all connections to the RDS MySQL DB instance must use SSL/TLS. This parameter, supported by MySQL 5.7 and later, rejects any non-encrypted connection attempt, ensuring transport layer security for all client-server communication.

Exam trap

The trap here is that candidates confuse `require_secure_transport` with `rds.force_ssl`, which is a valid parameter for RDS SQL Server but not for RDS MySQL, leading them to select the wrong option based on familiarity with other database engines.

How to eliminate wrong answers

Option A is wrong because `ssl_cipher` only specifies the allowed cipher suites for SSL connections but does not enforce that connections must use SSL; it allows non-SSL connections to proceed. Option C is wrong because `tls_version` controls the minimum TLS protocol version (e.g., TLS 1.2) but does not mandate that connections be encrypted; unencrypted connections are still permitted. Option D is wrong because `rds.force_ssl=1` is not a valid parameter for RDS MySQL; the correct parameter to enforce SSL is `require_secure_transport`, and `rds.force_ssl` is a parameter used in Amazon RDS for SQL Server, not MySQL.

Practice this question →

56

MCQmedium

A company is migrating a 2 TB MySQL database to Amazon Aurora MySQL. They need to minimize downtime and ensure data consistency. Which approach should be used?

A.Use AWS DMS with ongoing replication (CDC).

B.Use mysqldump to export and import into Aurora.

C.Establish AWS Direct Connect and use MySQL replication.

D.Use AWS SCT to convert schema and data.

AnswerA

DMS with CDC minimizes downtime by replicating changes.

Why this answer

AWS DMS with ongoing replication (CDC) is the correct approach because it allows you to perform an initial full load of the 2 TB database while continuously capturing and applying changes from the source MySQL database. This minimizes downtime by keeping the target Aurora MySQL cluster nearly synchronized, and you only need to stop writes briefly during the final cutover to ensure data consistency.

Exam trap

The trap here is that candidates often assume native MySQL replication (Option C) can be used directly with Aurora, but Aurora MySQL does not support standard MySQL replication as a replica; DMS is the AWS-native service designed for this purpose.

How to eliminate wrong answers

Option B is wrong because mysqldump creates a logical snapshot that requires the source database to be read-locked during the export, causing significant downtime for a 2 TB database, and it does not support ongoing replication to minimize cutover time. Option C is wrong because MySQL native replication to Aurora is not directly supported; Aurora MySQL uses a different storage engine and replication protocol, and establishing AWS Direct Connect alone does not solve the compatibility issue. Option D is wrong because AWS SCT is a schema conversion tool that helps convert database schemas and some data, but it does not provide ongoing replication or minimize downtime; it is typically used in conjunction with DMS for heterogeneous migrations, not for a homogeneous MySQL-to-Aurora migration.

Practice this question →

57

MCQeasy

A company is migrating an on-premises MySQL database to Amazon RDS for MySQL. The company wants to minimize application changes. Which endpoint type should the application use after migration?

A.RDS reader endpoint

B.RDS cluster endpoint

C.RDS instance endpoint (DNS name)

D.RDS console endpoint

AnswerC

Application connects to the RDS instance endpoint.

Why this answer

The RDS instance endpoint (DNS name) is the standard connection endpoint for a single RDS DB instance, which is the target of a direct migration from on-premises MySQL to Amazon RDS for MySQL. This endpoint requires no application changes, as the application simply replaces the old on-premises hostname with the RDS instance DNS name, maintaining the same MySQL protocol and connection logic.

Exam trap

The trap here is that candidates confuse RDS instance endpoints with Aurora cluster endpoints, mistakenly selecting the cluster endpoint (Option B) for a standard RDS MySQL migration, even though cluster endpoints are exclusive to Aurora and not applicable to single-instance RDS deployments.

How to eliminate wrong answers

Option A is wrong because the RDS reader endpoint is used only with Aurora clusters to distribute read traffic across read replicas; it is not available for standard RDS for MySQL instances and would cause connection failures if used. Option B is wrong because the RDS cluster endpoint is specific to Aurora DB clusters (for write operations) and does not exist for standard RDS for MySQL instances; using it would result in a DNS resolution error. Option D is wrong because the RDS console endpoint is not a valid database connection endpoint; it refers to the AWS Management Console URL for managing RDS resources, not a MySQL protocol endpoint.

Practice this question →

58

MCQhard

A company is planning to migrate a 5 TB Oracle data warehouse to Amazon Redshift. The migration must be completed within a 2-day maintenance window. The source database is heavily normalized and uses complex joins. Which strategy is most appropriate?

A.Use AWS DMS to directly migrate data to Redshift with full load and ongoing replication.

B.Export data to flat files, use S3 Transfer Acceleration to upload to S3, then COPY into Redshift.

C.Use AWS SCT to convert the Oracle schema to Redshift-compatible format, then use AWS DMS to load the data.

D.Use AWS Glue to crawl the Oracle schema and create Redshift tables, then run a Glue ETL job to load data.

AnswerC

AWS SCT converts Oracle’s normalised schema and complex joins into Redshift’s columnar, denormalised format, while AWS DMS performs the continuous 5 TB load within the 2-day window using full-load plus change data capture, satisfying the tight migration deadline.

Why this answer

AWS Schema Conversion Tool (SCT) is specifically designed to convert Oracle schemas (including heavily normalized structures with complex joins) into Amazon Redshift-compatible format, which is essential for a data warehouse migration. AWS DMS then efficiently loads the converted schema and data into Redshift within the 2-day window, as it can handle large volumes with full load and ongoing replication if needed.

Exam trap

The trap here is that candidates assume DMS alone can handle schema conversion, but DMS is a data migration service, not a schema transformation tool; SCT is required for converting complex Oracle schemas to Redshift-optimized formats.

How to eliminate wrong answers

Option A is wrong because AWS DMS cannot directly migrate a heavily normalized Oracle schema to Redshift without schema conversion; Redshift is a columnar data warehouse optimized for denormalized schemas, and DMS alone does not handle schema transformation for complex joins. Option B is wrong because exporting to flat files and using S3 Transfer Acceleration for a 5 TB migration within 2 days is feasible but lacks schema conversion; the heavily normalized schema with complex joins would not be optimized for Redshift, leading to poor query performance. Option D is wrong because AWS Glue can crawl and create tables, but it is not designed for schema conversion from Oracle to Redshift; it would require extensive custom ETL logic to handle the normalization and complex joins, making it inefficient for a time-constrained migration.

Practice this question →

59

MCQeasy

A company is migrating a 100 GB Microsoft SQL Server database from an on-premises data center to Amazon RDS for SQL Server. The migration uses AWS DMS with full load only (no ongoing replication). The full load completes successfully, but the company's application team reports that some data in the target database is missing. The source database was not modified during the migration. The DMS task logs show no errors. What is the MOST likely cause of the missing data?

A.The DMS task used the 'Change Data Capture' mode instead of full load.

B.The target RDS instance was not large enough to store all data.

C.The DMS task did not use transactional consistency.

D.The source database had foreign key constraints that were not migrated.

AnswerC

Without transactional consistency, DMS may not capture all changes in a consistent state.

Why this answer

DMS full load captures a snapshot of the source database. If the source database has active transactions during the snapshot, some changes may not be included. Using transactional consistency ensures a consistent snapshot.

Disabling foreign keys is not recommended. Using a larger instance does not affect consistency.

Practice this question →

60

Multi-Selecthard

A company is deploying a new application on AWS that requires a highly available relational database with automatic failover and read scaling. The database size is 100 GB and the workload is balanced between reads and writes. Which THREE AWS services or features should be used?

Select 3 answers

A.Multi-AZ deployment

B.DynamoDB Accelerator (DAX)

C.Amazon Aurora Replicas

D.Amazon Aurora

E.Amazon RDS Proxy

AnswersA, C, D

Aurora automatically replicates data across AZs, providing failover.

Why this answer

Multi-AZ deployment (Option A) is correct because it provides automatic failover for Amazon RDS by provisioning a synchronous standby replica in a different Availability Zone. If the primary DB instance fails, Amazon RDS automatically fails over to the standby, ensuring high availability without manual intervention. This directly meets the requirement for automatic failover in a relational database scenario.

Exam trap

The trap here is that candidates may confuse Amazon RDS Proxy with a high-availability or failover solution, but it only manages connections and does not replicate data or provide automatic failover.

Practice this question →

61

MCQmedium

A company is migrating a 2 TB PostgreSQL database from on-premises to Amazon RDS for PostgreSQL. The database has a 4-hour downtime window. The company requires minimal data loss and wants to use AWS DMS. The on-premises network has a 100 Mbps internet connection. Which migration method should the company use?

A.Use AWS Schema Conversion Tool (SCT) to migrate the data to Amazon RDS.

B.Use AWS DMS with a full load only, then stop the source database and resume applications.

C.Use pg_dump and pg_restore to export and import the database during the downtime window.

D.Use AWS DMS with a full load and ongoing change data capture (CDC) replication.

AnswerD

Full load plus CDC minimizes downtime by replicating changes continuously.

Why this answer

AWS DMS with a full load and ongoing change data capture (CDC) replication allows the company to migrate the 2 TB database with minimal data loss within the 4-hour downtime window. The full load transfers the existing data, and CDC captures and applies ongoing changes from the source database to the target RDS instance, reducing the final cutover downtime to seconds or minutes. This approach is ideal for large databases with tight downtime constraints and limited bandwidth (100 Mbps), as the initial full load can run before the downtime window, and only the final CDC catch-up occurs during the window.

Exam trap

The trap here is that candidates often assume pg_dump/pg_restore or a full-load-only DMS job can complete within the downtime window, ignoring the bandwidth calculation (2 TB at 100 Mbps = ~46 hours) and the need for minimal data loss, which only CDC can satisfy.

How to eliminate wrong answers

Option A is wrong because AWS Schema Conversion Tool (SCT) is used for converting database schemas from one engine to another (e.g., Oracle to PostgreSQL), not for migrating data to the same engine; it also does not handle data migration itself. Option B is wrong because using AWS DMS with a full load only would require stopping the source database during the entire data transfer, which would exceed the 4-hour downtime window given the 2 TB size and 100 Mbps bandwidth (approximately 46 hours for full load). Option C is wrong because pg_dump and pg_restore are native PostgreSQL tools that require the source database to be stopped or in read-only mode during the entire export/import process, which would not complete within the 4-hour window due to the large data volume and bandwidth limitation.

Practice this question →

62

MCQhard

A company has an Amazon RDS for MySQL database with Multi-AZ deployment. The database is experiencing high CPU utilization due to a reporting workload. The company wants to migrate to Amazon Aurora MySQL to improve performance and scalability. The migration must have minimal downtime. Which migration strategy meets these requirements?

A.Create an Aurora MySQL replica from the RDS MySQL instance and promote it

B.Take a snapshot of the RDS instance and restore it to an Aurora cluster

C.Migrate to a larger RDS MySQL instance to handle the workload

D.Use AWS DMS with full load and ongoing replication

AnswerA

This allows minimal downtime and uses native replication.

Why this answer

Creating an Aurora MySQL replica from an existing RDS MySQL instance uses the native MySQL replication protocol to perform an online migration with minimal downtime. Once the replica is fully synchronized, you can promote it to become a standalone Aurora cluster, which provides better performance and scalability for the reporting workload.

Exam trap

The trap here is that candidates often assume AWS DMS is the only way to achieve minimal downtime, but the native Aurora replica feature provides a simpler and faster migration path with even lower downtime when the source engine is compatible.

How to eliminate wrong answers

Option B is wrong because taking a snapshot of the RDS instance and restoring it to an Aurora cluster is an offline migration method that requires the source database to be unavailable during the snapshot process, leading to significant downtime. Option C is wrong because it does not migrate to Aurora at all; it only scales the existing RDS instance vertically, which does not address the requirement to migrate to Aurora MySQL for improved performance and scalability. Option D is wrong because while AWS DMS with full load and ongoing replication can achieve minimal downtime, it is more complex and slower to set up compared to creating an Aurora replica, and the question specifically asks for the strategy that meets the requirements with minimal downtime, making the native Aurora replica approach the most straightforward.

Practice this question →

63

MCQeasy

A company wants to test an application against an Amazon RDS for MySQL database with a recent set of production data without impacting the production database. The test database must be available quickly and be refreshed regularly. Which solution should be used?

A.Export production data to S3 and import into a test instance using Lambda.

B.Create a read replica of the production database, then promote it to a standalone instance for testing.

C.Use AWS DMS to continuously replicate data from production to a test RDS instance.

D.Create a snapshot of the production database and restore it as a new RDS instance.

AnswerB

A read replica can be promoted quickly and refreshed by creating a new replica.

Why this answer

Creating a read replica of the production RDS for MySQL database and then promoting it to a standalone instance is the fastest way to obtain a near-current copy of production data without impacting the source. The replica is created asynchronously using MySQL's native binlog replication, and promotion breaks the replication link, leaving a fully writable test instance. This approach minimizes setup time because the replica is already hydrated with data from the moment of creation.

Exam trap

The trap here is that candidates often choose snapshot restore (Option D) because it seems like the most straightforward backup method, but they overlook that a read replica can be promoted to a standalone instance much faster and with less operational overhead for regular refreshes.

How to eliminate wrong answers

Option A is wrong because exporting production data to S3 and importing via Lambda introduces significant latency and complexity; it is not the quickest method and requires custom scripting, whereas RDS read replicas are a managed, one-click solution. Option C is wrong because AWS DMS continuous replication is designed for ongoing migration or synchronization, not for creating an immediate, point-in-time test copy; it adds overhead and is slower to set up than a read replica. Option D is wrong because creating a snapshot and restoring it as a new RDS instance takes longer than promoting a read replica, as snapshots are point-in-time backups that must be fully restored before the instance is available, whereas a read replica is already running and can be promoted in minutes.

Practice this question →

64

MCQmedium

A company is migrating a database using AWS DMS. The IAM policy shown is attached to the DMS replication instance role. When the DMS replication task is created in the us-west-2 region, it fails. What is the most likely cause?

A.The IAM policy does not allow the 'dms:CreateReplicationTask' action.

B.The IAM policy does not specify the VPC where the replication instance is deployed.

C.The IAM policy does not specify the resource ARN for the replication instance.

D.The IAM policy restricts the region to us-east-1, but the task is created in us-west-2.

AnswerD

The condition 'aws:RequestedRegion' restricts to us-east-1 only.

Why this answer

The IAM policy explicitly restricts the region to us-east-1 using the `aws:RequestedRegion` condition key. When the DMS replication task is created in us-west-2, the policy denies the `dms:CreateReplicationTask` action because the region condition fails, causing the task creation to fail. DMS replication tasks require the IAM role to have permissions in the same region where the task is being created.

Exam trap

The trap here is that candidates often overlook the `Condition` block with `aws:RequestedRegion` and focus only on the Action and Resource fields, assuming a missing action or resource ARN is the cause, when the real issue is a regional restriction enforced by the condition key.

How to eliminate wrong answers

Option A is wrong because the policy includes `dms:CreateReplicationTask` in the Action list, so the action is allowed; the failure is due to the region condition, not a missing action. Option B is wrong because DMS replication instances are associated with a VPC via subnet groups, not by specifying the VPC in the IAM policy; the IAM policy does not need to specify the VPC. Option C is wrong because the policy uses a wildcard `*` for the Resource, which covers all DMS resources including the replication instance; the issue is the region condition, not the resource ARN.

Practice this question →

65

Multi-Selectmedium

A company is migrating a MySQL database to Amazon RDS for MySQL. They want to use AWS DMS for continuous replication. Which TWO prerequisites must be met before starting the migration?

Select 2 answers

A.Enable binary logging (binlog) on the source MySQL database.

B.Ensure the DMS replication instance has network connectivity to the source and target databases.

C.Set the source database to read-only mode during migration.

D.Place the source database in a VPC.

E.Create an S3 bucket to store the migration logs.

AnswersA, B

Binary logging is necessary for DMS to capture ongoing changes.

Why this answer

AWS DMS uses MySQL's binary log (binlog) to capture ongoing changes for continuous replication (CDC). Enabling binlog on the source database is mandatory because DMS reads the binlog to identify insert, update, and delete operations after the initial full load. Without binlog enabled, DMS cannot perform change data capture and the migration will be limited to a one-time full load only.

Exam trap

The trap here is that candidates often assume the source must be read-only during migration (Option C), but DMS supports live migration with zero downtime by using CDC, so read-only mode is only needed for certain homogenous migrations or final cutover phases, not as a general prerequisite.

Practice this question →

66

MCQmedium

A company is migrating a 2 TB Oracle database from on-premises to Amazon RDS for Oracle. The network bandwidth is 100 Mbps. The migration must be completed within 3 days. Which approach is MOST efficient?

A.Use AWS DMS with parallel load and ongoing replication.

B.Use Oracle RMAN to create a backup and restore to RDS.

C.Use Oracle Data Pump with a single export and import.

D.Use Oracle GoldenGate for real-time replication.

AnswerA

DMS parallel load reduces migration time.

Why this answer

AWS DMS with parallel load and ongoing replication is the most efficient approach because it can handle the 2 TB migration within the 3-day window over a 100 Mbps link. At 100 Mbps, the theoretical maximum transfer is about 1.08 TB per day (100 Mbps * 86400 seconds / 8 bits per byte / 1024^4), so 2 TB would take nearly 2 days just for the full load. DMS's parallel load splits the data into multiple tasks, maximizing throughput and reducing the full-load time, while ongoing replication captures changes during the migration, allowing a seamless cutover without downtime.

Exam trap

The trap here is that candidates often assume Oracle-native tools like RMAN or Data Pump are always the best for migrations, but they overlook the bandwidth constraint and RDS's lack of direct OS access, making DMS the only viable option for a time-bound, large-scale migration with minimal downtime.

How to eliminate wrong answers

Option B is wrong because Oracle RMAN cannot be used to directly restore a backup to Amazon RDS for Oracle; RDS does not provide access to the underlying file system or allow RMAN restore operations, and the backup would need to be converted or migrated via other tools. Option C is wrong because Oracle Data Pump with a single export and import would be too slow for a 2 TB database over 100 Mbps, as a single-threaded export/import cannot saturate the bandwidth and would likely exceed the 3-day window, especially with network overhead. Option D is wrong because Oracle GoldenGate is designed for real-time replication and continuous synchronization, which is overkill for a one-time migration and adds unnecessary complexity and cost; it is better suited for ongoing replication scenarios, not for a time-bound full load.

Practice this question →

67

MCQmedium

A company is migrating an on-premises Oracle database to Amazon RDS for Oracle. The database is 1 TB and has a large number of stored procedures and triggers. The migration must minimize application changes. Which migration approach should be used?

A.Use AWS Schema Conversion Tool (AWS SCT) to convert the schema and AWS DMS for data migration

B.Use AWS Database Migration Service (AWS DMS) with full load and ongoing replication

C.Use Oracle Data Pump (expdp/impdp) to export and import the database

D.Use AWS S3 to store the data and AWS Glue to transform and load into RDS

AnswerB

AWS DMS supports ongoing replication to minimize downtime.

Why this answer

AWS DMS with full load and ongoing replication minimizes application changes by supporting heterogeneous migrations with minimal downtime, and it can handle stored procedures and triggers by replicating data changes in near real-time without requiring schema conversion. AWS DMS directly supports Oracle as a source and Amazon RDS for Oracle as a target, preserving the existing schema and procedural logic, which avoids the need for application rewrites.

Exam trap

The trap here is that candidates often assume AWS SCT is required for any Oracle migration, but SCT is only needed when changing database engines; for a homogeneous migration to RDS for Oracle, DMS alone suffices, and using SCT would introduce unnecessary schema conversion risks.

How to eliminate wrong answers

Option A is wrong because AWS SCT is designed for schema conversion when migrating to a different database engine (e.g., Oracle to Aurora PostgreSQL), but the question specifies migrating to Amazon RDS for Oracle, which uses the same engine, so schema conversion is unnecessary and would introduce unnecessary complexity. Option C is wrong because Oracle Data Pump (expdp/impdp) is a logical export/import tool that requires significant downtime for a 1 TB database and does not provide ongoing replication, making it unsuitable for minimizing application changes during a live migration. Option D is wrong because AWS S3 and AWS Glue are ETL services for data transformation and loading, not designed for database migration with minimal application changes; they would require schema redesign and cannot natively handle Oracle stored procedures and triggers.

Practice this question →

68

MCQmedium

A company is migrating a 2 TB Oracle database to Amazon Aurora PostgreSQL. The migration must have minimal downtime and support ongoing replication. Which AWS service should be used?

A.AWS DataSync

B.Amazon S3 Glacier

C.AWS Database Migration Service (AWS DMS)

D.AWS Schema Conversion Tool (AWS SCT)

AnswerC

DMS supports heterogeneous migrations and ongoing replication from Oracle to Aurora.

Why this answer

AWS Database Migration Service (AWS DMS) is the correct choice because it supports ongoing replication (change data capture, CDC) from an Oracle source to an Amazon Aurora PostgreSQL target, enabling a migration with minimal downtime. DMS can handle a 2 TB database by using a large replication instance and tuning task settings, and it continuously replicates changes until the cutover is complete.

Exam trap

The trap here is that candidates often confuse AWS SCT (schema conversion) with the actual data migration, or they assume DataSync can handle database replication, but DMS is the only service that provides both schema conversion (via SCT integration) and ongoing data replication for heterogeneous migrations.

How to eliminate wrong answers

Option A is wrong because AWS DataSync is designed for transferring large datasets over the network or between on-premises storage and AWS storage services (e.g., S3, EFS, FSx), but it does not support ongoing replication or heterogeneous database migrations like Oracle to Aurora PostgreSQL. Option B is wrong because Amazon S3 Glacier is a cold storage service for archival data, not a migration tool; it cannot perform live database replication or schema conversion. Option D is wrong because AWS Schema Conversion Tool (AWS SCT) is used to convert the source database schema and code to a target-compatible format, but it does not perform the actual data migration or ongoing replication; SCT is typically used in conjunction with DMS, not as a standalone migration service.

Practice this question →

69

Multi-Selectmedium

A company is migrating an on-premises PostgreSQL database to Amazon RDS for PostgreSQL. They need to minimize downtime and ensure data consistency. Which TWO methods can be used together to achieve this?

Select 2 answers

A.Take a file system snapshot and copy to Amazon EBS

B.Use pg_dump and pg_restore

C.Use AWS DMS with full load and CDC

D.Export data to Amazon S3 and import using COPY

E.Set up pglogical replication from on-premises to RDS

AnswersC, E

DMS can replicate data continuously.

Why this answer

AWS DMS with full load and Change Data Capture (CDC) enables a zero-downtime migration by first copying the existing data (full load) and then continuously replicating ongoing changes from the on-premises PostgreSQL source to the Amazon RDS for PostgreSQL target. This ensures data consistency because CDC captures transactions in near real-time using the PostgreSQL logical replication slot mechanism, allowing the target to stay synchronized until the cutover.

Exam trap

The trap here is that candidates often think pg_dump/restore (Option B) is sufficient for minimal downtime, but they overlook that it requires a consistent snapshot and cannot capture ongoing changes, whereas the correct answer combines a full load with CDC to achieve near-zero downtime.

Practice this question →

70

MCQmedium

A company is migrating an on-premises MongoDB database to Amazon DocumentDB. They need to ensure that the migration is completed with minimal downtime and that data remains consistent. Which tool should they use?

A.Use AWS DMS with MongoDB as source and DocumentDB as target

B.Use mongoexport and mongoimport

C.Export data to Amazon S3 and load into DocumentDB

D.Use MongoDB Atlas Live Migration

AnswerA

DMS supports continuous replication for MongoDB.

Why this answer

AWS DMS supports continuous change data capture (CDC) from MongoDB to Amazon DocumentDB, enabling near-zero downtime migration by replicating ongoing changes after the initial full load. This ensures data consistency without requiring application downtime, unlike batch export/import methods.

Exam trap

The trap here is that candidates may confuse MongoDB Atlas Live Migration (which is specific to Atlas) with a general-purpose migration tool, or assume that offline tools like mongoexport are sufficient for minimal downtime scenarios.

How to eliminate wrong answers

Option B is wrong because mongoexport and mongoimport are offline, batch tools that require stopping writes to the source database, causing significant downtime and lacking CDC for ongoing changes. Option C is wrong because exporting to S3 and loading into DocumentDB is a manual, offline process that does not support continuous replication, leading to data inconsistency if writes continue during migration. Option D is wrong because MongoDB Atlas Live Migration is a tool for migrating to MongoDB Atlas, not to Amazon DocumentDB, and is not compatible with DocumentDB's API or infrastructure.

Practice this question →

71

MCQhard

Refer to the exhibit. A database administrator is trying to use AWS DMS to migrate data from an on-premises Oracle database to Amazon RDS for Oracle. The DMS replication instance is in the same VPC as the RDS instance. The administrator receives an access denied error when starting the replication task. The IAM policy attached to the DMS replication instance is shown. What is the MOST likely cause of the error?

A.The IAM policy does not include permissions for the source database endpoint

B.The IAM policy does not allow the dms:CreateReplicationInstance action

C.The RDS instance is not in the same VPC as the DMS replication instance

D.The DMS replication instance is not associated with the IAM role

AnswerA

DMS needs permissions to create and test endpoints, which are missing.

Why this answer

The error occurs because the IAM policy attached to the DMS replication instance does not include the necessary permissions to access the source Oracle database endpoint. Specifically, the policy lacks actions like `dms:TestConnection` and `dms:DescribeEndpoints` that are required for DMS to validate and connect to the source endpoint. Without these permissions, DMS cannot establish the connection to the on-premises Oracle database, resulting in an access denied error when starting the replication task.

Exam trap

The trap here is that candidates often assume the error is due to network connectivity (Option C) or role association (Option D), but the exhibit clearly shows the IAM policy is missing source endpoint permissions, which is a common misconfiguration in DMS migrations.

How to eliminate wrong answers

Option B is wrong because the error occurs during the replication task start, not during the creation of the replication instance; the `dms:CreateReplicationInstance` action is only needed when provisioning the instance, and the task start failure is unrelated to that permission. Option C is wrong because the question explicitly states the DMS replication instance is in the same VPC as the RDS instance, so a VPC mismatch is not the cause. Option D is wrong because the IAM policy is attached to the replication instance (as shown in the exhibit), meaning the role is associated; the issue is the policy's insufficient permissions, not the lack of association.

Practice this question →

72

MCQmedium

A company is deploying a MySQL database on Amazon RDS and needs to enforce encryption at rest. Which configuration step is required?

A.Use a custom DB parameter group with SSL enabled.

B.Modify the DB instance to enable encryption after creation.

C.Enable SSL/TLS on the RDS instance.

D.Select encryption option when creating the RDS instance.

AnswerD

Encryption at rest is enabled at launch.

Why this answer

Amazon RDS for MySQL requires encryption at rest to be enabled at instance creation time by selecting the encryption option in the AWS Management Console, CLI, or API. Encryption at rest uses AWS Key Management Service (KMS) to encrypt the underlying storage, automated backups, read replicas, and snapshots. This setting cannot be applied to an existing unencrypted DB instance, so it must be chosen during the initial launch.

Exam trap

The trap here is that candidates confuse encryption at rest with encryption in transit (SSL/TLS), leading them to select options that enable SSL rather than the required storage-level encryption.

How to eliminate wrong answers

Option A is wrong because a custom DB parameter group with SSL enabled controls in-transit encryption (SSL/TLS connections), not encryption at rest. Option B is wrong because Amazon RDS does not support enabling encryption at rest on an existing unencrypted DB instance; you must migrate data to a new encrypted instance. Option C is wrong because enabling SSL/TLS on the RDS instance enforces encryption in transit between clients and the database, not encryption of data at rest on the storage volume.

Practice this question →

73

MCQmedium

A company is deploying a new application with a PostgreSQL database on Amazon RDS. The database must be highly available across two Availability Zones. Which deployment option meets this requirement?

A.RDS with a read replica in another AZ.

B.Multi-AZ RDS instance.

C.Single-AZ RDS instance.

D.Amazon Aurora Global Database.

AnswerB

Provides automatic failover to a standby in another AZ.

Why this answer

A Multi-AZ RDS instance automatically provisions and maintains a synchronous standby replica in a different Availability Zone, providing automatic failover for high availability. This ensures the database remains accessible even if the primary AZ fails, meeting the requirement for cross-AZ high availability.

Exam trap

The trap here is that candidates often confuse read replicas with Multi-AZ deployments, assuming a read replica in another AZ provides high availability, but it lacks automatic failover and synchronous replication required for true HA.

How to eliminate wrong answers

Option A is wrong because a read replica is designed for read scaling, not high availability; it requires manual promotion to become the primary and does not provide automatic failover. Option C is wrong because a Single-AZ RDS instance runs in only one Availability Zone, offering no redundancy or automatic failover if that AZ fails. Option D is wrong because Amazon Aurora Global Database is designed for global disaster recovery across multiple AWS regions, not for high availability within a single region across two AZs; it adds complexity and cost beyond the stated requirement.

Practice this question →

74

Multi-Selecteasy

A company is migrating a 2 TB MySQL database to Amazon Aurora MySQL. They want to minimize downtime and ensure data consistency. Which TWO methods should they use? (Choose two.)

Select 2 answers

A.Use AWS DMS with ongoing replication

B.Use AWS Schema Conversion Tool to convert the schema

C.Use AWS Snowball Edge to transfer backup files

D.Enable binary logging on the source database for change data capture

E.Use mysqldump to export data

AnswersA, D

Minimizes downtime with CDC.

Why this answer

AWS DMS with ongoing replication (Option A) is correct because it allows continuous change data capture (CDC) from the source MySQL database to the target Aurora MySQL cluster, minimizing downtime by keeping the target synchronized during the migration. This approach ensures data consistency by applying incremental changes after the initial full load, enabling a controlled cutover with minimal service interruption.

Exam trap

The trap here is that candidates often think mysqldump or Snowball are viable for minimizing downtime, but they fail to recognize that these methods require taking the source offline or introduce significant latency, whereas DMS with binary logging enables near-zero downtime through continuous replication.

Practice this question →

75

MCQhard

A company is migrating a self-managed PostgreSQL database with extensions (PostGIS, pg_stat_statements) to Amazon RDS for PostgreSQL. After migration, they find that the extensions are not available. What is the most likely cause?

A.The required extensions are not included in the default parameter group and must be manually added to shared_preload_libraries.

B.The extensions are incompatible with the RDS engine version.

C.The RDS instance is not configured to allow extensions.

D.RDS does not support any PostgreSQL extensions.

AnswerA

Extensions need to be enabled via parameter group.

Why this answer

Amazon RDS for PostgreSQL does not automatically load extensions that require shared library preloading, such as pg_stat_statements. These extensions must be explicitly added to the `shared_preload_libraries` parameter in the DB parameter group. PostGIS, while not requiring preloading, must be created via `CREATE EXTENSION` after the extension files are present; however, the most likely cause of extensions not being available is that the custom parameter group was not configured to include the required libraries in `shared_preload_libraries`.

Exam trap

The trap here is that candidates assume extensions are automatically available after migration, overlooking that certain extensions require explicit parameter group configuration and a reboot to load the shared library.

How to eliminate wrong answers

Option B is wrong because both PostGIS and pg_stat_statements are fully supported by Amazon RDS for PostgreSQL on compatible engine versions; incompatibility is not the typical cause. Option C is wrong because RDS does not have a blanket 'allow extensions' toggle; extensions are controlled via parameter groups and permissions, not a single instance-level setting. Option D is wrong because RDS for PostgreSQL supports many extensions, including PostGIS and pg_stat_statements, as documented in the AWS RDS user guide.

Practice this question →

Page 1 of 5 · 341 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Deployment and Migration questions.

Start 20-question session