Your operations team currently stores 10 TB of data in an object storage service from a third-party provider. They want to move this data to a Cloud Storage bucket as quickly as possible, following Google-recommended practices. They want to minimize the cost of this data migration. Which approach should they use?

As a cloud architect, you're helping a large organization deploy an update to their mission-critical application on App Engine. The application is used 24/7 by users worldwide, and it is crucial that the update does not affect application availability or user experience. Which of the following deployment strategies should you recommend?

You want to optimize the performance of an accurate, real-time, weather-charting application. The data comes from 50,000 sensors sending 10 readings a second, in the format of a timestamp and sensor reading.

Where should you store the data?

Introductory Info Company overview -

TerramEarth manufactures heavy equipment for the mining and agricultural industries. They currently have over 500 dealers and service centers in 100 countries.

Their mission is to build products that make their customers more productive.

Solution concept -

There are 2 million TerramEarth vehicles in operation currently, and we see 20% yearly growth. Vehicles collect telemetry data from many sensors during operation. A small subset of critical data is transmitted from the vehicles in real time to facilitate fleet management. The rest of the sensor data is collected, compressed, and uploaded daily when the vehicles return to home base. Each vehicle usually generates 200 to 500 megabytes of data per day.

Existing technical environment -

TerramEarth's vehicle data aggregation and analysis infrastructure resides in Google Cloud and serves clients from all around the world. A growing amount of sensor data is captured from their two main manufacturing plants and sent to private data centers that contain their legacy inventory and logistics management systems. The private data centers have multiple network interconnects configured to Google Cloud. The web frontend for dealers and customers is running in

Google Cloud and allows access to stock management and analytics.

Business requirements -

* Predict and detect vehicle malfunction and rapidly ship parts to dealerships for just-in-time repair where possible.

* Decrease cloud operational costs and adapt to seasonality.

* Increase speed and reliability of development workflow.

* Allow remote developers to be productive without compromising code or data security.

* Create a flexible and scalable platform for developers to create custom API services for dealers and partners.

Technical requirements -

* Create a new abstraction layer for HTTP API access to their legacy systems to enable a gradual move into the cloud without disrupting operations.

* Modernize all CI/CD pipelines to allow developers to deploy container-based workloads in highly scalable environments.

* Allow developers to run experiments without compromising security and governance requirements.

* Create a self-service portal for internal and partner developers to create new projects, request resources for data analytics jobs, and centrally manage access to the API endpoints.

* Use cloud-native solutions for keys and secrets management and optimize for identity-based access.

* Improve and standardize tools necessary for application and network monitoring and troubleshooting.

Executive statement -

Our competitive advantage has always been our focus on the customer, with our ability to provide excellent customer service and minimize vehicle downtimes.

After moving multiple systems into Google Cloud, we are seeking new ways to provide best-in-class online fleet management services to our customers and improve operations of our dealerships. Our 5-year strategic plan is to create a partner ecosystem of new products by enabling access to our data, increasing autonomous operation capabilities of our vehicles, and creating a path to move the remaining legacy systems to the cloud. Question For this question, refer to the TerramEarth case study. You are migrating a Linux-based application from your private data center to Google Cloud. The

TerramEarth security team sent you several recent Linux vulnerabilities published by Common Vulnerabilities and Exposures (CVE). You need assistance in understanding how these vulnerabilities could impact your migration. What should you do? (Choose two.)

Introductory Info Company Overview -

Dress4Win is a web-based company that helps their users organize and manage their personal wardrobe using a website and mobile application. The company also cultivates an active social network that connects their users with designers and retailers. They monetize their services through advertising, e-commerce, referrals, and a premium app model.

Company Background -

Dress4Win's application has grown from a few servers in the founder's garage to several hundred servers and appliances in a collocated data center. However, the capacity of their infrastructure is now insufficient for the application's rapid growth. Because of this growth and the company's desire to innovate faster,

Dress4Win is committing to a full migration to a public cloud.

Solution Concept -

For the first phase of their migration to the cloud, Dress4Win is considering moving their development and test environments. They are also considering building a disaster recovery site, because their current infrastructure is at a single location. They are not sure which components of their architecture they can migrate as is and which components they need to change before migrating them.

Existing Technical Environment -

The Dress4Win application is served out of a single data center location.

Databases:

- MySQL - user data, inventory, static data

- Redis - metadata, social graph, caching

Application servers:

- Tomcat - Java micro-services

- Nginx - static content

- Apache Beam - Batch processing

Storage appliances:

- iSCSI for VM hosts

- Fiber channel SAN - MySQL databases

- NAS - image storage, logs, backups

Apache Hadoop/Spark servers:

- Data analysis

- Real-time trending calculations

MQ servers:

- Messaging

- Social notifications

- Events

Miscellaneous servers:

- Jenkins, monitoring, bastion hosts, security scanners

Business Requirements -

Build a reliable and reproducible environment with scaled parity of production.

Improve security by defining and adhering to a set of security and Identity and Access Management (IAM) best practices for cloud.

Improve business agility and speed of innovation through rapid provisioning of new resources.

Analyze and optimize architecture for performance in the cloud.

Migrate fully to the cloud if all other requirements are met.

Technical Requirements -

Evaluate and choose an automation framework for provisioning resources in cloud.

Support failover of the production environment to cloud during an emergency.

Identify production services that can migrate to cloud to save capacity.

Use managed services whenever possible.

Encrypt data on the wire and at rest.

Support multiple VPN connections between the production data center and cloud environment.

CEO Statement -

Our investors are concerned about our ability to scale and contain costs with our current infrastructure. They are also concerned that a new competitor could use a public cloud platform to offset their up-front investment and freeing them to focus on developing better features.

CTO Statement -

We have invested heavily in the current infrastructure, but much of the equipment is approaching the end of its useful life. We are consistently waiting weeks for new gear to be racked before we can start new projects. Our traffic patterns are highest in the mornings and weekend evenings; during other times, 80% of our capacity is sitting idle.

CFO Statement -

Our capital expenditure is now exceeding our quarterly projections. Migrating to the cloud will likely cause an initial increase in spending, but we expect to fully transition before our next hardware refresh cycle. Our total cost of ownership (TCO) analysis over the next 5 years puts a cloud strategy between 30 to 50% lower than our current model. Question As part of their new application experience, Dress4Wm allows customers to upload images of themselves.

The customer has exclusive control over who may view these images.

Customers should be able to upload images with minimal latency and also be shown their images quickly on the main application page when they log in.

Which configuration should Dress4Win use?