The Google Professional Machine Learning Engineer (Professional-Machine-Learning-Engineer)

The best option for reducing the sensitivity of the dataset before training the model is to use the Cloud Data Loss Prevention (DLP) API to scan for sensitive data, and use Dataflow with the DLP API to encrypt sensitive values with Format Preserving Encryption. This option allows you to keep every column in the dataset, while protecting the sensitive data from unauthorized access or exposure.  The Cloud DLP API can detect and classify various types of sensitive data, such as names, email addresses, phone numbers, credit card numbers, and more 1 .  Dataflow can create scalable and reliable pipelines to process large volumes of data from BigQuery and other sources 2 .  Format Preserving Encryption (FPE) is a technique that encrypts sensitive data while preserving its original format and length, which can help maintain the utility and validity of the data 3 . By using Dataflow with the DLP API, you can apply FPE to the sensitive values in the dataset, and store the encrypted data in BigQuery or another destination.  Yo u can also use the same pipeline to decrypt the data when needed, by using the same encryption key and method 4 .

The other options are not as suitable as option B, for the following reasons:

Option A: Using Dataflow to ingest the columns with sensitive data from BigQuery, and then randomize the values in each sensitive column, would reduce the sensitivity of the data, but also the utility and accuracy of the data.  Randomization is a technique that replaces sensitive data with random values, which can prevent re-identification of t he data, but also distort the distribution and relationships of the data 3 . This can affect the performance and quality of the ML model, especially if every column is critical to the model.

Option C: Using the Cloud DLP API to scan for sensitive data, and use Dataflow to replace all sensitive data by using the encryption algorithm AES-256 with a salt, would reduce the sensitivity of the data, but also the utility and validity of the data. AES-256 is a symmetric encryption algorithm that uses a 256-bit key to encrypt and decrypt data. A salt is a random value that is added to the data before encryption, to increase the randomness and security of the encrypted data. However, AES-256 does not preserve the format or length of the original data, which can cause problems when storing or processing the data.  For example, if the original data is a 10-digit phone number, AES-256 would produce a much longer and different string, which can break the schema or logic of the dataset 3 .

Option D: Before training, using BigQuery to select only the columns that do not contain sensitive data, and creating an authorized view of the data so that sensitive values cannot be accessed by unauthorized individuals, would reduce the exposure of the sensitive data, but also the completeness and relevance of the data. An authorized view is a BigQuery view that allows you to share query results with particular users or groups, without giving them access to the underlying tables. However, this option assumes that you can identify the columns that do not contain sensitive data, which may not be easy or accurate. Moreover, this option would remove some columns from the dataset, which can affect the performance and quality of the ML model, especially if every column is critical to the model.

TFRecord is a binary file format that stores your data as a sequence of binary strings 1 .  TFRecord files are efficient, scalable, and easy to process 1 .  Sharding is a technique that splits a large file into smaller files, which can improve parallelism and perfo rmance 2 .  Dataflow is a service that allows you to create and run data processing pipelines on G oogle Cloud 3 .  Dataflow can create sharded TFRecord files from your images in a Cloud Storage directory 4 .

tf.data.TFRecordDataset is a class that allows you to read and parse TFRecord files in TensorFlow. You can use this class to create a tf.data.Dataset object that represents your input data for training. tf.data.Dataset is a high-level API that provides various methods to transform, batch, shuffle, and prefetch your data.

Vertex AI Training is a service that allows you to train your custom models on Google Cloud using various hardware accelerators, such as GPUs. Vertex AI Training supports TensorFlow models and can read data from Cloud Storage. You can use Vertex AI Training to train your image classification model by using a V100 GPU, which is a powerful and fast GPU for deep learning.

AI Platform Training is a service that allows you to run your machine learning experiments on Google Cloud using various features, model architectures, and hyperparameters.  You can use AI Platform Training to scale up your experiments, leverage distributed training, and access specialized hardware such as GPUs and TPUs 1 . Cloud Monitoring is a service that collects and analyzes metrics, logs, and traces from Google Cloud, AWS, and other sources.  You can use Cloud Monitoring to create dashboards, alerts, and reports based on your data 2 .  The Monitoring API is an interface that allows you to programmatically access and manipulate your monitoring data 3 .

