Answer-first summary for fast verification
Answer: Use your existing CI/CD pipeline. Use the generated Docker images and deploy them to Cloud Run. Update the configurations and the required endpoints.
The correct answer is A. Deploying the Docker images to Cloud Run is the most efficient approach because Cloud Run is designed to run containerized applications in a serverless environment. This aligns with the current setup of using Docker containers for the microservices. Additionally, using the existing CI/CD pipeline ensures a seamless transition, and updating the configurations and required endpoints will make sure the application runs smoothly in the new environment. Options B and C suggest using Cloud Functions, which is not suitable for complex applications with multiple microservices. Option D suggests using the same configurations as on-premises, which might not be compatible with the Cloud Run environment without updates.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your team is currently managing an on-premises ecommerce application that employs a complex architecture of microservices. These microservices are developed using Python and are hosted within Docker containers. The application configurations are managed through environment variables. The team is now tasked with migrating this application to a serverless infrastructure on Google Cloud. What steps should you take to successfully deploy your application in this new environment?
A
Use your existing CI/CD pipeline. Use the generated Docker images and deploy them to Cloud Run. Update the configurations and the required endpoints.
B
Use your existing continuous integration and delivery (CI/CD) pipeline. Use the generated Docker images and deploy them to Cloud Function. Use the same configuration as on-premises.
C
Use the existing codebase and deploy each service as a separate Cloud Function. Update the configurations and the required endpoints.
D
Use your existing codebase and deploy each service as a separate Cloud Run. Use the same configurations as on-premises.
No comments yet.