A company is migrating an on-premises application to AWS. The company wants to use Amazon Redshift as a solution.
Which use cases are suitable for Amazon Redshift in this scenario? (Choose three.)
A company is migrating an on-premises application to AWS. The company wants to use Amazon Redshift as a solution.
Which use cases are suitable for Amazon Redshift in this scenario? (Choose three.)
Amazon Redshift is designed as a data warehouse solution, which suits specific use cases. It supports client-side and server-side encryption to protect data both during transit and at rest, making option B valid. Redshift is also optimized for running complex analytic queries on large datasets, which can be scheduled during specified hours, such as off-peak times, aligning with option C. Additionally, Redshift is built to scale massively and can support petabytes of data, which makes option E appropriate as it can handle very large scale analytics workloads efficiently.
Amazon Redshift is a data warehouse solution, so it is suitable for: -Supporting encryption (client-side and server-side) -Handling analytics workloads, especially during off-peak hours when the application is less active -Scaling to large amounts of data and high query volumes for analytics purposes The following options are incorrect because: A) Data APIs are not typically used with Redshift. It is more for running SQL queries and analytics. D) Redshift is not typically used for caching data. It is for analytics and data warehouse purposes. F) Redshift clusters do not create replicas in the management console. They are standalone clusters. you could create DR cluster from snapshot and restore to another region (automated or manual) but I do not think this what is meant in this option.
"Data APIs are not typically used with Redshift" -> "With the Data API, you can programmatically access data in your Amazon Redshift cluster from different AWS services such as AWS Lambda, Amazon SageMaker notebooks, AWS Cloud9, and also your on-premises applications using the AWS SDK. This allows you to build cloud-native, containerized, serverless, web-based, and event-driven applications on the AWS Cloud."
B. Supporting client-side and server-side encryption: Amazon Redshift supports both client-side and server-side encryption for improved data security. C. Building analytics workloads during specified hours and when the application is not active: Amazon Redshift is optimized for running complex analytic queries against very large datasets, making it a good choice for this use case. E. Scaling globally to support petabytes of data and tens of millions of requests per minute: Amazon Redshift is designed to handle petabytes of data, and to deliver fast query and I/O performance for virtually any size dataset.
Why E lol? It's a data warehouse! it has no need to support millions of requests, it is not mentioned anywhere (https://aws.amazon.com/redshift/features) In fact Redshift editor supports max 500 connections and workgroup support max 2000 connections at once, see it's quota page Redshift has a cache layer, D is correct
Amazon Redshift provides a Data API that you can use to painlessly access data from Amazon Redshift with all types of traditional, cloud-native, and containerized, serverless web services-based and event-driven applications. Amazon Redshift supports up to 500 concurrent queries per cluster, which may be expanded by adding more nodes to the cluster.
change to ABD To reduce query runtime and improve system performance, Amazon Redshift caches the results of certain types of queries in memory on the leader node. When a user submits a query, Amazon Redshift checks the results cache for a valid, cached copy of the query results. If a match is found in the result cache, Amazon Redshift uses the cached results and doesn't run the query. Result caching is transparent to the user.
CEF for me
https://docs.aws.amazon.com/redshift/latest/mgmt/welcome.html
Quote: "The Data API enables you to seamlessly access data from Redshift Serverless with all types of traditional, cloud-native, and containerized serverless web service-based applications and event-driven applications." at https://aws.amazon.com/blogs/big-data/use-the-amazon-redshift-data-api-to-interact-with-amazon-redshift-serverless/ (28/4/2023). Choose A. B and C are next chosen correct answers.
Typo, I want said "C and E are next chosen correct answers."
The key use cases for Amazon Redshift that fit this scenario are: B) Redshift supports both client-side and server-side encryption to protect sensitive data. C) Redshift is well suited for running batch analytics workloads during off-peak times without affecting OLTP systems. E) Redshift can scale to massive datasets and concurrent users to support large analytics workloads.
A: source https://aws.amazon.com/blogs/big-data/using-the-amazon-redshift-data-api-to-interact-with-amazon-redshift-clusters/ B: source: https://docs.aws.amazon.com/redshift/latest/mgmt/security-encryption.html C: not sure, but you can configure scheduled queries, but the remark " and when the application is not active " , that is not relevant. D: source https://docs.aws.amazon.com/redshift/latest/dg/c_challenges_achieving_high_performance_queries.html E: Scaling globally is not supported; redshift is only a regional service. F: only read replica is supported. So not a secondary replica of the cluster.
A, C, E are for data and Redshift is data warehouse. B is too generic of a choice D caching is not the main purpose of Redshift F replication is not main use of Redshift CE are easy Between AB, I chose A because Redshift supports data API and client-side encryption is not Redshift specific
A seems correct The Data API enables you to seamlessly access data from Redshift Serverless with all types of traditional, cloud-native, and containerized serverless web service-based applications and event-driven applications.
BCE, For B this is why https://docs.aws.amazon.com/redshift/latest/mgmt/security-encryption.html
Technically both options A and B apply, this is from the links below: A. You can access your Amazon Redshift database using the built-in Amazon Redshift Data API. https://docs.aws.amazon.com/redshift/latest/mgmt/data-api.html#:~:text=in%20Amazon%20Redshift-,Data%20API,-.%20Using%20this%20API B. You can encrypt data client-side and upload the encrypted data to Amazon Redshift. In this case, you manage the encryption process, the encryption keys, and related tools. https://docs.aws.amazon.com/redshift/latest/mgmt/security-encryption.html#:~:text=Use-,client%2Dside,-encryption%20%E2%80%93%20You%20can
A: https://aws.amazon.com/de/blogs/big-data/get-started-with-the-amazon-redshift-data-api/ B: https://docs.aws.amazon.com/redshift/latest/mgmt/security-encryption.html D: https://docs.aws.amazon.com/redshift/latest/dg/c_challenges_achieving_high_performance_queries.html#result-caching Not C: Redshift is a Data Warehouse; you can use that for analytics, but it is not directly related to an "application" Not E: "Petabytes of data" yes, but "tens of millions of requests per minute" is not a typical feature of Redshift Nor F: Replicas are not a Redshift feature
Redshift is OLAP(online analytical processing) so D is wrong, "when the application is not active"
*C is wrong
The following are obviously incorrect: (D) Redshift is not as suitable as ElastiCache for caching. (F) A secondary replica of the cluster is not supported. The debate is between BCE & ACE or simplified, between A & C. (A) is incorrect bc there is a difference btw Amazon Redshift Data API & API Gateway. API Gateway supports containerized and serverless workloads, as well as web applications. Amazon Redshift Data API is a built in API to access Redshift data with web services–based applications, including AWS Lambda, Amazon SageMaker notebooks, and AWS Cloud9. https://aws.amazon.com/blogs/big-data/build-a-serverless-analytics-application-with-amazon-redshift-and-amazon-api-gateway/ (B) is correct. You have the following options of protecting data at rest in Amazon Redshift. Use server-side encryption OR use client-side encryption https://docs.aws.amazon.com/redshift/latest/mgmt/security-encryption.html
Found this related to A -- but specific to Redshift Serverless - but should qualify as a Redshift use case The Data API enables you to seamlessly access data from Redshift Serverless with all types of traditional, cloud-native, and containerized serverless web service-based applications and event-driven applications. https://www.amazonaws.cn/en/blog-selection/use-the-amazon-redshift-data-api-to-interact-with-amazon-redshift-serverless/