Free Google Cloud Architect Professional Exam Braindumps
Google Cloud Certified - Professional Cloud Architect Questions 226–230 (page: 47)

Updated On: 31-Aug-2026

Company Overview -KnightMotives is a car manufacturer specializing in autonomous, self-driving vehicles, including Battery Electric Vehicles (BEVs), hybrids and traditional internal combustion engine (ICE) vehicles.
While KnightMotives has made strides with the in-vehicle experience in their BEV fleet, the hybrid and ICE vehicles have yet to implement these new systems and are viewed poorly by critics and drivers. The lack of modern in-vehicle technology in hybrid and ICE vehicles has resulted in declining sales and customer satisfaction. KnightMotives wants to modernize the consumer experience across all vehicles within five years Artificial Intelligence offers a unique opportunity to revolutionize the in-vehicle experience, as well as the shopping buying and service/maintenance experience. Investment in this new technology will require a shift in financial priorities on a global scale. KnightMotives also wants to improve their online ordering system, which is unreliable. Systems for customers to build their vehicle online for acquisition through a dealer are not delivering the data or reliability that dealers need, causing. A strain in the relationship between KnightMotives and dealers. Service technicians and sales staff need better tooling to enhance dealer successes, including built-to-order vehicles. Solution Concept -
KnightMotives wants to shift from manufacturing cars to creating a complete and compelling “automotive experience.” Then strategy prioritizes delivering a consistent experience across all models, developing AI-powered features, generating new revenue from data monetization, adopting a digital focus to differentiate their brand from competitors, and developing better tools for mechanics and salespeople. Existing Technical Environment -KnightMotives's IT is largely on-premises with some applications on major cloud platforms. Their supply chain runs on an outdated mainframe, and Enterprise Resource Planning (ERP) is also outdated, making new promotions and dealer discounts difficult to implement. Dealers have no budget for new equipment. There is fragmentation across vehicles with multiple code bases, and significant technical debt from supporting backwards compatibility. Network connectivity to manufacturing plants and vehicle connectivity in rural areas are challenges. Business Requirements -Key business requirements include fostering a personalized relationship with the driver and delivering a cohesive experience across all models. Creating a better build-to-order model will reduce time on the lot and provide transparency for both dealers and customers. Additionally, KnightMotives seeks to monetize corporate data to finance new technology investments, as their current AI infrastructure is obsolete and corporate data remains siloed. Security is a paramount concern due to past data breaches Adherence to European Union (EU) data protection regulations, especially for emerging autonomous platforms, is critical. KnightMotives plans to make significant investments in fully autonomous driving capabilities, with initial implementation targeting regions with favorable regulatory environments. Prioritizing employee upskilling, attracting top-tier talent, and fostering better communication between business and technical teams are also critical objectives. Technical Requirements -•Modernizing the in-vehicle experience includes developing a consistent user experience (UX) that seamlessly integrates AI-powered features across all models, updating in-vehicle hardware and software in legacy models to support new UX features and AI capabilities, and ensuring reliable network connectivity, especially in rural areas, to support real-time AI features and data transmission. •Network upgrades are necessary to support increased data traffic and improve connectivity between plants and headquarters. •IT infrastructure modernization requires adopting a hybrid cloud strategy to leverage the benefits of both on-premises and cloud infrastructure, and gradually modernizing or replacing legacy systems to improve efficiency and agility. •Autonomous vehicle development and testing requires investing in cutting-edge AI and machine learning technologies, building a robust simulation environment, and ensuring compliance with evolving regulations related to autonomous vehicles. •Data monetization and insights requires implementing a robust data management platform, strict data security and privacy measures, and a scalable AI/ML infrastructure. •Increased focus on security and risk management involves implementing a comprehensive security framework to protect against cyber threats and data breaches, developing an incident response plan, and providing security awareness training to employees. •Providing a delightful experience for dealers and customers requires improving the online build-to-order system; developing modern dealer tools to streamline dealer operations, including sales, service, and inventory management; and implementing a comprehensive Customer Relationship Management (CRM) system to track customer interactions personalize experiences, and improve customer satisfaction. Executive Statement -KnightMotives is committed to enhancing safety and saving lives by leveraging an extensive body of data — encompassing driving, road conditions, behavioral studies, and crash safety statistics — to create compelling digital experiences for drivers. Our AI consistently outperforms national safety statistics, ensuring the unique and coveted KnightMotives experience is aligned across all our vehicle models. Michael Knight, KnightMotives CEO For this question, refer to the KnightMotives Automotive case study. As part of its development of fully autonomous driving vehicles. KnightMotives wants to analyze all vehicle sensor data during test drives. The analysis will enable KnightMotives to improve its software based on insights from this data. •Different event types, such as parking, overtaking and navigating, need to be analyzed. Each test vehicle and event type has an ID. •Different categories of sensors, such as cameras, radars, and ultrasonic beams, also need to be analyzed. During each autonomously-initiated event, data from multiple sensors will be captured and sent to Google Cloud where the data will be stored in Bigtable. During data analysis, you want to be able to retrieve all sensor data of occurrences of the same event type for a specific vehicle within a specific interval of time. You need to design a Bigtable schema that is optimized for read performance.
What should you do?

  1. Use the sensor category, event ID, and timestamp (in that order) as the row key. Create a column family for each individual sensor and a column qualifier for each vehicle.
  2. Use the timestamp, vehicle ID, and event ID (in that order) as the row key. Create a column family per sensor category, and use a column qualifier for each individual sensor within its respective category.
  3. Use the vehicle ID, event ID, and timestamp (in that order) as the row key. Create a column family per sensor category, and use a column qualifier for each individual sensor within its respective category.
  4. Use the vehicle ID and event ID (in that order) as the row key. Create a column family per sensor category, and use a column qualifier for each individual sensor within its respective category. Utilize the timestamped versions of a cell to distinguish between different moments in time of similar events.

