Discuss Amazon ANS-C01 Exam Topic 1 Question 7

A company is planning to create a service that requires encryption in transit. The traffic must not be decrypted between the client and the backend of the service. The company will implement the service by using the gRPC protocol over TCP port 443. The service will scale up to thousands of simultaneous connections. The backend of the service will be hosted on an Amazon Elastic Kubernetes Service (Amazon EKS) duster with the Kubernetes Cluster Autoscaler and the Horizontal Pod Autoscaler configured. The company needs to use mutual TLS for two-way authentication between the client and the backend.

Which solution will meet these requirements?

AInstall the AWS Load Balancer Controller for Kubernetes. Using that controller, configure a Network Load Balancer with a TCP listener on port 443 to forward traffic to the IP addresses of the backend service Pods.

BInstall the AWS Load Balancer Controller for Kubernetes. Using that controller, configure an Application Load Balancer with an HTTPS listener on port 443 to forward traffic to the IP addresses of the backend service Pods.

CCreate a target group. Add the EKS managed node group's Auto Scaling group as a target Create an Application Load Balancer with an HTTPS listener on port 443 to forward traffic to the target group.

DCreate a target group. Add the EKS managed node group's Auto Scaling group as a target. Create a Network Load Balancer with a TLS listener on port 443 to forward traffic to the target group.

Suggested Answer: B

Get Premium ANS-C01 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

42 comments · newest first

Ligia 11 months ago

D looks good for scaling with the target group setup!

Olene 12 months ago

Wait, can a Network Load Balancer even handle mutual TLS?

Louvenia 12 months ago

Mutual TLS? Definitely need an Application Load Balancer for that!

Sheron 1 year ago

I think A is better for TCP connections.

Stanford 1 year ago

Option B seems solid for HTTPS traffic.

Tammara 1 year ago

I feel like the Network Load Balancer might be the right choice since it can handle TCP traffic directly, but I need to double-check the requirements for mutual TLS.

Nilsa 1 year ago

I'm a bit confused about whether we need a TCP listener or an HTTPS listener for this setup. Does mutual TLS require specific configurations?

Emerson 1 year ago

I think we practiced a similar question about load balancers in our last session, and I recall that the Application Load Balancer is more suited for HTTPS traffic.

Tiera 1 year ago

I remember studying the differences between Network Load Balancers and Application Load Balancers, but I'm not sure which one is better for mutual TLS.

Hester 1 year ago

I'm a bit unsure about some of the options here. I'll need to review my notes on composite sensors to make sure I don't miss anything important in my answer.

Odette 1 year ago

This question seems familiar; I think we discussed how overhead allocation can impact profitability. I need to double-check my calculations to see which profit figures make the most sense here.

Stevie 1 year ago

I'm pretty sure we discussed how observing sudden changes in lifestyle, like Elizabeth's purchases, could warrant further investigation.

Herminia 1 year ago

I feel like Cisco's security approach applies to multiple types of networks, maybe all of them? Like, isn't it supposed to be comprehensive?

Jesusita 1 year ago

From what I recall, High task; High relationship definitely involves coaching and support. I think that's the correct choice!

Valentin 1 year ago

Wait, is this a trick question? What if the answer is actually a combination of options, like a Network Load Balancer with an HTTPS listener and an Application Load Balancer for the backend? Hmm, better think this through again.

Yong 1 year ago

↳ replying to Valentin

Erasmo: Let's carefully review the requirements and options before making a decision.

Lindsey 1 year ago

↳ replying to Valentin

User 3: That could work, we need to make sure the traffic is secure and encrypted.

Erasmo 1 year ago

↳ replying to Valentin

User 2: Maybe we should consider using both a Network Load Balancer and an Application Load Balancer.

Casey 1 year ago

↳ replying to Valentin

User 1: I think the answer might be a combination of options.

Florinda 1 year ago

I'm a big fan of the Network Load Balancer, so I'm leaning towards option D as well. Gotta love those TLS listeners!

Josephine 1 year ago

↳ replying to Florinda

Definitely, option D provides the encryption needed for secure communication between the client and backend.

Amalia 1 year ago

↳ replying to Florinda

I agree, Network Load Balancer with a TLS listener seems like the best choice for this scenario.

Aleta 1 year ago

↳ replying to Florinda

Option D sounds like the way to go. TLS listeners are great for encryption.

Johanna 1 year ago

Haha, I bet the person who wrote this question loves to see us struggle with the differences between ALB and NLB. But I'm going with option D - a Network Load Balancer with a TLS listener seems like the right fit.

Farrah 1 year ago

↳ replying to Johanna

Definitely, using mutual TLS for two-way authentication is crucial for security in this scenario.

Novella 1 year ago

↳ replying to Johanna

Yeah, I think so too. It's important to make sure the traffic remains encrypted between the client and backend.

Carli 1 year ago

↳ replying to Johanna

I agree, option D with a Network Load Balancer and TLS listener seems like the best choice.

Wilbert 2 years ago

This is a tricky one. I'm not sure about the performance implications of using an Application Load Balancer versus a Network Load Balancer. Let me think this through a bit more.

Socorro 1 year ago

↳ replying to Wilbert

D) Mutual TLS might work better with a Network Load Balancer. Consider that option as well.

Bernadine 1 year ago

↳ replying to Wilbert

C) Create a target group. Add the EKS managed node group's Auto Scaling group as a target. Create an Application Load Balancer with an HTTPS listener on port 443 to forward traffic to the target group.

Serita 1 year ago

↳ replying to Wilbert

B) I think using a Network Load Balancer might be more suitable for this scenario.

Brianne 1 year ago

↳ replying to Wilbert

A) Install the AWS Load Balancer Controller for Kubernetes. Using that controller, configure a Network Load Balancer with a TCP listener on port 443 to forward traffic to the IP addresses of the backend service Pods.

Shawnna 1 year ago

↳ replying to Wilbert

D: True, but we also need to consider the mutual TLS authentication requirement.

Johnetta 1 year ago

↳ replying to Wilbert

C: But option C with an Application Load Balancer might provide more features for HTTPS traffic.

Cletus 1 year ago

↳ replying to Wilbert

B: I agree, Network Load Balancer could handle the traffic better.

Nichelle 1 year ago

↳ replying to Wilbert

B: I agree, that seems like the best choice for our requirements.

Rosendo 1 year ago

↳ replying to Wilbert

A: I think option A with a Network Load Balancer might be better for performance.

Dylan 1 year ago

↳ replying to Wilbert

A: I think we should go with option A and use a Network Load Balancer.

Jamal 2 years ago

But option C also seems viable, it utilizes an Application Load Balancer with an HTTPS listener and adds the EKS managed node group's Auto Scaling group as a target.

Iraida 2 years ago

Hmm, this seems straightforward. I think option B is the way to go - using an Application Load Balancer with an HTTPS listener to handle the mutual TLS requirement.

Elza 2 years ago

I disagree, I believe option B is better as it uses an Application Load Balancer with an HTTPS listener for secure communication.

Jamal 2 years ago

I think option A is the best solution because it uses a Network Load Balancer with a TCP listener on port 443.

Amazon ANS-C01 Exam - Topic 1 Question 7 Discussion