MULESOFT-PLATFORM-ARCHITECT-I practice question 18 of 25

A customer has an ELA contract with MuleSoft. An API deployed to CloudHub is consistently experiencing performance issues. Based on the root cause analysis, it is determined that autoscaling needs to be applied. How can this be achieved?

Full set: 152 questions

Domain Delivering and Managing APIs

Answer options
A: Configure a policy so that when the number of HTTP requests reaches a certain threshold the number of workers/replicas increases (horizontal scaling)
B: Configure two separate policies: When CPU and memory reach certain threshold, increase the worker/replica type (vertical sealing) and the number of workers/replicas (horizontal sealing)
C: Configure a policy based on CPU usage so that CloudHub auto-adjusts the number of workers/replicas (horizontal scaling) Correct answer
D: Configure a policy so that when the response time reaches a certain threshold the worker/replica type increases (vertical scaling)
Correct Answer:
C. Configure a policy based on CPU usage so that CloudHub auto-adjusts the number of workers/replicas (horizontal scaling)
Explanation

CloudHub autoscaling is designed to automatically adjust the number of workers (horizontal scaling) allocated to an application to maintain performance under fluctuating loads. This is achieved by configuring policies that monitor specific metrics. The supported metrics for triggering an autoscaling event are CPU utilization and memory utilization. When the configured threshold for CPU (or memory) is breached for a specified duration, the policy triggers an action to either add or remove workers, ensuring the application has adequate resources without manual intervention. This is a feature available to customers with an Enterprise License Agreement (ELA).

Why Incorrect

A. CloudHub autoscaling policies are triggered by CPU or memory usage, not by the number of HTTP requests.
B. CloudHub autoscaling only performs horizontal scaling (adjusting the number of workers), not automatic vertical scaling (changing worker size).
D. Autoscaling policies are not triggered by application response time, and they do not perform automatic vertical scaling.

References

1. MuleSoft Documentation, "Autoscaling": "Autoscaling enables you to configure your application to automatically scale up or down the number of workers based on the CPU or memory usage of your application’s workers." This section explicitly states that the triggers are CPU and memory usage and the action is adjusting the number of workers.

Source: MuleSoft Docs, Runtime Manager > CloudHub > Autoscaling.

2. MuleSoft Documentation, "Manage Applications on CloudHub": This document details the manual process of configuring worker size (vCores) and the number of workers during deployment or redeployment. It clarifies that changing the worker size (vertical scaling) is a manual configuration setting, not an automated action performed by a policy.

Source: MuleSoft Docs, Runtime Manager > CloudHub > Manage Applications on CloudHub > "Configure an Application in CloudHub".

Scroll to Top