You are building a new API. You want to minimize the cost of storing and reduce the latency of serving images.
Which architecture should you use?
You are building a new API. You want to minimize the cost of storing and reduce the latency of serving images.
Which architecture should you use?
For minimizing the cost of storing and reducing the latency of serving images, the most appropriate option is a Cloud Content Delivery Network (CDN) backed by Cloud Storage. Cloud Storage provides a cost-effective and scalable storage solution for images, while the CDN reduces latency by caching and serving content from locations closer to the user. This combination ensures both low storage costs and fast delivery times for the images, making it the ideal architecture for this scenario.
Answer D) seems more suitable as Cloud Storage has low cost and CDN provides low serving latency
Agree this is best answer
But shouldn't there be something (like Compute Engine / App Engine) between the CDN and Cloud Store? Thanks ?
For me A. With CDN i can't write API
Answer is D since CDN reduces latency and Cloud Storage is used for images
But shouldn't there be something (like Compute Engine / App Engine) between the CDN and Cloud Store? Thanks
not neeeded see the docsthey say: https://cloud.google.com/cdn/docs/overview That the CDN can be backed by cloud storage buckets
D is correct
D is more suitable answer in this case.
D - Cloud CDN
D. Cloud Content Delivery Network (CDN) backed by Cloud Storage. A Cloud CDN is a content delivery network that uses Google's globally distributed edge points of presence to accelerate content delivery for websites and applications served out of Google Cloud. Cloud CDN stores and serves content from Google Cloud Storage, which allows for efficient and low-cost storage of images, as well as low latency in serving the images. The other options do not mention low latency or cost-effective storage as their primary benefits.
C (Transfer Appliance backed by Cloud Filestore) may not be suitable because it is not designed for serving images, but rather for transferring large amounts of data.
A (App Engine backed by Cloud Storage) may not be suitable because App Engine may not be optimized for serving images, and it may not offer the lowest cost or latency for serving images. Option B (Compute Engine backed by Persistent Disk) may not be suitable because it may not offer the lowest cost for storing images, and it may not offer the lowest latency for serving images.
D (Cloud Content Delivery Network (CDN) backed by Cloud Storage) is the most suitable option because CDN is optimized for serving images and other static content, and it can reduce the latency of serving images by storing copies of the images closer to the users who are requesting them. In addition, using Cloud Storage to store the images can help minimize the cost of storing the images.
CDN is appropriated to serve static files. The right answer is B)
Answer is D
"Cloud CDN content can be sourced from various types of backends: ... Buckets in Cloud Storage Answer is D
I think A because CDN doesn't relate to API but to static resources
A is correct, the rest how can you write an API?
D is the best option here as CDN will reduce latency.
D. Cloud Content Delivery Network (CDN) backed by Cloud Storage Using Cloud CDN backed by Cloud Storage is a cost-effective and performance-optimized solution for storing and serving images. Cloud Storage provides a durable and highly available object storage solution, while Cloud CDN leverages Google's globally distributed edge points of presence to cache and serve content closer to users, reducing latency.
The best architecture for minimizing storage cost and reducing latency for serving images is D. Cloud Content Delivery Network (CDN) backed by Cloud Storage . Here's why: Cloud CDN: CDNs are designed to cache content closer to users, significantly reducing latency. They also handle the majority of image requests, reducing the load on your backend servers. Cloud Storage: Cloud Storage is a cost-effective and scalable object storage solution. It's ideal for storing images and other static content. Cost-Effective: CDNs are optimized for serving static content, making them more cost-effective than running your own servers. Cloud Storage offers tiered pricing, allowing you to optimize storage costs based on access frequency.
Why other options are less suitable: A. App Engine backed by Cloud Storage: While App Engine can serve images from Cloud Storage, it's not as efficient as a CDN for serving static content. App Engine instances are designed for dynamic applications, and serving images can be resource-intensive. B. Compute Engine backed by Persistent Disk: This approach is more expensive and less efficient than using a CDN. Persistent disks are designed for persistent data, not for serving static content at high volumes. C. Transfer Appliance backed by Cloud Filestore: Transfer Appliance is for bulk data transfers, not for serving images. Cloud Filestore is a managed file system, not optimized for serving static content. In summary: A CDN backed by Cloud Storage provides the best combination of cost-effectiveness, low latency, and scalability for serving images. It allows you to offload the majority of image requests to the CDN, reducing the load on your backend servers and minimizing storage costs.