Exam Professional Cloud Architect All Questions

View all questions & answers for the Professional Cloud Architect exam

Exam Professional Cloud Architect topic 12 question 1 discussion

Actual exam question from Google's Professional Cloud Architect

Question #: 1
Topic #: 12

[All Professional Cloud Architect Questions]

For this question, refer to the Dress4Win case study. Dress4Win 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. 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 App Engine, and MySQL to Cloud Datastore, and NAS to Cloud Storage. Deploy RabbitMQ, and deploy Hadoop servers using Deployment Manager.
B. Migrate RabbitMQ to Cloud Pub/Sub, Hadoop to BigQuery, and NAS to Compute Engine with Persistent Disk storage. Deploy Tomcat, and deploy Nginx using Deployment Manager.
C. Implement managed instance groups for Tomcat and Nginx. Migrate MySQL to Cloud SQL, RabbitMQ to Cloud Pub/Sub, Hadoop to Cloud Dataproc, and NAS to Compute Engine with Persistent Disk storage.
D. Implement managed instance groups for the Tomcat and Nginx. Migrate MySQL to Cloud SQL, RabbitMQ to Cloud Pub/Sub, Hadoop to Cloud Dataproc, and NAS to Cloud Storage.

Show Suggested Answer

Suggested Answer: D 🗳️

by MeasService at Oct. 19, 2019, 6:18 p.m.

Comments

Submit Cancel

MeasService

Highly Voted 5 years, 3 months ago

Why do we need to put NAS data on persistant disk and not on GCS ? I would go with D!

upvoted 46 times

techalik

4 years, 2 months ago

1. 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. Ref: https://cloud.google.com/compute/docs/images Using the same custom images every time ensures that your environments are "reliable and reproducible" and you achieve "rapid provisioning". D

upvoted 12 times

...

nitinz

3 years, 11 months ago

ans is D

upvoted 4 times

...

tartar

4 years, 5 months ago

D is ok

upvoted 11 times

Jphix

4 years ago

Agreed. 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 compute costs. D all the way.

upvoted 3 times

...

KouShikyou

Highly Voted 5 years, 3 months ago

I prefer D. Original NAS is for image, log, backup. GCS fits it perfectly.

upvoted 22 times

exampanic

5 years, 1 month ago

I agree that GCS fits perfectly for storing images, log, backup. However, the question asks to avoid major application changes. GCS is not NAS, meaning it does not provide SMB or NFS shares. Therefore moving the NAS files to Google Cloud Storage would require a major application change in the way they access these files. I believe the correct answer would be C.

upvoted 10 times

poseidon24

3 years, 6 months ago

It can, check on Cloud Storage FUSE. Buckets can be mounted as file systems.

upvoted 4 times

...

cloud_rider

Most Recent 4 months, 3 weeks ago

Selected Answer: D

D is correct answer.

upvoted 1 times

...

user263263

6 months, 1 week ago

A - no, MySQL (relational) to Datastore (document-oriented) is not a good idea B - no, because Hadoop to BigQuery C - NAS is currently 65 TB ("100 TB total storage; 35 TB available") for image storage, logs, backups, so with "10 times its size in data that mirrors the existing patterns of usage" would be 650 TB. A look to https://cloud.google.com/architecture/storage-advisor?hl=en#comparative_analysis says, it's too big for Persistent Disk. Also a replacement for NAS would be Filestore. D - I would choose this, even if it is an application change. Who knows if it is major. But it can have a good ROI, because Cloud Storage can be cheaper.

upvoted 2 times

...

farhan880

7 months ago

Selected Answer: C

Because min change

upvoted 1 times

...

farhan880

7 months ago

Selected Answer: C

Because min change

upvoted 1 times

...

mesodan

11 months, 1 week ago

Selected Answer: D

Use case suitability: Cloud Storage: Ideally suited for storing large, unstructured data like images, videos, and backups, which is likely the case for Dress4Win's NAS data. Persistent Disk: More appropriate for frequently accessed data that requires block-level access, such as databases or operating systems for virtual machines.

upvoted 4 times

...

kampatra

12 months ago

Selected Answer: D

Correct Ans: A NAS `" image storage, logs, backups : for storing images, logs and backups Cloud Storage is best practice and cost effective also.

upvoted 2 times

kampatra

12 months ago

Wrongly typed A, it must be D

upvoted 1 times

...

mbacelar

1 year, 1 month ago

Selected Answer: D

Should be D

upvoted 2 times

...

MahAli

1 year, 1 month ago

Selected Answer: C

Voting c NAS could have been replaced with file store to minimize any change, moving to GCS is not that easy change in overall architecture

upvoted 1 times

...

Jannchie

1 year, 1 month ago

Selected Answer: C

C, because we can run some script on NAS. It can act like a normal server. But GCS cannot.

upvoted 2 times

...

techtitan

1 year, 2 months ago

Selected Answer: C

without making major application changes and still maximize the ROI --> compute engine with persistent disk. without knowing access patterns, GCS may not be an easy change.

upvoted 1 times

...

thamaster

2 years, 1 month ago

Selected Answer: D

you don't need NAS to store archive and Image disk

upvoted 2 times

...

amxexam

2 years, 8 months ago

Selected Answer: D

D is the correct chand equivalent mapping

upvoted 2 times

...

MF2C

3 years ago

SAN -> persistent disk, NAS -> Cloud Storage

upvoted 2 times

...

edilramos

3 years, 1 month ago

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.

upvoted 2 times

...

phantomsg

3 years, 2 months ago

Selected Answer: C

The answer should be C. 'A' and 'B' are ruled out as they introduce significant architecture changes. or irrelevant. 'D' is fine except proposes to replace NAS with Cloud Storage. This will introduce major architectural changes. Instead, if the choice was to move 'NAS' to 'Cloud Filestore' then it would have made sense. Answer 'C' is the closest with the least amount of architectural changes involved in migration.

upvoted 3 times

...

Load full discussion...