Answer(s): C

Explanation:

C: Use the vehicle ID, event ID, and timestamp (in that order) as the row key. Create a column family per sensor category, and use a column qualifier for each individual sensor within its respective category. Row Key Design: Cloud Bigtable structures data lexicographically by row key [1]. To optimize read performance for queries filtering by a specific vehicle, same event type, and specific interval of time, the row key components must flow from most general to most specific filter [1]. Structuring it as [Vehicle_ID]#[Event_Type_ID]#[Timestamp] allows you to perform highly efficient prefix scans to isolate a specific vehicle and event, while using a timestamp range scan to grab the exact time interval.



Company Overview -KnightMotives is a car manufacturer specializing in autonomous, self-driving vehicles, including Battery Electric Vehicles (BEVs), hybrids and traditional internal combustion engine (ICE) vehicles.
While KnightMotives has made strides with the in-vehicle experience in their BEV fleet, the hybrid and ICE vehicles have yet to implement these new systems and are viewed poorly by critics and drivers. The lack of modern in-vehicle technology in hybrid and ICE vehicles has resulted in declining sales and customer satisfaction. KnightMotives wants to modernize the consumer experience across all vehicles within five years Artificial Intelligence offers a unique opportunity to revolutionize the in-vehicle experience, as well as the shopping buying and service/maintenance experience. Investment in this new technology will require a shift in financial priorities on a global scale. KnightMotives also wants to improve their online ordering system, which is unreliable. Systems for customers to build their vehicle online for acquisition through a dealer are not delivering the data or reliability that dealers need, causing. A strain in the relationship between KnightMotives and dealers. Service technicians and sales staff need better tooling to enhance dealer successes, including built-to-order vehicles. Solution Concept -KnightMotives wants to shift from manufacturing cars to creating a complete and compelling “automotive experience.” Then strategy prioritizes delivering a consistent experience across all models, developing AI-powered features, generating new revenue from data monetization, adopting a digital focus to differentiate their brand from competitors, and developing better tools for mechanics and salespeople. Existing Technical Environment -KnightMotives's IT is largely on-premises with some applications on major cloud platforms. Their supply chain runs on an outdated mainframe, and Enterprise Resource Planning (ERP) is also outdated, making new promotions and dealer discounts difficult to implement. Dealers have no budget for new equipment. There is fragmentation across vehicles with multiple code bases, and significant technical debt from supporting backwards compatibility. Network connectivity to manufacturing plants and vehicle connectivity in rural areas are challenges. Business Requirements -Key business requirements include fostering a personalized relationship with the driver and delivering a cohesive experience across all models. Creating a better build-to-order model will reduce time on the lot and provide transparency for both dealers and customers. Additionally, KnightMotives seeks to monetize corporate data to finance new technology investments, as their current AI infrastructure is obsolete and corporate data remains siloed. Security is a paramount concern due to past data breaches Adherence to European Union (EU) data protection regulations, especially for emerging autonomous platforms, is critical. KnightMotives plans to make significant investments in fully autonomous driving capabilities, with initial implementation targeting regions with favorable regulatory environments. Prioritizing employee upskilling, attracting top-tier talent, and fostering better communication between business and technical teams are also critical objectives. Technical Requirements -•Modernizing the in-vehicle experience includes developing a consistent user experience (UX) that seamlessly integrates AI-powered features across all models, updating in-vehicle hardware and software in legacy models to support new UX features and AI capabilities, and ensuring reliable network connectivity, especially in rural areas, to support real-time AI features and data transmission. •Network upgrades are necessary to support increased data traffic and improve connectivity between plants and headquarters. •IT infrastructure modernization requires adopting a hybrid cloud strategy to leverage the benefits of both on-premises and cloud infrastructure, and gradually modernizing or replacing legacy systems to improve efficiency and agility. •Autonomous vehicle development and testing requires investing in cutting-edge AI and machine learning technologies, building a robust simulation environment, and ensuring compliance with evolving regulations related to autonomous vehicles. •Data monetization and insights requires implementing a robust data management platform, strict data security and privacy measures, and a scalable AI/ML infrastructure. •Increased focus on security and risk management involves implementing a comprehensive security framework to protect against cyber threats and data breaches, developing an incident response plan, and providing security awareness training to employees. •Providing a delightful experience for dealers and customers requires improving the online build-to-order system; developing modern dealer tools to streamline dealer operations, including sales, service, and inventory management; and implementing a comprehensive Customer Relationship Management (CRM) system to track customer interactions personalize experiences, and improve customer satisfaction. Executive Statement -KnightMotives is committed to enhancing safety and saving lives by leveraging an extensive body of data — encompassing driving, road conditions, behavioral studies, and crash safety statistics — to create compelling digital experiences for drivers. Our AI consistently outperforms national safety statistics, ensuring the unique and coveted KnightMotives experience is aligned across all our vehicle models. Michael Knight, KnightMotives CEO For this question, refer to the KnightMotives Automotive case study, KnightMotives has deployed their new Dealer Tools on Google Kubernetes Engine (GKE). You are supporting KnightMotives in the performance of the GKE workloads. Some of the Pods are Statefull. To ensure these Pods do not consume an unlimited amount of CPU, you have configured resource limits on the Deployments. You have identified that these Pods were allocated too much CPU and are actually consuming drastically less some of the time. You want to optimize resource usage and allow maximum flexibility in case of higher load.
What should you do?

  1. Configure resource requests per Deployment. Set resource requests slightly above the typical CPU usage observed during monitoring.
  2. Configure resource requests per Deployment. Ensure the requests are equal to the current limits.
  3. Enable vertical Pod autoscaling on each Deployment. Ensure the autoscaling mode is set to Auto.
  4. Enable horizontal Pod autoscaling on each Deployment. Ensure the minimum number of Pods is lower than the currently configured amount in the Deployment.

