Google Professional Data Engineer Architecture and Operations

Answer : A
MariaDB needs costume metrics , and stackdriver built-in monitoring tools will not provide these metrics . Opencensus Agent will do this for you
For more info , refer to :
https://cloud.google.com/monitoring/custom-metrics/open-census

Answer: C
Description: The GitHub repository named google-fluentd-catch-all-config which includes the configuration files for the Logging agent for ingesting the logs from various third-party software packages.

Here's the rationale:
StackDriver Agent: The StackDriver Agent is designed to collect system and application metrics from virtual machine instances and send them to StackDriver Monitoring. It simplifies the process of collecting and forwarding metrics.
MySQL Plugin: The StackDriver Agent has a MySQL plugin that allows you to collect MySQL-specific metrics without the need for additional custom development. This includes metrics related to network connections, disk IO, and replication status – which are the specific metrics you mentioned.

Option D is the most straightforward and least development-intensive approach to achieve the monitoring and alerting requirements for MariaDB on GCE VM Instances using StackDriver.

replication status seems to be not included in sql agent metrics. but I do not like A in terms of efforts

it can't be A as it saying minimal development but for opencensus the development is needed.

To use metrics collected by OpenCensus in your Google Cloud project, you must make the OpenCensus metrics libraries and the Stackdriver exporter available to your application. The Stackdriver exporter exports the metrics that OpenCensus collects to your Google Cloud project. You can then use Cloud Monitoring to chart or monitor those metrics.

Option D is Correct
MariaDB is a community-developed, commercially supported fork of the MySQL relational database management system (RDBMS). To collect logs and metrics for MariaDB, use the mysql receivers.

The mysql receiver connects by default to a local MariaDB server using a Unix socket and Unix authentication as the root user.

reference:-https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/third-party/mariadb

https://cloud.google.com/monitoring/agent/ops-agent/third-party/mariadb

C is the answer, fluentd plug in is needed as the DB is on GCE

go for D

A
StackDriver Agent monitors default metrics of VMs and some Database stuff with the MySQL Plugin. Here you want to monitor some more custom stuff like Replication of MariaDB (I didn’t find anything of this sort in the plugin page), and you may want to use Custom Metrics rather than default metrics. “Cloud Monitoring automatically collects more than 1,500 built-in metrics from more than 100 monitored resources. But those metrics cannot capture application-specific data or client-side system data. Those metrics can give you information on backend latency or disk usage, but they can’t tell you how many background routines your application spawned.” https://cloud.google.com/monitoring/custom-metrics/open-census#monitoring_opencensus_metrics_quickstart-python

I'm not 100% sure as I have no experience with that issue, but I would say it's D - both A and D should work, but the keyword is "with minimal development effort" (and using pre-built plugin > creating custom metric in terms of simplicity, that's obvious) and all of the relevant data (as per question) should be there: https://cloud.google.com/monitoring/api/metrics_agent#agent-mysql

I'm not sure if C would work, but it also seems more advanced in implementation than D. B is 100% wrong and insufficient for that use case.

Feel free to prove me wrong :)

A and D both seem like viable options here, unsure which is Google's preferred method as that would be deemed the correct answer in the exam. Any opinions?

D
mariaDB is an extension of mysql and mysql plugin must work fine to extract the metrics of mariaDB.

Opencensus Agent is right one

D is correct. Answer : D
mariaDB is an extension of mysql and mysql plugin must work fine to extract the metrics of mariaDB.

Answer : D
mariaDB is an extension of mysql and mysql plugin must work fine to extract the metrics of mariaDB.
https://cloud.google.com/monitoring/agent/plugins/mysql

Well it doesn't mentions anything about not enough bandwidth to meet your project deadline. I guess you can assume they have 200GBps+ of bandwith, otherwise it shouldn't take only a few hours.

One who wanted to use Transfer Appliance to migrate data in a few hours, you should live near Google office and run really fast :D

