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

Home Forums AWS AWS Certified Solutions Architect Professional Error spoted in Section-Based – Migration Planning (SA-Professional) Reply To: Error spoted in Section-Based – Migration Planning (SA-Professional)

  • claude

    Member
    June 28, 2020 at 11:36 pm

    Other small error spotted : Section-Based – Migration Planning (SA-Professional)

    You are working in a major robotics company as a Cloud Engineer, and the team is migrating all of the web applications hosted on the on-premises network to the AWS cloud. However, some of these apps only support TCP, which means that they will only work on ports 80 and 8080. Your manager also requires you to use an ELB and Auto Scaling to ensure that the traffic is routed properly and ensure scalability of the application.

    In this scenario, which listener configuration would you create on the ELB?

    The ELB and instance protocol will be configured to ports HTTP:80 and HTTP:8080.

    Launch and configure an Application Load Balancer with ports HTTP:80 and HTTP:8080 with instance protocols set to TCP:80 and TCP:8080 respectively.

    Launch and configure a Classic Load Balancer with instance protocols set to TCP:80 and TCP:8080.

    Launch and configure an Application Load Balancer with ports HTTP:80 and HTTP:8080, while the instance protocols are set to HTTPS:80 and HTTPS:8080 respectively.

    Hence, the option that says: Launch and configure a Classic Load Balancer with instance protocols set to TCP:80 and TCP:8080 is correct because for the ELB to route the traffic correctly, it should be configured with ports TCP:80 and TCP 8080. For the backends as well, the ports that should be configured must be TCP:80 an TCP:8080.

    The following options are all incorrect as both the ELB and instance protocol must be configured for ports TCP:80 and TCP:8080:

    – Launch and configure an Application Load Balancer with ports HTTP:80 and HTTP:8080, while the instance protocols are set to HTTPS:80 and HTTPS:8080 respectively

    – Launch and configure an Application Load Balancer with ports HTTP:80 and HTTP:8080 with instance protocols set to TCP:80 and TCP:8080 respectively

    – Launch and configure a Classic Load Balancer with ports set to HTTP:80 and HTTP:8080.


    last wrong answer does not belong to the proposed answer and looks very correct.

    Claude


    • This reply was modified 3 years, 11 months ago by  claude.