A news teed web service has the following code running on Google App Engine. During peak load, users report that they can see news articles they already viewed. What is the most likely cause of this problem?
Correct Answer: A
Question 142
As part of Dress4Win's plans to migrate to the cloud, they want to be able to set up a managed logging and monitoring system so they can handle spikes in their traffic load. They want to ensure that: * The infrastructure can be notified when it needs to scale up and down to handle the ebb and flow of usage throughout the day * Their administrators are notified automatically when their application reports errors. * They can filter their aggregated logs down in order to debug one piece of the application across many hosts Which Google StackDriver features should they use?
Correct Answer: A
Question 143
You want to enable your running Google Container Engine cluster to scale as demand for your application changes. What should you do?
Correct Answer: C
https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler To enable autoscaling for an existing node pool, run the following command: gcloud container clusters update [CLUSTER_NAME] --enable-autoscaling \--min-nodes 1 -- max-nodes 10 --zone [COMPUTE_ZONE] -- nodepool default-pool
Question 144
For this question, refer to the TerramEarth case study. You are asked to design a new architecture for the ingestion of the data of the 200,000 vehicles that are connected to a cellular network. You want to follow Google-recommended practices. Considering the technical requirements, which components should you use for the ingestion of the data?
The current Dress4Win system architecture has high latency to some customers because it is located in one data center. As of a future evaluation and optimizing for performance in the cloud, Dresss4Win wants to distribute its system architecture to multiple locations when Google cloud platform. Which approach should they use?
Correct Answer: A
Explanation/Reference: Dress4Win, B Testlet 1 Company Overview Dress4Win is a web-based company that helps their users organize and manage their personal wardrobe using a web app 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 freemium app model. The application has grown from a few servers in the founder's garage to several hundred servers and appliances in a colocated 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 moving their development and test environments. They are also 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. All servers run Ubuntu LTS v16.04. Databases: * MySQL. 1 server for user data, inventory, static data: - MySQL 5.8 - 8 core CPUs - 128 GB of RAM - 2x 5 TB HDD (RAID 1) * Redis 3 server cluster for metadata, social graph, caching. Each server is: - Redis 3.2 - 4 core CPUs - 32GB of RAM Compute: * 40 Web Application servers providing micro-services based APIs and static content. - Tomcat - Java - Nginx - 4 core CPUs - 32 GB of RAM * 20 Apache Hadoop/Spark servers: - Data analysis - Real-time trending calculations - 8 core CPUs - 128 GB of RAM - 4x 5 TB HDD (RAID 1) * 3 RabbitMQ servers for messaging, social notifications, and events: - 8 core CPUs - 32GB of RAM * Miscellaneous servers: - Jenkins, monitoring, bastion hosts, security scanners - 8 core CPUs - 32GB of RAM Storage appliances: * iSCSI for VM hosts * Fiber channel SAN - MySQL databases - 1 PB total storage; 400 TB available * NAS - image storage, logs, backups - 100 TB total storage; 35 TB available 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. Technical Requirements * Easily create non-production environments in the cloud. * Implement an automation framework for provisioning resources in cloud. * Implement a continuous deployment process for deploying applications to the on-premises datacenter or cloud. * Support failover of the production environment to cloud during an emergency. * Encrypt data on the wire and at rest. * Support multiple private connections between the production data center and cloud environment. Executive Statement Our investors are concerned about our ability to scale and contain costs with our current infrastructure. They are also concerned that a competitor could use a public cloud platform to offset their up-front investment and free them to focus on developing better features. Our traffic patterns are highest in the mornings and weekend evenings; during other times, 80% of our capacity is sitting idle. 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 for a public cloud strategy achieves a cost reduction between 30% and 50% over our current model.