Cloud Interconnect provides a dedicated private connection between on-prem and Google Cloud for high bandwidth (up to 100 Gbps) and low latency. This facilitates large, fast data transfers.
Storage Transfer Service supports parallel data transfers over Cloud Interconnect. It can transfer petabyte-scale datasets faster by transferring objects in parallel.
Storage Transfer Service uses HTTPS encryption in transit and at rest by default for secure data transfers.
It follows Google-recommended practices for large data migrations vs ad hoc methods like gsutil or scp.
The other options would take too long for a 1 PB transfer (VPN capped at 3 Gbps, manual transfers) or introduce extra steps like batching and checksums. Cloud Interconnect + Storage Transfer is the recommended Google solution.

It is believed that A.
One reason is that for "secure" and "in a few hours," the communication can be done securely using a direct physical line without going through an ISP. Also, depending on the case, in the case of "Dedicated Interconnect," the maximum transfer can be as high as 200 Gbps, and the fastest data transfer of 1 PB can be completed in 11 hours.
Therefore, A.

A
https://cloud.google.com/storage-transfer/docs/transfer-options#:~:text=Transferring%20more%20than%201%20TB%20from%20on%2Dpremises

Dedicated Interconnect provides direct physical connections between your on-premises network and Google's network. Dedicated Interconnect enables you to transfer large amounts of data between networks, which can be more cost-effective than purchasing additional bandwidth over the public internet. https://cloud.google.com/network-connectivity/docs/interconnect/concepts/dedicated-overview

1 PB and "few hours". It is clearly referring to Transfer Appliance

https://cloud.google.com/architecture/migration-to-google-cloud-transferring-your-large-datasets#time

gpt: Based on security and speed, if the data is highly sensitive and security is the top priority, then option B (using a Transfer Appliance) may be a better choice. Transfer Appliance uses hardware encryption to transfer data and is designed to securely transfer large amounts of data. However, if speed is the primary concern, then option A (using Cloud Interconnect and Storage Transfer Service) may be a better choice as it allows for faster transfer speeds over a dedicated and secure connection. It ultimately depends on the specific needs and priorities of the organization.

A vague treaky question. Bad author of it...
B is also good. As were said in discuss. by smb, a question asks "safe connection", so - a Cloud Interconnect (A)

Either this question is very tricky or very poor written. It says 'Data transfer time during the migration should take only a few hours'. We should not add the 20days for overhead time for Appliance into the total time of migration.

If 'a few hours' = 30hours or more, A will be good enough.
If 'a few hours' = 10 or less, B is the only way (with multiple devices to copy at the same time)

Expected time via transfer appliance is around 20 days , and achieving the same using Storage transfer service with highest bandwidth of 100GPS is 30 hrs, so hence its been asked for hrs .. its A
Acquiring a Transfer Appliance is straightforward. In the Google Cloud console, you request a Transfer Appliance, indicate how much data you have, and then Google ships one or more appliances to your requested location. You're given a number of days to transfer your data to the appliance ("data capture") and ship it back to Google.

The expected turnaround time for a network appliance to be shipped, loaded with your data, shipped back, and rehydrated on Google Cloud is 20 days. If your online transfer timeframe is calculated to be substantially more than this timeframe, consider Transfer Appliance. The total cost for the 300 TB device process is less than $2,500.

Even with 100gbps bandwith, you will not reach a data transfer time within the range of "hours" for 1PB. Transfer appliance is the way to go. https://cloud.google.com/architecture/migration-to-google-cloud-transferring-your-large-datasets#time

Answer A,
One time transfer is cheaper and less secure always using Transfer Appliance.
you need to do it in faster way, set up Interconnect speed limit is 50mbps - 10GBps
and Transfer Appliance speed can goes up to 40GBps.
I am choosing A for security concern only.

A is right

B
https://cloud.google.com/architecture/migration-to-google-cloud-transferring-your-large-datasets#:~:text=Few%20things%20in,not%20be%20obtained.

A is correct.

A is correct
https://cloud.google.com/architecture/migration-to-google-cloud-transferring-your-large-datasets#transfer_appliance_for_larger_transfers

Huge data can be migrated over cloud interconnect