Ends in
00
days
00
hrs
00
mins
00
secs
SHOP NOW

ALL AWS Specialty Practice Exams for only $17.99 $13.99 each!

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

Home Forums AWS AWS Certified Solutions Architect Associate VPC Peering and Fault Tolerance

  • VPC Peering and Fault Tolerance

  • SeanB

    Member
    December 29, 2022 at 2:01 am

    Regarding the question and answer below, i want to make sure i am understanding this correctly.

    Test Question:

    A media company has two VPCs: VPC-1 and VPC-2 with peering connection between each other. VPC-1 only contains private subnets while VPC-2 only contains public subnets. The company uses a single AWS Direct Connect connection and a virtual interface to connect their on-premises network with VPC-1.

    Which of the following options increase the fault tolerance of the connection to VPC-1? (Select TWO.)

    Test Answer:

    – Establish a hardware VPN over the Internet between the VPC and the on-premises network.

    – Establish another AWS Direct Connect connection and private virtual interface in the same AWS region.

    My Question 1: To increase fault tolerance to on premise we are creating a second connection from VPC 1 to on premise and that is done with a hardware VPN, is that correct?

    My Question 2: Then a second connection from VPC 1 to VPC 2 is used to provide fault tolerance and that is done using direct connect? Why did the correct answer not say Establish another AWS Direct Connect connection and private virtual interface between VPC1 and <b style=”font-style: italic;”>VPC 2.” instead of Establish another AWS Direct Connect connection and private virtual interface in the same AWS region.” Assuming that since the direct connect can only be established between two VPCs that it is assumed it is between VPC1 and VPC2?

    • This discussion was modified 1 year, 5 months ago by  SeanB.
  • SeanB

    Member
    December 29, 2022 at 2:03 am

    test

Viewing 1 - 2 of 2 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now