Find answers, ask questions, and connect with our
community around the world.

Home Forums AWS AWS Certified Database – Specialty Similiar options and incorrect fact in one of the question

  • Similiar options and incorrect fact in one of the question

  • monteroete

    Member
    January 10, 2022 at 6:33 pm

    <div>Hi Jon,</div><div>

    There seems to be an error in one of the possible answer in the following question. Both option 1 and 4 are identical. The correct question from the system is 4.

    I understand that one of these two options are meant to “misled” the candidate. But SCT does not do the migration, the DMS task defined in SCT does.

    Best regards,

    Kenny

    </div><div>

    35. Question

    Category: DBS – Deployment and Migration

    A retail company plans to migrate a 90 TB on-premises data warehouse from its data center to an Amazon Redshift cluster using AWS Schema Conversion Tool (AWS SCT) and AWS Database Migration Service (AWS DMS). The company’s Database Specialist intends to use Amazon S3 as the data lake. The migration has a limited maintenance window of two weeks and should keep the encryption settings (both at-rest and in-transit). However, the network bandwidth of the site is 500Mbps.

    Which approach is most likely to succeed in migrating the data with the least risk involved?

    1. Order two AWS Snowball Edge Compute Optimized devices. Use AWS SCT to move the data to the AWS Snowball Edge devices with a Local & DMS task.
    In turn, AWS Snowball Edge devices will move the data to Amazon S3 with
    encryption enabled. AWS SCT will finally migrate the data from the
    Amazon S3 bucket to Amazon Redshift.

    2. Configure an encryption-enabled VPN solution to connect the data center
    network to AWS. Use AWS SCT to convert the schema to Amazon Redshift and
    create an AWS DMS task to migrate the data from the original data
    warehouse to Amazon S3. Load data from Amazon S3 to Amazon Redshift
    using AWS Glue.

    3. Configure an encryption-enabled VPN solution to connect the data center
    network to AWS. Use the data warehouse’s native export tools to backup
    the data. Perform a multipart upload to move the data to Amazon S3 with
    AWS KMS encryption. Load data from Amazon S3 to Amazon Redshift using
    AWS Glue.

    4. Order two AWS Snowball Edge Storage Optimized devices. Use AWS SCT to move the data to the AWS Snowball Edge devices with a Local & DMS task.
    In turn, AWS Snowball Edge devices will move the data to Amazon S3 with
    encryption enabled. AWS SCT will finally migrate the data from the
    Amazon S3 bucket to Amazon Redshift.

    </div><div>

    </div>

  • Joboy-Pineda-TD

    Member
    January 10, 2022 at 8:20 pm

    Dear Kenny,

    Thanks for your query. However, #1 and #4 are not similar (first sentence). While #1 recommends to use AWS Snowball Edge Compute Optimized devices, #4 recommends to use AWS Snowball Edge Storage Optimized devices instead. In this scenario, due to the storage requirements, two Storage Optimized devices, which can store 80 TB each, meets the solution.

    <font face=”inherit”>It is also not intended to mislead you because of two points: 1) AWS Snowball Edge devices work specifically with AWS SCT, and 2) the choice stated the AWS SCT’s Local and DMS task option to give acknowledgement that</font> the DMS subtask will move the data without needing to be too explicit and make the choice unnecessarily wordy.

    The link below may help you with more details:

    https://docs.aws.amazon.com/dms/latest/userguide/CHAP_LargeDBs.html

    I hope this clarifies the situation.

    Best, Joboy

  • monteroete

    Member
    January 10, 2022 at 8:34 pm

    Hi Joboy,

    Thank you for the clarification.

    My mistake, I have misread the names of the 2 Snowball Option.

    Best regards,

    Kenny

    • Joboy-Pineda-TD

      Member
      January 13, 2022 at 6:15 pm

      Hi Kenny,

      No prob. Feel free to ask if you have other concerns. Happy to help!

      Joboy

Viewing 1 - 3 of 3 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now