Answer(s): A

Explanation:

Why option A is the optimal choice
Resource requests define the minimum CPU that a pod is guaranteed to receive. By setting a request a little higher than the observed average usage, the scheduler places the pod on a node that can meet that guarantee, while still leaving headroom for occasional spikes. Requests are independent of limits. A limit caps the maximum CPU a pod may consume; keeping the request slightly above normal usage prevents the pod from being throttled, yet it does not over-provision resources. Stateful workloads need predictable placement. Because the pods are stateful, they cannot be freely rescheduled by a horizontal autoscaler; a stable request ensures the pod stays on the same node without risking CPU starvation. Flexibility for higher load. If demand rises, the pod can burst beyond its request up to the limit, and the cluster can add more replicas only when the request-based utilization metric indicates sustained overload.
Why the other options are less suitable
Option B – requests equal to current limits would leave no headroom for bursts; any transient increase would cause the pod to be throttled, degrading performance and violating the goal of “maximum flexibility.” Option C – vertical Pod Autoscaler (VPA) in Auto mode continuously adjusts the request and limit values, but VPA is not recommended for stateful workloads because it may cause disruptive pod recreation and does not integrate cleanly with existing Deployments that already have limits configured. Option D – horizontal Pod Autoscaler (HPA) with a lower minimum would add or remove pods based on CPU, which is irrelevant for CPU-limited stateful services that must maintain a fixed identity (e.g., persistent storage). Reducing the minimum pod count could also cause under-replication during normal load.
Implementation guidance
1. Capture CPU usage over a representative period (e.g., 7-14 days) using Cloud Monitoring. 2. Set the request to approximately 10-20 % above the 95th-percentile usage. 3. Keep the existing limit unchanged or slightly higher to allow burst capability. 4. Validate that the pod’s CPU utilization stays within the desired range and that the scheduler does not over-provision nodes.


