A new service was deployed on a shared host. The log shows recurring memory trouble, and platform monitoring indicates the system is near its capacity. Which option fixes this situation most effectively?
Use an older product variant that relies on fewer features
Limit overall memory usage across all workloads to a standard setting
Wait for users to experience more crashes, then add extra capacity
Increase allocated resources or place the workload on a more capable host
Allocating additional capacity or migrating the service to a suitable host prevents crashes by providing sufficient memory. Reducing available memory globally does not eliminate local stress on the service, and scaling later risks ongoing failures. Deploying a legacy release removes functionality rather than solving the root cause of resource constraints.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What does 'allocating additional capacity' mean in this context?
Open an interactive chat with Bash
What type of monitoring tools can help prevent resource constraints in shared hosts?
Open an interactive chat with Bash
Why is migrating to a legacy release a poor solution?