Explanation:
Given HipLocal's need for a serverless architecture to facilitate elastic scaling and their .NET-based auth service's intermittent load issues, the best solution is to use App Engine. App Engine provides a fully managed environment that supports .NET Core, enabling automatic scaling without the need for infrastructure management. This aligns with HipLocal's technical requirements and Google-recommended practices for cloud computing. Cloud Functions, while serverless, is more suited for event-driven workloads rather than a full auth service. Compute Engine options would require manual scaling and management, which does not meet the requirement for elastic scaling or reduce infrastructure management time and cost.
Ultimate access to all questions.
No comments yet.
HipLocal's .NET-based authentication service experiences failures under intermittent load. What solution should they implement?
Correction Notes:
A
Use App Engine for autoscaling.
B
Use Cloud Functions for autoscaling.
C
Use a Compute Engine cluster for the service.
D
Use a dedicated Compute Engine virtual machine instance for the service.