Reference:

Kubernetes Engine – Assigning CPU resources to containers : https://cloud.google.com/kubernetes-engine/docs/concepts/cpu-requests-limits Vertical Pod Autoscaler – Overview and best practices : https://cloud.google.com/kubernetes-engine/docs/concepts/vertical-pod-autoscaling (see “When to use VPA” section)



Company Overview -KnightMotives is a car manufacturer specializing in autonomous, self-driving vehicles, including Battery Electric Vehicles (BEVs), hybrids and traditional internal combustion engine (ICE) vehicles.
While KnightMotives has made strides with the in-vehicle experience in their BEV fleet, the hybrid and ICE vehicles have yet to implement these new systems and are viewed poorly by critics and drivers. The lack of modern in-vehicle technology in hybrid and ICE vehicles has resulted in declining sales and customer satisfaction. KnightMotives wants to modernize the consumer experience across all vehicles within five years Artificial Intelligence offers a unique opportunity to revolutionize the in-vehicle experience, as well as the shopping buying and service/maintenance experience. Investment in this new technology will require a shift in financial priorities on a global scale. KnightMotives also wants to improve their online ordering system, which is unreliable. Systems for customers to build their vehicle online for acquisition through a dealer are not delivering the data or reliability that dealers need, causing. A strain in the relationship between KnightMotives and dealers. Service technicians and sales staff need better tooling to enhance dealer successes, including built-to-order vehicles. Solution Concept -KnightMotives wants to shift from manufacturing cars to creating a complete and compelling “automotive experience.” Then strategy prioritizes delivering a consistent experience across all models, developing AI-powered features, generating new revenue from data monetization, adopting a digital focus to differentiate their brand from competitors, and developing better tools for mechanics and salespeople. Existing Technical Environment -KnightMotives's IT is largely on-premises with some applications on major cloud platforms. Their supply chain runs on an outdated mainframe, and Enterprise Resource Planning (ERP) is also outdated, making new promotions and dealer discounts difficult to implement. Dealers have no budget for new equipment. There is fragmentation across vehicles with multiple code bases, and significant technical debt from supporting backwards compatibility. Network connectivity to manufacturing plants and vehicle connectivity in rural areas are challenges. Business Requirements -Key business requirements include fostering a personalized relationship with the driver and delivering a cohesive experience across all models. Creating a better build-to-order model will reduce time on the lot and provide transparency for both dealers and customers. Additionally, KnightMotives seeks to monetize corporate data to finance new technology investments, as their current AI infrastructure is obsolete and corporate data remains siloed. Security is a paramount concern due to past data breaches Adherence to European Union (EU) data protection regulations, especially for emerging autonomous platforms, is critical. KnightMotives plans to make significant investments in fully autonomous driving capabilities, with initial implementation targeting regions with favorable regulatory environments. Prioritizing employee upskilling, attracting top-tier talent, and fostering better communication between business and technical teams are also critical objectives. Technical Requirements -•Modernizing the in-vehicle experience includes developing a consistent user experience (UX) that seamlessly integrates AI-powered features across all models, updating in-vehicle hardware and software in legacy models to support new UX features and AI capabilities, and ensuring reliable network connectivity, especially in rural areas, to support real-time AI features and data transmission. •Network upgrades are necessary to support increased data traffic and improve connectivity between plants and headquarters. •IT infrastructure modernization requires adopting a hybrid cloud strategy to leverage the benefits of both on-premises and cloud infrastructure, and gradually modernizing or replacing legacy systems to improve efficiency and agility. •Autonomous vehicle development and testing requires investing in cutting-edge AI and machine learning technologies, building a robust simulation environment, and ensuring compliance with evolving regulations related to autonomous vehicles. •Data monetization and insights requires implementing a robust data management platform, strict data security and privacy measures, and a scalable AI/ML infrastructure. •Increased focus on security and risk management involves implementing a comprehensive security framework to protect against cyber threats and data breaches, developing an incident response plan, and providing security awareness training to employees. •Providing a delightful experience for dealers and customers requires improving the online build-to-order system; developing modern dealer tools to streamline dealer operations, including sales, service, and inventory management; and implementing a comprehensive Customer Relationship Management (CRM) system to track customer interactions personalize experiences, and improve customer satisfaction. Executive Statement -KnightMotives is committed to enhancing safety and saving lives by leveraging an extensive body of data — encompassing driving, road conditions, behavioral studies, and crash safety statistics — to create compelling digital experiences for drivers. Our AI consistently outperforms national safety statistics, ensuring the unique and coveted KnightMotives experience is aligned across all our vehicle models. Michael Knight, KnightMotives CEO For this question, refer to the KnightMotives Automotive case study. KnightMotives has established a dedicated Google Cloud Interconnect with 99.99% availability between its headquarters and two different metropolitan areas corresponding to the us-central1 and us-east1 Google Cloud regions. To minimize cost and latency between these workloads, you want to ensure all workloads in Google Cloud are deployed in these two regions as the VLAN attachment for the Cloud Interconnect.
What should you do?

  1. Schedule an export of all assets via Asset Inventory into BigQuery. Schedule a daily Cloud Run function to query the export and send out an alert if resources are created in regions outside of the allowed list.
  2. Ensure all deployments are done through Infrastructure as Code using standardized Terraform modules. Configure the region variable of all resources with a default value corresponding to one of the allowed regions.
  3. Limit the Google Cloud VPC used by the Cloud Interconnect to only have subnets in the allowed regions.
  4. Configure the Resource Location Restriction constraint organization policy at the organization level, and ensure only the allowed regions are listed.

