Practice Test 3 | Google Cloud Certified Professional Cloud Architect | Dumps | Mock Test
For this question, refer to the EHR Healthcare case study.
EHR Healthcare wants, in an initial project phase, to transfer its workloads to the Cloud in an efficient way and minimizing the impact for applications.
This also applies to its on-premises databases, which are mySQL, SQL Server and MongoDB.
At a later stage, the data management will be reorganized together with the management applications and procedures.
There is a need to bring MongoDB to the Cloud. MongoDB is used for non-transactional, scalable systems and you want to continue using a noSQL system of this type, in order to have full control of its management but the final goal is to have a service that is fully managed in the Google Cloud Platform.
Given these requirements, which solution would you recommend for the first migration and subsequent integration?
A. Install MongoDB in Cloud on a VM and then switch to Datastore
B. Deploy MongoDB in Cloud as a StatefulSet and then switch to Firestore
C. Directly migrate MongoDB to Firestore
D. Directly migrate MongoDB to DocumentDB and then switch to Datastore
Correct answer: B
MongoDB is a horizontally scalable noSQL Document Database that is not offered in GCP as a managed service; in order to obtain horizontal scalability and data redundancy, however, you need to install it on a cluster of VMs.
Given the volumes of EHR, the best solution is certainly to use Kubernetes and its StatefulSets and Volumes.
Kubernetes is known for offering a perfect environment for Microservices, with its Stateless Deployments , but it is not the only possible solution. In fact, there are also StatefulSets, Demons and Jobs.
It should be noted that Google uses its own internal Kubernetes for any type of workload.
The closest MongoDB-like product in the GCP is Firebase, so this is the best strategy.
- A is wrong because a single VM deployment doesn’t offer any scalability and failover.
- C and D are wrong because a migration is out of the requirements scopes. Moreover, DocumentDB is an AWS Service, not a GCP one.
For any further detail:
Comments are closed, but trackbacks and pingbacks are open.