Error spoted in Section-Based – Migration Planning (SA-Professional)

[claude]

Hi, here s the question

A multinational consumer goods company is currently using a VMWare vCenter Server to manage their virtual machines, multiple ESXi hosts, and all dependent components from a single centralized location. To save costs and to avail the benefits of cloud computing, the company decided to move their virtual machines to AWS.

Which of the following should you do to implement the cloud migration? (Choose 2)

and here are the proposed answers :

Establish a Direct Connect connection between your data center and your VPC. Use AWS Service Catalog to centrally manage all your IT services and to quickly migrate virtual machines to your virtual private cloud.

Both the IAM policy and the SCP are the problem The SCP should explicitly allow S3 bucket creation in its policy and the IAM policy should explicitly match the resources of the SCP.

Use Serverless Application Model (SAM) to migrate the virtual machines (VMs) to AWS and automatically launch an Amazon ECS Cluster to host the VMs.

Install the Server Migration Connector to your on-premises virtualization environment.

Use the AWS Server Migration Service (SMS).

I know that some answers are pure distractors, but this one looks really lost here.

Claude.

[claude]

other (small) error spotted : 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.

proposed answers :

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.

in explanations :

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

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.

the last wrong answer is not in the proposed answer, and looks correct to me.

Claude.

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

[claude]

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, 10 months ago by  claude.

[TutorialsDojo-Support]

– 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.

Hi claude,

Thank you for your feedback.

The option “Launch and configure a Classic Load Balancer with ports set to HTTP:80 and HTTP:8080.” may be correct on certain scenarios but on this particular question, the application only supports TCP protocol which is not the same as the standard HTTP protocol. So you need to configure your Classic Load Balancer accordingly to support TCP connections.

In this case, you need to “Launch and configure a Classic Load Balancer with instance protocols set to TCP:80 and TCP:8080. “

Hope this helps.

Regards,

Kenneth Samonte @ Tutorials Dojo

[claude]

agreed but here the explanation is based on an answer that does not belong to the proposed ones.

Claude

[TutorialsDojo-Support]

Hi Claude,

I’m sorry I’m a bit confused, what do you mean by “the explanation is based on an answer that does not belong to the proposed ones.”?

I’ve read through the question and the explanation looks accurate to me. Can you elaborate on which part is not clear so we can review it and revise if needed.

Explanation:

In Elastic Load Balancing, you must configure one or more listeners for your Classic Load Balancer. A listener is a process that checks for connection requests. It is configured with a protocol and a port for front-end (client to load balancer) connections, and a protocol and a port for back-end (load balancer to back-end instance) connections.

Elastic Load Balancing supports the following protocols: HTTP, HTTPS (secure HTTP), TCP and SSL (secure TCP).

https://i.udemycdn.com/redactor/raw/2020-01-27_11-57-06-c21cca2ed04ccc9203d941a4fa84c578.png

The HTTPS protocol uses the SSL protocol to establish secure connections over the HTTP layer. You can also use the SSL protocol to establish secure connections over the TCP layer. If the front-end connection uses TCP or SSL then your back-end connections can use either TCP or SSL. If the front-end connection uses HTTP or HTTPS then your back-end connections can use either HTTP or HTTPS.

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.

Regards,

Kenneth Samonte @ Tutorials Dojo

[claude]

Hi, yes I agree, quiete confusing but please carefully read

proposed answers :

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

2/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.

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

4/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.

in the correction we have

correct : Launch and configure a Classic Load Balancer with instance protocols set to TCP:80 and TCP:8080 = matches 3/

incorrect

– 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 matches 4/

– 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 matches 2/

– Launch and configure a Classic Load Balancer with ports set to HTTP:80 and HTTP:8080 should match 1/ ? maybe this is the confusing part for me.

Claude.

[TutorialsDojo-Support]

Hi Claude,

“proposed answers :

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

– Launch and configure a Classic Load Balancer with ports set to HTTP:80 and HTTP:8080 should match 1/ ? maybe this is the confusing part for me.”

I’ve updated the option on the to change it to instance protocol to prevent confusion. The original wording makes it look like the Classic LB listener is HTTP, which can be correct in some scenarios.

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

Thanks and Regards,

Kenneth Samonte @ Tutorials Dojo

[claude]

Thanks, for the reply. Sorry for the -so long dicussion- for a -so small issue- my goal was not to point at little issues in your system but to contribute to make better if I could.

You re doing an amazing job!

C.

[TutorialsDojo-Support]

Hi claude,

Thanks for the feedback.

I tried searching for the choices: “Both the IAM policy and the SCP are the problem The SCP should explicitly allow S3 bucket creation in its policy and the IAM policy should explicitly match the resources of the SCP.” on my question bank and it seems this option is no longer present.

I think this question is already updated. If you see it on your exam today, maybe on the next batch of updates the revision will be applied and this option will be swapped with another more related option.

Regards,

Kenneth Samonte @ Tutorials Dojo

[TutorialsDojo-Support]

Hi claude,

Thanks for the feedback.

I tried searching for the choices: “Both the IAM policy and the SCP are the problem The SCP should explicitly allow S3 bucket creation in its policy and the IAM policy should explicitly match the resources of the SCP.” on my question bank and it seems this option is no longer present.

I think this question is already updated. If you see it on your exam today, maybe on the next batch of updates the revision will be applied and this option will be swapped with another more related option.

Regards,

Kenneth Samonte @ Tutorials Dojo