Answer(s): D

Explanation:

D: Configure the Resource Location Restriction constraint organization policy at the organization level, and ensure only the allowed regions are listed. Proactive Enforcement: The Resource Location Restriction organization policy (gcp.resourceLocations) is a native Google Cloud governance tool. Applying it at the organization level acts as a hard guardrail. It prevents any user, service account, or automated pipeline from spinning up compute, storage, or networking resources in non-approved regions.Direct Alignment: This satisfies KnightMotives' constraint by systematically forcing all resource creations into us-central1 and us-east1, eliminating accidental latency overheads and cloud spend outside their Cloud Interconnect landing zones.



Company Overview -KnightMotives is a car manufacturer specializing in autonomous, self-driving vehicles, including Battery Electric Vehicles (BEVs), hybrids and traditional internal combustion engine (ICE) vehicles.
While KnightMotives has made strides with the in-vehicle experience in their BEV fleet, the hybrid and ICE vehicles have yet to implement these new systems and are viewed poorly by critics and drivers. The lack of modern in-vehicle technology in hybrid and ICE vehicles has resulted in declining sales and customer satisfaction. KnightMotives wants to modernize the consumer experience across all vehicles within five years Artificial Intelligence offers a unique opportunity to revolutionize the in-vehicle experience, as well as the shopping buying and service/maintenance experience. Investment in this new technology will require a shift in financial priorities on a global scale. KnightMotives also wants to improve their online ordering system, which is unreliable. Systems for customers to build their vehicle online for acquisition through a dealer are not delivering the data or reliability that dealers need, causing. A strain in the relationship between KnightMotives and dealers. Service technicians and sales staff need better tooling to enhance dealer successes, including built-to-order vehicles. Solution Concept -KnightMotives wants to shift from manufacturing cars to creating a complete and compelling “automotive experience.” Then strategy prioritizes delivering a consistent experience across all models, developing AI-powered features, generating new revenue from data monetization, adopting a digital focus to differentiate their brand from competitors, and developing better tools for mechanics and salespeople. Existing Technical Environment -KnightMotives's IT is largely on-premises with some applications on major cloud platforms. Their supply chain runs on an outdated mainframe, and Enterprise Resource Planning (ERP) is also outdated, making new promotions and dealer discounts difficult to implement. Dealers have no budget for new equipment. There is fragmentation across vehicles with multiple code bases, and significant technical debt from supporting backwards compatibility. Network connectivity to manufacturing plants and vehicle connectivity in rural areas are challenges. Business Requirements -Key business requirements include fostering a personalized relationship with the driver and delivering a cohesive experience across all models. Creating a better build-to-order model will reduce time on the lot and provide transparency for both dealers and customers. Additionally, KnightMotives seeks to monetize corporate data to finance new technology investments, as their current AI infrastructure is obsolete and corporate data remains siloed. Security is a paramount concern due to past data breaches Adherence to European Union (EU) data protection regulations, especially for emerging autonomous platforms, is critical. KnightMotives plans to make significant investments in fully autonomous driving capabilities, with initial implementation targeting regions with favorable regulatory environments. Prioritizing employee upskilling, attracting top-tier talent, and fostering better communication between business and technical teams are also critical objectives. Technical Requirements -•Modernizing the in-vehicle experience includes developing a consistent user experience (UX) that seamlessly integrates AI-powered features across all models, updating in-vehicle hardware and software in legacy models to support new UX features and AI capabilities, and ensuring reliable network connectivity, especially in rural areas, to support real-time AI features and data transmission. •Network upgrades are necessary to support increased data traffic and improve connectivity between plants and headquarters. •IT infrastructure modernization requires adopting a hybrid cloud strategy to leverage the benefits of both on-premises and cloud infrastructure, and gradually modernizing or replacing legacy systems to improve efficiency and agility. •Autonomous vehicle development and testing requires investing in cutting-edge AI and machine learning technologies, building a robust simulation environment, and ensuring compliance with evolving regulations related to autonomous vehicles. •Data monetization and insights requires implementing a robust data management platform, strict data security and privacy measures, and a scalable AI/ML infrastructure. •Increased focus on security and risk management involves implementing a comprehensive security framework to protect against cyber threats and data breaches, developing an incident response plan, and providing security awareness training to employees. •Providing a delightful experience for dealers and customers requires improving the online build-to-order system; developing modern dealer tools to streamline dealer operations, including sales, service, and inventory management; and implementing a comprehensive Customer Relationship Management (CRM) system to track customer interactions personalize experiences, and improve customer satisfaction. Executive Statement -KnightMotives is committed to enhancing safety and saving lives by leveraging an extensive body of data — encompassing driving, road conditions, behavioral studies, and crash safety statistics — to create compelling digital experiences for drivers. Our AI consistently outperforms national safety statistics, ensuring the unique and coveted KnightMotives experience is aligned across all our vehicle models. Michael Knight, KnightMotives CEO For this question, refer to the KnightMotives Automotive case study. KnightMotives is managing supplier data and pricing in a central MySQL database at headquarters (HQ). Only personnel at HQ are allowed to change the data.
Each local plant stores a copy of the data in their own MySQL database, often using a different database schema or version. Every night a batch job exports any product or price updates in XML format from the central database at HQ and stores the updated data on a central FTP server. Each local plant must download this XML file and update their local system with the new information. The local data kept by some plants has become inconsistent with the source data due to XML parsing issues. HQ wants to easily verify that all changes are applied correctly at each plant.

  1. Create a Pub/Sub topic per supplier, and have HQ publish all changes related to the respective supplier in JSON format on that topic. Allow all plants to create Pub/Sub Pull subscription to receive messages for their suppliers and update their databases.
  2. Create a Pub/Sub topic per supplier, and have HQ publish all changes related to the respective supplier in JSON format on that topic. Allow all plants to create Pub/Sub Push subscription to receive messages for their suppliers and update their databases.
  3. Migrate the self-hosted MySQL database at HQ to Cloud SQL. Standardize the database schema across all plants, and configure the local databases as external read replicas in Cloud SQL.
  4. Migrate the self-hosted MySQL database at HQ to Cloud SQL. Configure Database Migration Service between Cloud SQL and the on-premises databases.
    When creating the migration job. choose continuous migration instead of one-time migration.

