Explanation:
The correct approach is to set the min_idle_instances property in the app.yaml file, as this ensures a specified number of instances are always running and ready to serve traffic, which is crucial for handling sudden load spikes. This method is effective for priming your application for rapid increases in request volume, though it's important to note that these instances incur charges regardless of traffic. Options A and D are incorrect because manual scaling does not guarantee minimal running instances. Option B is not suitable as min_instances pertains to dynamic scaling and does not ensure idle instances are available for burst traffic.
Ultimate access to all questions.
No comments yet.
Your company's marketing application is currently running on App Engine with Autoscaling and performing well. With a massive marketing campaign on the horizon, the team anticipates significant burst traffic. What step should you take to ensure there are always 3 idle instances ready to handle the surge?
A
Switch to manual scaling and enable the burst_traffic_protection property in the app.yaml file.
B
Adjust the min_instances property in the app.yaml file to manage dynamic scaling.
C
Specify the min_idle_instances property in the app.yaml file to maintain a minimum number of idle instances.
D
Opt for manual scaling and set the idle_instance_count property in the app.yaml file.