Azgomi is a community application that facilitates communication between people in close proximity, used for event planning and organizing sporting events, and for businesses to connect with their local communities. Azgomi's unique style of hyper-local community communication and business outreach is in demand around the world. The executive statement is to expand the number one local community app globally. The solution concept is to expand their existing service in new regions to better serve their global customers, and hire and train a new team to support these regions in their time zones. Azgomi wants to ensure the application scales smoothly and provides clear uptime data, and that they analyze and respond to any issues that occur. Their existing technical environment is a mix of on-premises hardware and infrastructure running in Google Cloud Platform.

Azgomi's investors want to expand their footprint and support the increase in demand they are seeing. They require the application to expand availability to new regions, support 10x as many concurrent users, ensure a consistent experience for users when they travel to different regions, obtain user activity metrics to better monetize their product, ensure compliance with regulations in new regions, reduce infrastructure management time and cost, and adopt Google-recommended practices for cloud computing. The technical requirements include providing secure communications between the on-premises data center and cloud-hosted applications and infrastructure, providing usage metrics and monitoring, requiring authentication and authorization for APIs, implementing faster and more accurate validation of new features, providing actionable information for logging and performance metrics, and scaling to meet user demand.

A recent security audit discovered that Azgomi's database credentials for their Compute Engine-hosted MySQL databases are stored in plain text on persistent disks. Azgomi needs to reduce the risk of these credentials being stolen.

What actions do you suggest for them?

An API is being developed for use in Android and iOS apps.

What kind of API architecture would be suitable for an API that needs to support HTTPs, minimize bandwidth cost, and integrate easily with mobile apps?

You are planning to deploy your application in a Google Kubernetes Engine (GKE) cluster. Your application can scale horizontally, and each instance of your application needs to have a stable network identity and its own persistent disk. Which GKE object should you use?

Your application will be deployed on a Compute Engine instance that will communicate with Cloud SQL. In order to allow communication between the application and the database using the service account associated with the instance, you will use Cloud SQL Proxy. It is recommended by Google to provide minimum access for the role assigned to the service account, which you intend to follow as a best practice.

What actions do you recommend taking?

The task at hand is to create a microservice-based application on Google Kubernetes Engine (GKE). The application requires access to various Google Cloud APIs. Two of these services must be able to access these APIs.

What is the recommended approach for implementing authentication of these services in the cluster according to Google's best practices?