Answer(s): C

Explanation:

C: Migrate the self-hosted MySQL database at HQ to Cloud SQL. Standardize the database schema across all plants, and configure the local databases as external read replicas in Cloud SQL. Eliminates Parsing Errors: By standardizing the database schema and using native MySQL replication, KnightMotives completely eliminates brittle nighty batch exports, FTP transfers, and custom XML parsing scripts that were causing the data inconsistencies.



Company Overview -KnightMotives is a car manufacturer specializing in autonomous, self-driving vehicles, including Battery Electric Vehicles (BEVs), hybrids and traditional internal combustion engine (ICE) vehicles.
While KnightMotives has made strides with the in-vehicle experience in their BEV fleet, the hybrid and ICE vehicles have yet to implement these new systems and are viewed poorly by critics and drivers. The lack of modern in-vehicle technology in hybrid and ICE vehicles has resulted in declining sales and customer satisfaction. KnightMotives wants to modernize the consumer experience across all vehicles within five years Artificial Intelligence offers a unique opportunity to revolutionize the in-vehicle experience, as well as the shopping buying and service/maintenance experience. Investment in this new technology will require a shift in financial priorities on a global scale. KnightMotives also wants to improve their online ordering system, which is unreliable. Systems for customers to build their vehicle online for acquisition through a dealer are not delivering the data or reliability that dealers need, causing. A strain in the relationship between KnightMotives and dealers. Service technicians and sales staff need better tooling to enhance dealer successes, including built-to-order vehicles. Solution Concept -KnightMotives wants to shift from manufacturing cars to creating a complete and compelling “automotive experience.” Then strategy prioritizes delivering a consistent experience across all models, developing AI-powered features, generating new revenue from data monetization, adopting a digital focus to differentiate their brand from competitors, and developing better tools for mechanics and salespeople. Existing Technical Environment -KnightMotives's IT is largely on-premises with some applications on major cloud platforms. Their supply chain runs on an outdated mainframe, and Enterprise Resource Planning (ERP) is also outdated, making new promotions and dealer discounts difficult to implement. Dealers have no budget for new equipment. There is fragmentation across vehicles with multiple code bases, and significant technical debt from supporting backwards compatibility. Network connectivity to manufacturing plants and vehicle connectivity in rural areas are challenges. Business Requirements -Key business requirements include fostering a personalized relationship with the driver and delivering a cohesive experience across all models. Creating a better build-to-order model will reduce time on the lot and provide transparency for both dealers and customers. Additionally, KnightMotives seeks to monetize corporate data to finance new technology investments, as their current AI infrastructure is obsolete and corporate data remains siloed. Security is a paramount concern due to past data breaches Adherence to European Union (EU) data protection regulations, especially for emerging autonomous platforms, is critical. KnightMotives plans to make significant investments in fully autonomous driving capabilities, with initial implementation targeting regions with favorable regulatory environments. Prioritizing employee upskilling, attracting top-tier talent, and fostering better communication between business and technical teams are also critical objectives. Technical Requirements -•Modernizing the in-vehicle experience includes developing a consistent user experience (UX) that seamlessly integrates AI-powered features across all models, updating in-vehicle hardware and software in legacy models to support new UX features and AI capabilities, and ensuring reliable network connectivity, especially in rural areas, to support real-time AI features and data transmission. •Network upgrades are necessary to support increased data traffic and improve connectivity between plants and headquarters. •IT infrastructure modernization requires adopting a hybrid cloud strategy to leverage the benefits of both on-premises and cloud infrastructure, and gradually modernizing or replacing legacy systems to improve efficiency and agility. •Autonomous vehicle development and testing requires investing in cutting-edge AI and machine learning technologies, building a robust simulation environment, and ensuring compliance with evolving regulations related to autonomous vehicles. •Data monetization and insights requires implementing a robust data management platform, strict data security and privacy measures, and a scalable AI/ML infrastructure. •Increased focus on security and risk management involves implementing a comprehensive security framework to protect against cyber threats and data breaches, developing an incident response plan, and providing security awareness training to employees. •Providing a delightful experience for dealers and customers requires improving the online build-to-order system; developing modern dealer tools to streamline dealer operations, including sales, service, and inventory management; and implementing a comprehensive Customer Relationship Management (CRM) system to track customer interactions personalize experiences, and improve customer satisfaction. Executive Statement -KnightMotives is committed to enhancing safety and saving lives by leveraging an extensive body of data — encompassing driving, road conditions, behavioral studies, and crash safety statistics — to create compelling digital experiences for drivers. Our AI consistently outperforms national safety statistics, ensuring the unique and coveted KnightMotives experience is aligned across all our vehicle models. Michael Knight, KnightMotives CEO For this question, refer to the KnightMotives Automotive case study. KnightMotives wants to personalize the dealer experience for its customers and has decided to train its own AI models for personalized recommendations. The company will start collecting personally identifiable information (PII) from its customers to use as part of the models training data. KnightMotives wants to ensure maximum security and compliance worldwide. You need to ensure the data is encrypted both at rest and during AI model training without impacting the models’ accuracy.
What should you do?

  1. Store the training data in BigQuery using column-level encryption. Train the model using Confidential GKE Nodes.
  2. Store the training data in BigQuery using column-level encryption Train the model on VertexAI notebooks using customer-managed encryption keys.
  3. Process all data with Sensitive Data Protection’s de-identification service. Replace any PII with a random string before storing it. Train the model using Confidential GKE Nodes.
  4. Process all data with Sensitive Data Protection's de-identification service. Replace any PII with a random string before storing it. Train the model on VertexAI notebooks using customer-managed encryption keys.

