New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft AZ-305 Exam - Topic 3 Question 65 Discussion

Actual exam question for Microsoft's AZ-305 exam
Question #: 65
Topic #: 3
[All AZ-305 Questions]

You have an Azure Functions microservice app named Appl that is hosted in the Consumption plan. App1 uses an Azure Queue Storage trigger.

You plan to migrate App1 to an Azure Kubernetes Service (AKS) cluster.

You need to prepare the AKS cluster to support Appl. The solution must meet the following requirements:

* Use the same scaling mechanism as the current deployment.

* Support kubenet and Azure Container Netwoking Interface (CNI) networking.

Which two actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct answer is worth one point.

Show Suggested Answer Hide Answer
Suggested Answer: A, D, D

by Daniel at Sep 08, 2024, 11:12 AM

Limited Time Offer

25%

Off

Get Premium AZ-305 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Lili
3 months ago
I thought the virtual node add-on was only for specific scenarios?
upvoted 0 times
...
Lenny
3 months ago
A and C are definitely the right moves here!
upvoted 0 times
...
Breana
3 months ago
Wait, KEDA? Isn't that overkill for a simple queue trigger?
upvoted 0 times
...
Salome
4 months ago
I think B is a good option too, but not sure about D.
upvoted 0 times
...
Brittney
4 months ago
Gotta go with A and C for scaling!
upvoted 0 times
...
Peggy
4 months ago
KEDA was mentioned in a practice question, and it seems relevant for event-driven scenarios. I wonder if it’s necessary for this migration, though.
upvoted 0 times
...
Mitsue
4 months ago
I’m a bit confused about the difference between the virtual node add-on and the virtual kubelet. I feel like I need to review that part again.
upvoted 0 times
...
Cecil
4 months ago
I think the AKS cluster autoscaler is also important for managing resources, especially since we need to mimic the current scaling mechanism.
upvoted 0 times
...
Joni
5 months ago
I remember we talked about the horizontal pod autoscaler in class. It seems like it could be a good fit for scaling, but I'm not entirely sure if it's the only option.
upvoted 0 times
...
Stanford
5 months ago
I'm feeling pretty confident about this one. The requirements are clear, and I think a combination of configuring the horizontal pod autoscaler and the virtual node add-on should do the trick.
upvoted 0 times
...
Shalon
5 months ago
Ah, I see. The virtual node add-on could also be a good choice since it allows us to support both kubenet and Azure CNI networking. I'll make sure to consider that as well.
upvoted 0 times
...
Leonor
5 months ago
Okay, the key is that we need to support the same scaling mechanism as the current deployment, which is using an Azure Queue Storage trigger. So I'm thinking the Kubernetes-based Event Driven Autoscaling (KEDA) option might be the way to go.
upvoted 0 times
...
Mitsue
5 months ago
Hmm, I'm a bit unsure about the difference between the horizontal pod autoscaler and the AKS cluster autoscaler. I'll need to review those concepts to make sure I understand which one is more appropriate here.
upvoted 0 times
...
Paola
5 months ago
This question seems straightforward. I think I'll start by looking at the requirements and considering which options best meet them.
upvoted 0 times
...
Clay
1 year ago
I believe installing the virtual node add-on is also necessary for networking support.
upvoted 0 times
...
Titus
1 year ago
I heard the Kubernetes team is working on a new feature called 'Kubernetes-based Extreme Daenerys Autoscaling' - it scales your pods based on the number of dragons you have. Very effective, but a bit hard to control.
upvoted 0 times
Lea
1 year ago
Yeah, I'll focus on configuring the horizontal pod autoscaler and the AKS cluster autoscaler for now.
upvoted 0 times
...
Sheridan
1 year ago
You should probably stick to the standard scaling mechanisms for now.
upvoted 0 times
...
Cherri
1 year ago
That sounds interesting, but I don't think I need dragons for my microservice app.
upvoted 0 times
...
...
Starr
1 year ago
We also need to configure the AKS cluster autoscaler for proper scaling.
upvoted 0 times
...
Douglass
1 year ago
I agree with Tequila, that will help with scaling.
upvoted 0 times
...
Judy
1 year ago
I'm pretty sure the answer is A and C. The question specifically mentions scaling requirements, so we need to configure the horizontal pod autoscaler and the AKS cluster autoscaler to meet those needs.
upvoted 0 times
Merilyn
1 year ago
Agreed. Configuring both will ensure the scaling mechanism is in place for the migration.
upvoted 0 times
...
Lemuel
1 year ago
That makes sense. Those two actions should prepare the AKS cluster for the migration.
upvoted 0 times
...
Rosalind
1 year ago
Yes, and we also need to configure the AKS cluster autoscaler to support scaling as well.
upvoted 0 times
...
Goldie
1 year ago
I think you're right. We should configure the horizontal pod autoscaler for scaling.
upvoted 0 times
...
...
Vanna
1 year ago
This is a trick question, the answer is obviously E. KEDA is the way to go, it's the coolest sounding option. Who needs boring old autoscaling when you can have Kubernetes-based Event Driven Autoscaling!
upvoted 0 times
Cyril
1 year ago
You're both wrong. The correct answers are C) Configure the AKS cluster autoscaler and D) Configure the virtual node add-on.
upvoted 0 times
...
Winifred
1 year ago
No, I believe the correct answers are D) Configure the virtual node add-on and E) Install Kubemetes-based Event Driven Autoscaling (KEDA).
upvoted 0 times
...
Charlene
1 year ago
I think the answer is A) Configure the horizontal pod autoscaler.
upvoted 0 times
...
...
Tequila
1 year ago
I think we should configure the horizontal pod autoscaler.
upvoted 0 times
...
Florinda
1 year ago
Haha, I'm just going to guess and say B and D. Virtual Kubelet and the virtual node add-on sound like they might be the right answers, even though I have no idea what they actually do.
upvoted 0 times
...
Kandis
1 year ago
I think the answer is A and C. We need to configure the horizontal pod autoscaler to handle scaling based on the same mechanism as the current deployment, and also configure the AKS cluster autoscaler to handle the scaling of the cluster nodes.
upvoted 0 times
Markus
1 year ago
Yes, and we also need to configure the AKS cluster autoscaler to support the scaling of the cluster nodes.
upvoted 0 times
...
Glennis
1 year ago
I agree with you, we definitely need to configure the horizontal pod autoscaler for scaling.
upvoted 0 times
...
...

Save Cancel