Ends in
00
days
00
hrs
00
mins
00
secs
SHOP NOW

🚀 25% OFF All Practice Exams, Video Courses, & eBooks – Cyber Sale Extension!

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

Home Forums Azure AZ104 review mode set 4 question 52 incorrect answer or explanation

  • AZ104 review mode set 4 question 52 incorrect answer or explanation

     Neil-TutorialsDojo updated 1 week, 6 days ago 2 Members · 4 Posts
  • jshurak

    Member
    November 23, 2024 at 1:19 am

    Scenario 2’s answer or explanation is incorrect. The initial instance count is 3 and the minimum instance count is 2. Since the scale down value will bring the instance count below the minimum it would not occur. The correct answer should be 3 not 2.

  • Neil-TutorialsDojo

    Member
    November 25, 2024 at 11:16 am

    Hello jshurak,

    Good day!

    Thank you for reaching out to us. To provide you with the most accurate and helpful support, could you please share the specific snippet of the question you’re referring to? Thank you.

    Regards,

    Neil @ Tutorials Dojo

  • jshurak

    Member
    November 28, 2024 at 7:53 pm

    Hello, I’ve just gotten back to that question. Here is the issue. In the first picture you can see that the initial instance count is 3. In scenario 2, the high workload is not enough to trigger a scale out. The workload then drops down to below the scale in threshold. While the minimum instance count is 2, the current instance count is 3 as nothing has occurred to change that.

    The second screenshot shows the explanation of the answer. It is correct in its explanation except it is incorrect on the current number of vms running. It explains that the initial instance count is 2….that is incorrect, it is 3 as per the question description.

  • Neil-TutorialsDojo

    Member
    November 29, 2024 at 10:17 am

    Hello jshurak,

    Good day!

    Thank you once again for posting here.

    To clarify, the “minimum instance count of 2” mentioned in the explanation refers to the “Minimum number of VMs: 2” specified in the scenario and NOT the “Initial instance count: 3” (as seen in the provided images).

    Here’s a detailed breakdown of the scenario:

    Scenario 2: Initial state: 3 VMs First condition: 70% CPU for 8 minutes (no action taken as duration is less than 10 minutes) Second condition: 15% CPU for 12 minutes Scale In Policy: If CPU < 20%, decrease by 2 VMs

    In this scenario, the scale-in condition is met (CPU < 20% for more than 10 minutes). Therefore, 2 VMs will be removed from the initial 3 VMs. However, the minimum number of VMs is set to 2, so the scale set cannot go below this number.

    Result: 3 (initial) – 1 (scaled in, limited by minimum) = 2 VMs

    I hope this clears up any confusion. We appreciate your feedback, as it helps us improve our content and explanations.

    Best regards,
    Neil @ Tutorials Dojo

Viewing 1 - 4 of 4 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now
Skip to content