Answer(s): A

Explanation:

Why option A is the optimal choice
End-to-end encryption – Column-level encryption in BigQuery protects the data at rest with customer-managed keys, satisfying global compliance (e.g., GDPR, CCPA).
Encryption in use – Training on Confidential GKE Nodes runs the workload inside Intel SGX-backed VMs, encrypting data while it is processed (memory-level protection). This meets the requirement to keep PII encrypted during model training without exposing it to the underlying host. Model accuracy preserved – Because the raw PII remains intact (only encrypted), the training data retains its full fidelity, avoiding the information loss that de-identification introduces. Compliance-ready – Confidential Computing is explicitly referenced in Google Cloud’s compliance documentation for handling sensitive data, making it easier to demonstrate adherence to EU data-protection rules and industry standards.
Why the other options are less suitable
Option B – While it also uses column-level encryption, training on Vertex AI notebooks does not provide a confidential-computing environment; the data is decrypted in the notebook runtime, exposing PII during model training. Option C – De-identification removes or randomizes PII, which destroys the richness needed for personalized AI recommendations and can degrade model accuracy. Encryption in use is still achieved via Confidential GKE, but the loss of data utility outweighs the security benefit. Option D – Combines de-identification (same accuracy-impacting issue) with Vertex AI notebooks, inheriting the lack of confidential-computing protection for the training phase.
Therefore, option A delivers maximum security (encryption at rest + in use) , preserves data utility for accurate model training , and aligns with global regulatory requirements.


Reference:

BigQuery column-level encryption : https://cloud.google.com/bigquery/docs/column-level-encryption Confidential GKE nodes (Confidential Computing) : https://cloud.google.com/kubernetes-engine/docs/how-to/confidential-computing
These links are official Google Cloud documentation and are currently active.



Viewing page 47 of 98
Viewing questions 231 - 235 out of 480 questions


Post your Comments and Discuss Google Google Cloud Architect Professional exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!