MENU
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.
Suggested Answer: A, D, D
Get Premium AZ-305 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
35 comments · newest first
LI
Lili
11 months ago
I thought the virtual node add-on was only for specific scenarios?
LE
Lenny
11 months ago
A and C are definitely the right moves here!
BR
Breana
11 months ago
Wait, KEDA? Isn't that overkill for a simple queue trigger?
SA
Salome
12 months ago
I think B is a good option too, but not sure about D.
BR
Brittney
12 months ago
Gotta go with A and C for scaling!
PE
Peggy
1 year 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.
MI
Mitsue
1 year 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.
CE
Cecil
1 year ago
I think the AKS cluster autoscaler is also important for managing resources, especially since we need to mimic the current scaling mechanism.
JO
Joni
1 year 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.
ST
Stanford
1 year 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.
SH
Shalon
1 year 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.
LE
Leonor
1 year 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.
MI
Mitsue
1 year 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.
PA
Paola
1 year ago
This question seems straightforward. I think I'll start by looking at the requirements and considering which options best meet them.
CL
Clay
2 years ago
I believe installing the virtual node add-on is also necessary for networking support.
TI
Titus
2 years 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.
LE
Lea
2 years ago
Yeah, I'll focus on configuring the horizontal pod autoscaler and the AKS cluster autoscaler for now.
SH
Sheridan
2 years ago
You should probably stick to the standard scaling mechanisms for now.
CH
Cherri
2 years ago
That sounds interesting, but I don't think I need dragons for my microservice app.
ST
Starr
2 years ago
We also need to configure the AKS cluster autoscaler for proper scaling.
DO
Douglass
2 years ago
I agree with Tequila, that will help with scaling.
JU
Judy
2 years 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.
ME
Merilyn
2 years ago
Agreed. Configuring both will ensure the scaling mechanism is in place for the migration.
LE
Lemuel
2 years ago
That makes sense. Those two actions should prepare the AKS cluster for the migration.
RO
Rosalind
2 years ago
Yes, and we also need to configure the AKS cluster autoscaler to support scaling as well.
GO
Goldie
2 years ago
I think you're right. We should configure the horizontal pod autoscaler for scaling.
VA
Vanna
2 years 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!
CY
Cyril
2 years ago
You're both wrong. The correct answers are C) Configure the AKS cluster autoscaler and D) Configure the virtual node add-on.
WI
Winifred
2 years ago
No, I believe the correct answers are D) Configure the virtual node add-on and E) Install Kubemetes-based Event Driven Autoscaling (KEDA).
CH
Charlene
2 years ago
I think the answer is A) Configure the horizontal pod autoscaler.
TE
Tequila
2 years ago
I think we should configure the horizontal pod autoscaler.
FL
Florinda
2 years 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.
KA
Kandis
2 years 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.
MA
Markus
2 years ago
Yes, and we also need to configure the AKS cluster autoscaler to support the scaling of the cluster nodes.
GL
Glennis
2 years ago
I agree with you, we definitely need to configure the horizontal pod autoscaler for scaling.