By using AI Platform Training and Cloud Monitoring, you can track and report your experiments while minimizing manual effort.  You can write the accuracy metrics from your experiments to Cloud Monitoring usin g the AI Platform Training Python package 4 . You can then query the results using the Monitoring API and compare the performance of different experiments.  You can also visualize the metrics in the Cloud Console or create custom dashboards and alerts 5 . Therefore, using AI Platform Training and Cloud Monitoring is the best option for this use case.

 TensorFlow Data Validation (TFDV) is a library that helps you understand, validate, and monitor your data for machine learning. It can automatically detect and report schema anomalies, such as missing features, new features, or different data types, in your data. It can also generate descriptive statistics and data visualizations to help you explore and debug your data. TFDV can be integrated with your model training pipeline to ensure data quality and consistency throughout the machine learning lifecycle.  References :

TensorFlow Data Validation

Data Validation | TensorFlow

Data Validation | Machin e Learning Crash Course | Google Developers

In the context of MLOps on Google Cloud and Vertex AI, the goal is to balance model performance with operational efficiency. Here is why Option D is the correct strategy for minimizing cost and effort while maintaining reliability:

Data Drift and Model Decay: In production environments, the distribution of live data often changes over time (a phenomenon known as Training-Serving Skew or Data Drift ). If the customer attributes in the real world no longer match the data the model was trained on, the model’s predictive power will degrade.

Vertex AI Model Monitoring: Vertex AI provides built-in tools to monitor for Feature Attribution Drift and Training-Serving Skew . By setting up alerts for these shifts, you implement " Performance-based " or " Condition-based " retraining. This is more cost-effective than retraining every week (Option C), which might use expensive compute resources to retrain a model that is still performing perfectly.

Why other options are incorrect:

Option A: Latency is an infrastructure/engineering metric, not a predictive quality metric. Retraining the model will not fix latency issues caused by high traffic; that would require scaling your prediction nodes.

Option B: While accuracy is important, waiting for a 10% drop on a new dataset often means the model has already been underperforming in production for some time. Furthermore, calculating accuracy requires " ground truth " (actual labels), which may not be available immediately for churn.

Option C: Retraining weekly regardless of performance leads to unnecessary compute costs and engineering overhead if the data hasn ' t changed significantly.

Categorical cross-entropy is a loss function that is suitable for multi-class classification problems, where the target variable has more than two possible values. Categorical cross-entropy measures the difference between the true probability distribution of the target classes and the predicted probability distribution of the model. It is defined as:

L = - sum(y_i * log(p_i))

where y_i is the true probability of class i, and p_i is the predicted probability of class i. Categorical cross-entropy penalizes the model for making incorrect predictions, and encourages the model to assign high probabilities to the correct classes and low probabilities to the incorrect classes.

For the use case of building a model that predicts whether images contain a driver’s license, passport, or credit card, categorical cross-entropy is the appropriate loss function to use. This is because the problem is a multi-class classification problem, where the target variable has three possible values: [‘drivers_license’, ‘passport’, ‘credit_card’]. The label map is a list that maps the class names to the class indices, such that ‘drivers_license’ corresponds to index 0, ‘passport’ corresponds to index 1, and ‘credit_card’ corresponds to index 2. The model should output a probability distribution over the three classes for each image, and the categorical cross-entropy loss function should compare the output with the true labels. Therefore, categorical cross-entropy is the best loss function for this use case.

Cost-effectiveness: User-managed notebooks in Vertex AI Workbench allow you to leverage pre-configured virtual machines with reasonable resource allocation, keeping costs lower compared to options involving managed notebooks or Dataproc clusters.

Development flexibility: User-managed notebooks offer full control over the environment, allowing you to install additional libraries or dependencies needed for your specific EDA, preprocessing, and model training tasks. This flexibility is crucial while experimenting with different algorithms.

BigQuery integration: The %%bigquery magic commands provide seamless integration with BigQuery within the Jupyter Notebook environment. This enables efficient querying and exploration of customer transaction data stored in BigQuery directly from the notebook, streamlining the workflow.

Other options and why they are not the best fit:

B. Managed notebook: While managed notebooks offer an easier setup, they might have limited customization options, potentially hindering your ability to install specific libraries or tools.

C. Dataproc Hub: Dataproc Hub focuses on running large-scale distributed workloads, and it might be overkill for your scenario involving exploratory analysis and experimentation with different algorithms. Additionally, it could incur higher costs compared to a user-managed notebook.

D. Dataproc cluster with spark-bigquery-connector: Similar to option C, using a Dataproc cluster with the spark-bigquery-connector would be more complex and potentially more expensive than using %%bigquery magic commands within a user-managed notebook for accessing BigQuery data.