Question-23: The total projected investment cost over three years is equal to $0.79 million. This means a return on investment of 222% (on a 3-year level) with a break-even on their investment in 8 months. QuickTechie Inc is expected to grow to 10 times its size in 1 year with a corresponding growth in data and traffic that mirrors the existing patterns of usage. QuickTechie Inc. uses Google Cloud Platform services for its data processing needs. The CIO has set the target of migrating production infrastructure to the cloud within the next 6 months. How will you configure the solution to scale for this growth without making major application changes and still maximize the ROI?
A. Migrate the web application layer to Google's App Engine, MySQL to Cloud Datastore, and NAS to the cloud. Deploy RabbitMQ, and deploy Hadoop servers using Deployment Manager.
B. Migrate RabbitMQ to Cloud Pub/Sub, BigQuery to Hadoop, and NAS to Compute Engine with persistent disc storage. Tomcat and Nginx should be deployed using the Deployment Manager.
C. Implement instance group management for Tomcat and Nginx. MySQL should be migrated to Cloud SQL, RabbitMQ to Cloud Pub/Sub, Hadoop to Cloud Dataproc, and NAS to Compute Engine with persistent disc storage.
D. Implement Tomcat and Nginx managed instance groups MySQL should be migrated to Cloud SQL, RabbitMQ to Cloud Pub/Sub, Hadoop to Cloud Dataproc, and NAS to Cloud Storage.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 4 Explanation: Looking to maximize ROI as well according to the question, and even the most expensive cloud storage is still going to be half the price of cheapest Persistent Disk storage, and that's without even including your computer costs. Option-4 all the way. Use Cloud Marketplace to provision Tomcat and Nginx on Google Compute Engine. 2. Replace MySQL with Cloud SQL for MySQL. 3. Use the Deployment Manager to provision Jenkins on Google Compute Engine. is the right answer. As explained above, you would use Cloud SQL to replace MySQL. For the other requirements, i.e. Nginx/Tomcat and Jenkins, you can deploy these through Cloud Deployment Manager by using custom images. Using the same custom images every time ensures that your environments are reliable and reproducible and you achieve rapid provisioning. Option-4. Managed Instances With Tomcat and Nginx would bring the minimum necessary tweaking to the new environment. Migrating from MySql to Cloud SQL does not require any syntax changes. Moving from Rabbit MQ to Pub/Sub is relatively straightforward and has very complete documentation. DataProc has Libraries and tools to ensure Apache Hadoop interoperability. Without many changes in the environment, mainly keeping the original architecture, Datastorage will keep the presentation characteristics of a shared area, mapped to the instances. They expect “to grow to 10 times its size in 1 year with a corresponding growth in data and traffic� And “migrating production infrastructure to the cloud within the next 6 months�. The MySQL DB has now 5 TB of data. In 6 months, it will raise to 25 TB. In 1 year to 50 TB. The limit for MySQL DB size is 30 TB. So it is very likely that when we launch the solution on PROD the MySQL DB will be very close to the limit. I would rather avoid the problem and migrate MySQL DB to Datastore. Datastore is also transactional like MySQL, hence no change in application code. Deploying RabbitMQ also will avoid the need to the code change. Migration of the web application layer to App Engine and Hadoop: as is. From the application code perspective, migration to option A requires only one change NAS -> GCS. And at the end we get and scalable solution.