# Amazon Managed Streaming for Apache Kafka

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/amazon-managed-streaming-for-apache-kafka

> Amazon Managed Streaming for Apache Kafka (Amazon MSK) is a fully managed service that enables you to build and run applications that use Apache Kafka to process streaming data without having to manage the Kafka infrastructure.

Practice exams covering Amazon Managed Streaming for Apache Kafka: [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [MLA-C02 AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 7 key features of Amazon Managed Streaming for Apache Kafka

Amazon Managed Streaming for Apache Kafka (MSK) is a fully managed service that simplifies building and running applications that use Apache Kafka to process streaming data, offering robust scalability, high-throughput, and low-latency streaming capabilities with built-in security features.

1. **Fully Managed Service**: Amazon MSK is a fully managed service that takes care of the underlying infrastructure, including the provisioning, configuration, and maintenance of Apache Kafka clusters. This allows developers to focus on building applications rather than managing complex Kafka infrastructure.
2. **Serverless Option**: Amazon MSK now offers a serverless option, allowing users to automatically scale the throughput and storage with no capacity planning required. This eliminates the need to manage and operate Kafka clusters, reducing operational complexity and cost.
3. **Highly Available and Secure**: MSK ensures high availability by automatically replicating data across multiple AWS Availability Zones. It also integrates with AWS security services such as AWS Identity and Access Management (IAM), Amazon VPC, and AWS Key Management Service (KMS), offering encryption in transit and at rest to ensure data is secured.
4. **Compatible with Open Source Tools**: Being fully compatible with Apache Kafka, MSK allows you to easily migrate your existing Kafka applications to AWS without needing to change your code. It also supports Apache Kafka community and third-party tools, which facilitates seamless integration with your existing applications.
5. **Monitoring and Logging**: Amazon MSK integrates with Amazon CloudWatch for monitoring and Amazon CloudWatch Logs for logging, providing deep insights into the performance and health of your Kafka clusters. This enables you to quickly detect and respond to issues.
6. **Easy to Start**: With just a few clicks in the AWS Management Console, you can create and configure an Amazon MSK cluster. This simplifies the process of setting up Apache Kafka on AWS and significantly reduces the time to get started.
7. **KRaft Metadata Management**: Amazon MSK supports KRaft metadata management, which propagates cluster metadata among Kafka controllers instead of ZooKeeper nodes. KRaft controllers are included at no additional cost and require no additional setup or management.

## Where Amazon Managed Streaming for Apache Kafka is used

Amazon Managed Streaming for Apache Kafka is used for building and running applications that process large streams of data in real time, such as log aggregation, stream processing, and event sourcing.

1. **Real-time Data Processing**: Amazon MSK is ideal for real-time data processing applications. It allows businesses to easily collect, process, and analyze streaming data in real time. This enables applications such as real-time analytics, dashboards, and alerting systems that need to process data the moment it arrives, providing timely insights and actions.
2. **Log Aggregation**: Organizations can use Amazon MSK to aggregate logs from various sources such as applications, systems, and services. This centralized approach to log aggregation simplifies log analysis and monitoring, making it easier to troubleshoot issues, monitor system health, and understand application behaviors across a distributed architecture.
3. **Event-Driven Architecture**: Amazon MSK supports building event-driven architectures, where producers generate events and consumers react to them, decoupling the producers and consumers of data. This architecture enhances scalability, flexibility, and responsiveness, enabling developers to build loosely coupled systems that can easily adapt to changing business requirements.
4. **Message Brokering**: MSK facilitates smooth message brokering between different parts of applications or between different applications. By acting as a scalable and highly available message queue, it can manage high-throughput, fault-tolerant messaging for inter-process communication, thereby ensuring reliable data delivery in complex distributed systems.
5. **Stream Analytics**: With Amazon MSK, organizations can perform stream analytics on data in motion. This is valuable for use cases that require real-time analysis of data streams to detect patterns, anomalies or to aggregate data over time. Stream analytics can be applied in scenarios such as fraud detection, monitoring IoT device states, or real-time marketing analytics.

## How Amazon Managed Streaming for Apache Kafka is priced

Amazon Managed Streaming for Apache Kafka (MSK) pricing is based on the chosen cluster configuration, including the number and type of broker nodes, the storage provisioned, and data transfer costs, with no upfront investment required.

- **On-Demand Pricing**: Pay for the capacity you use by the hour without any long-term commitments or upfront payments. Pricing varies based on the instance type and the region in which your MSK cluster is running.
- **Data Transfer Pricing**: Charges apply for data transferred in and out of Amazon MSK across the internet or between AWS regions. Data transfer within the same AWS region (inter-zone) involving MSK is also subject to charges, but transferring data between nodes within the same MSK cluster does not incur costs.
- **Standard Broker Storage**: Standard broker storage is charged for provisioned capacity in GB-months, calculated from the GB provisioned each hour.
- **Express Broker Storage and Ingestion**: Express brokers charge for storage actually used in GB-months and for data written at a per-GB rate billed at per-byte resolution.
- **Provisioned Storage Throughput**: Optional additional storage throughput is charged by provisioned MB/s per month, calculated from the throughput provisioned each hour per broker.
- **Tiered Storage**: Using the low-cost storage tier adds charges for low-cost storage capacity and data retrieved from that tier.
- **Multi-VPC Private Connectivity**: Optional multi-VPC private connectivity incurs an hourly charge per cluster and enabled authentication scheme, plus a per-GB data-processing charge. Standard AWS PrivateLink charges also apply to the managed VPC connections used by clients.
- **MSK Serverless**: MSK Serverless charges per cluster-hour and partition-hour, per GB written and read, and for storage consumed.
- **MSK Connect**: MSK Connect charges an hourly connector-usage rate billed at one-second resolution, based on worker count and worker size in MSK Connect Units (MCUs). Each MCU provides 1 vCPU and 4 GB of memory.
- **MSK Replicator**: MSK Replicator charges an hourly rate for each Replicator and a per-GB rate for data processed, including metadata and data filtered to prevent replication loops when identical topic names are used.
- **Data Delivery**: Native delivery from MSK to streaming tables in Amazon S3 Tables or general purpose Amazon S3 buckets is charged by the volume delivered, with pricing varying by destination type and no setup fees, minimum commitments, or upfront costs.

## Services Amazon Managed Streaming for Apache Kafka works with

MSK Connect lets you use Kafka Connect to configure data delivery to Amazon S3 and Amazon S3 Tables.

MSK Replicator can migrate data from existing Kafka deployments to Express brokers on Amazon MSK.

- **[Amazon Aurora](https://blowstack.com/tools/cloud-services-hub/amazon-aurora)**: Amazon MSK Connect can run Debezium source connectors that capture changes from Aurora databases and publish them to Kafka topics. This supports streaming inserts, updates, and deletes to downstream consumers.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Amazon MSK publishes cluster and broker metrics to CloudWatch for monitoring and alarms. MSK Provisioned clusters and MSK Connect connectors can also deliver logs to CloudWatch Logs.
- **[Amazon Data Firehose](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-firehose)**: Amazon MSK can serve as a source for Amazon Data Firehose delivery streams. Firehose reads records from Kafka topics and delivers them to supported destinations, with optional transformation, buffering, and format conversion.
- **[Amazon DocumentDB (with MongoDB compatibility)](https://blowstack.com/tools/cloud-services-hub/amazon-documentdb-(with-mongodb-compatibility))**: Amazon MSK Connect can run a MongoDB Kafka source connector configured to read Amazon DocumentDB change streams. Document changes are published to Kafka topics for downstream processing.
- **[Amazon DynamoDB](https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb)**: Amazon MSK Connect can run a DynamoDB sink connector to write Kafka topic records into DynamoDB tables. This lets applications maintain a low-latency key-value or document view of incoming events.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Amazon MSK Provisioned runs its brokers on managed EC2 compute capacity. Broker instance types determine the compute and memory available to the cluster, while MSK handles provisioning and maintenance.
- **[Amazon Elastic Block Store (Amazon EBS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-block-store-(amazon-ebs))**: Amazon MSK Standard brokers use EBS volumes for Kafka log storage. You can increase broker storage capacity and, for supported configurations, provision storage throughput.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: Amazon MSK can supply streaming records to Spark applications running on Amazon EMR. Spark Structured Streaming can consume Kafka topics, transform the records, and publish results back to MSK or another destination.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: Amazon MSK is a supported source for EventBridge Pipes. A pipe can consume Kafka records, filter or enrich them, and deliver them to a supported target without requiring a custom consumer application.
- **[Amazon Managed Grafana](https://blowstack.com/tools/cloud-services-hub/amazon-managed-grafana)**: Amazon MSK metrics can be visualized in Amazon Managed Grafana using its CloudWatch data source. Dashboards can track broker CPU, storage utilization, throughput, and consumer lag.
- **[Amazon Managed Service for Apache Flink](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-apache-flink)**: Amazon MSK topics can be sources and sinks for applications in Managed Service for Apache Flink. Applications can process events with stateful operations and publish results to Kafka with exactly-once guarantees when appropriately configured.
- **[Amazon Managed Service for Prometheus](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-prometheus)**: Amazon MSK open monitoring exposes broker metrics through JMX Exporter and Node Exporter endpoints. Prometheus collectors can scrape these endpoints and remote-write the metrics to Amazon Managed Service for Prometheus.
- **[Amazon Managed Workflows for Apache Airflow (Amazon MWAA)](https://blowstack.com/tools/cloud-services-hub/amazon-managed-workflows-for-apache-airflow-(amazon-mwaa))**: Amazon MWAA can use the Apache Airflow Amazon provider's MSK operators and hooks to create, inspect, and delete MSK clusters. This allows cluster lifecycle operations to be coordinated with other workflow tasks.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: Amazon OpenSearch Ingestion can consume records from Amazon MSK topics and index them in OpenSearch Service. Pipelines can parse, filter, and transform streaming records before indexing.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Amazon MSK Connect can run database source connectors, such as Debezium, to capture changes from supported RDS database engines. JDBC sink connectors can also write Kafka records into supported RDS databases.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: Amazon Redshift streaming ingestion reads records directly from Amazon MSK topics into materialized views. This makes Kafka events available for SQL analytics without first staging them in Amazon S3.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon MSK Connect can run S3 connectors that export Kafka records to S3 or import supported S3 data into Kafka. MSK can also deliver broker logs to S3, and MSK Connect loads custom connector plugins from S3.
- **[Amazon Timestream](https://blowstack.com/tools/cloud-services-hub/amazon-timestream)**: Amazon MSK Connect can run the Amazon Timestream sink connector to write Kafka records into Timestream tables. This supports collecting time-series events from Kafka for subsequent time-based queries.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon MSK places cluster connectivity in selected VPC subnets and uses security groups to control network access. Clients can connect privately, and supported provisioned clusters can optionally expose public endpoints.
- **[AWS Auto Scaling](https://blowstack.com/tools/cloud-services-hub/aws-auto-scaling)**: Amazon MSK integrates with Application Auto Scaling to increase broker storage automatically. You configure a target storage-utilization percentage and a maximum storage capacity for the scaling policy.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: CloudFormation can provision and manage Amazon MSK clusters, serverless clusters, configurations, and cluster policies. It also supports MSK Connect resources, allowing connectors and their configuration to be deployed as infrastructure as code.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: Amazon MSK integrates with CloudTrail to record control-plane API activity, including cluster creation and configuration changes. These events provide an audit trail of who performed management operations and when.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Config records supported Amazon MSK resource configurations and evaluates them against compliance rules. Managed rules can check settings such as encryption in transit and enhanced monitoring.
- **[AWS Database Migration Service (AWS DMS)](https://blowstack.com/tools/cloud-services-hub/aws-database-migration-service-(aws-dms))**: Amazon MSK can be a Kafka target for AWS DMS replication tasks. DMS publishes full-load data and ongoing database changes to Kafka topics for streaming consumers.
- **[AWS Fault Injection Service](https://blowstack.com/tools/cloud-services-hub/aws-fault-injection-simulator-(aws-fis))**: AWS Fault Injection Service can reboot brokers in an Amazon MSK Provisioned cluster as part of a controlled experiment. This lets you test how producers and consumers respond to broker failures and recovery.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: AWS Glue streaming ETL jobs can consume records from Amazon MSK and transform them for downstream destinations. MSK producers and consumers can also use AWS Glue Schema Registry to serialize records and manage schema compatibility.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: Amazon MSK uses IAM policies to authorize management operations and supports IAM authentication and authorization for Kafka clients. IAM access control can restrict actions such as connecting to a cluster, reading a topic, or writing records.
- **[AWS IoT Core](https://blowstack.com/tools/cloud-services-hub/aws-iot-core)**: The AWS IoT Core Kafka rule action publishes device messages directly to supported Amazon MSK clusters. Rules can select and transform MQTT message data before sending it to a Kafka topic.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: Amazon MSK uses KMS keys to encrypt cluster data at rest. You can choose a customer managed key to control key policies and audit key usage.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: Amazon MSK topics can trigger Lambda functions through event source mappings. Lambda manages polling and batching, invokes the function with Kafka records, and commits offsets after successful processing.
- **[AWS Managed Services (AMS)](https://blowstack.com/tools/cloud-services-hub/aws-managed-services-(ams))**: Amazon MSK is available through AMS Self-Service Provisioning in supported AMS managed accounts. This allows MSK resources to be provisioned within the AMS operational environment.
- **[AWS Marketplace](https://blowstack.com/tools/cloud-services-hub/aws-marketplace)**: AWS Marketplace offers Kafka connector products for use with Amazon MSK and MSK Connect. These connectors extend MSK pipelines to supported external databases, applications, and storage systems.
- **[AWS Private Certificate Authority](https://blowstack.com/tools/cloud-services-hub/aws-private-certificate-authority)**: Amazon MSK supports mutual TLS client authentication using certificates issued by AWS Private Certificate Authority. You associate trusted private certificate authorities with the cluster so it can authenticate connecting Kafka clients.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: Amazon MSK multi-VPC private connectivity uses AWS PrivateLink to connect clients in other VPCs to supported clusters. It provides private connectivity without requiring VPC peering or transit gateways.
- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: Amazon MSK uses Secrets Manager to store credentials for SASL/SCRAM authentication. Associating secrets with a cluster makes those credentials available for authenticating Kafka users.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: Security Hub includes controls that evaluate Amazon MSK security settings, such as encryption in transit and enhanced monitoring. Failed checks produce findings that can be reviewed alongside other security issues.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: Amazon MSK IAM authentication supports temporary AWS credentials, including credentials obtained by assuming an IAM role through STS. Kafka clients can use these credentials instead of long-lived access keys.
- **[AWS Step Functions](https://blowstack.com/tools/cloud-services-hub/aws-step-functions)**: Step Functions can call Amazon MSK management APIs through AWS SDK service integrations. Workflows can create a cluster, check its status, and coordinate subsequent setup or cleanup operations.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: Systems Manager Automation provides the AWSSupport-TroubleshootMSKNetworkConnectivity runbook for diagnosing connectivity between clients and Amazon MSK brokers. It checks relevant network configuration to help identify connection failures.

## What is Amazon Managed Streaming for Apache Kafka

Amazon Managed Streaming for Apache Kafka, often abbreviated as Amazon MSK, is an innovative service that provides a fully managed, highly available, and secure environment for running Apache Kafka. Apache Kafka, a prominent open-source platform, is designed for building real-time streaming data pipelines and applications.

Amazon MSK offers Provisioned and Serverless deployment options. With MSK Provisioned, you choose Standard or Express brokers and scale the cluster in units of brokers. MSK Serverless abstracts cluster scaling and management, so applications run without requiring you to provision, configure, or optimize clusters.

By handling data streams, it enables developers and organizations to publish, subscribe to, store, and process streams of records in real time. However, managing an Apache Kafka cluster in production can be complex and resource-intensive, requiring expertise in configuring, maintaining, and securing clusters, which is where Amazon MSK steps in to simplify the process. Amazon MSK essentially lifts the heavy lifting involved in managing Kafka clusters by automating tasks such as hardware provisioning, software patching, setup, and configuration. This automation serves to drastically reduce the operational load and complexity for developers and businesses, allowing them to focus more on the application development aspect rather than the underlying infrastructure management.

Furthermore, Amazon MSK is designed to be highly available and secure by default, providing multiple levels of security, including encryption in-transit and at-rest, VPC network isolation, IAM access controls, and private connectivity to help ensure that data is securely managed and processed. One of the significant benefits of Amazon MSK is its seamless integration with other AWS services, which allows developers to easily build and run applications that leverage rich data analytics, AI/ML, and other AWS services. For instance, integration with Amazon Kinesis makes it easier to ingest, buffer, and process data in real time, enhancing the capabilities of real-time analytics applications.

Additionally, Amazon CloudWatch integration provides comprehensive monitoring and logging capabilities, enabling users to efficiently observe the health and performance of their Kafka clusters and applications.

Cost management is another area where Amazon MSK shines. It offers a pay-as-you-go pricing model, which means customers pay only for the resources they use without upfront costs or commitments. This model provides the flexibility to scale resources up or down based on demand, optimizing cost efficiency.

In summary, Amazon Managed Streaming for Apache Kafka offers a fully managed service that simplifies the deployment, management, and scaling of Apache Kafka clusters. It reduces the operational burden on users while ensuring high availability, security, and integration with other AWS services, thereby enabling organizations to focus on innovation and application development rather than infrastructure management.

## Concepts related to Amazon Managed Streaming for Apache Kafka

- [Event Streaming](https://blowstack.com/tools/cloud-concepts-hub/event-streaming): Event streaming is the continuous publication, retention, and consumption of event records so independent applications can react to changes and replay event history.
- [Fan-In](https://blowstack.com/tools/cloud-concepts-hub/fan-in): Fan-in is a many-to-one data-flow pattern in which multiple producers or streams feed a shared destination or processing stage.
- [Message Ordering](https://blowstack.com/tools/cloud-concepts-hub/message-ordering): Message ordering is the preservation of a defined sequence of messages as they move through a distributed system.
- [Partitioning](https://blowstack.com/tools/cloud-concepts-hub/partitioning): Partitioning divides data or a stream of records into smaller, addressable groups so storage, ingestion, and processing can scale efficiently.
- [Schema Evolution](https://blowstack.com/tools/cloud-concepts-hub/schema-evolution): Schema evolution is the controlled modification of data structures over time while managing compatibility between existing data, producers, and consumers.

## Amazon Managed Streaming for Apache Kafka exam questions

Real practice exam questions on Amazon Managed Streaming for Apache Kafka, with the correct answer and its explanation.

### Question 1 (SAP-C03)

**Question:**

A logistics company publishes immutable shipment events as JSON records to Amazon Managed Streaming for Apache Kafka (Amazon MSK). Each event contains a carrier ID. Operations analysts need a SQL dashboard that joins recent events with carrier-reference data and targets event freshness of less than one minute.

Each night, a source system delivers a complete replacement carrier-reference dataset to Amazon S3. Existing carriers can have changed attributes, and some carriers are removed. Every dashboard query must see either the complete previous reference dataset or the complete replacement dataset, never an empty, partially loaded, or mixed-version dataset. The joins must use the reference dataset current when the query starts, including for events ingested before the nightly replacement.

The company has sufficient Amazon Redshift capacity and network connectivity. It wants native managed ingestion without maintaining a separate stream-processing application. Streaming events must not pass through an intermediate S3 delivery pipeline.

Which design meets these requirements?

**Correct answer:** Create an external schema for MSK and an automatically refreshed streaming materialized view that ingests only event data. Load each nightly reference snapshot into a staging table by using COPY and validate it. In one transaction, DELETE all rows from the live reference table and INSERT the staged rows, then commit. Expose an ordinary SQL view that joins the streaming materialized view with the live reference table.

**Explanation:** Native Redshift streaming ingestion reads MSK events into an automatically refreshed materialized view without S3 staging or a custom consumer. An ordinary SQL view performs enrichment using the reference data visible to each query. Loading and validating a staging table first, then replacing the live table's contents with transactional DELETE and INSERT statements, makes the reference replacement atomic. Queries see a consistent committed reference dataset.

### Question 2 (DEA-C01)

**Question:**

A payment platform publishes events to an Amazon Managed Streaming for Apache Kafka (Amazon MSK) topic by using Kafka transactions. Each transaction contains several related payment events. Producers commit successful transactions and abort transactions when validation fails.

A data ingestion application uses a native Kafka consumer with isolation.level=read_uncommitted. The application sometimes receives events from aborted transactions. It must ingest events from committed transactions continuously without exposing events from aborted or still-open transactions to its processing logic. The team wants to avoid implementing transaction filtering in application code.

Which change meets these requirements?

**Correct answer:** Set isolation.level=read_committed on the consumer, and retain the application's existing offset-management strategy.

**Explanation:** A read_committed consumer excludes aborted transactional records and reads transactional records only after their transactions commit. Reading is bounded by the last stable offset, preventing still-open transactions from being exposed to the application's processing logic.

### Question 3 (SAA-C03)

**Question:**

A company uses an Amazon MSK Provisioned cluster to ingest application events into a Kafka topic with 8 partitions. Producers distribute events evenly across all available partitions. A transformation application runs 24 identical consumer instances in one consumer group, but only 8 instances actively process events.

During sustained peaks, producers publish 9,000 events per second. Each consumer instance processes records sequentially and can transform at most 500 events per second. Testing confirms that broker CPU, storage throughput, and network bandwidth have sufficient spare capacity. Events do not require ordering, and the transformation code cannot be changed.

Which change will allow the application to keep up with peak traffic without having multiple consumer groups independently transform the same events?

**Correct answer:** Increase the topic's partition count to 24 and retain all 24 consumer instances in the existing consumer group.

**Explanation:** Within a consumer group, each partition is assigned to only one consumer at a time. Increasing to 24 evenly loaded partitions allows all 24 consumers to work concurrently, providing a total processing capacity of 12,000 events per second, which exceeds the 9,000-event-per-second peak.

## Practice Amazon Managed Streaming for Apache Kafka in a full exam

Questions on Amazon Managed Streaming for Apache Kafka in each practice exam, with every answer option and an explanation for each:

- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 7 questions
- [MLA-C02](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 3 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 2 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 2 questions

## Learn Amazon Managed Streaming for Apache Kafka in lessons

7 short lessons on Amazon Managed Streaming for Apache Kafka in 4 certification courses.

- MLA-C02: Amazon MSK: ingesting data through Kafka topics (Premium), https://app.blowstack.com/lessons/amazon-msk-ingesting-data-through-kafka-topics-mla-c02
- SAP-C03: Amazon Managed Streaming for Apache Kafka: replayable analytics streams (Premium), https://app.blowstack.com/lessons/amazon-managed-streaming-for-apache-kafka-replayable-analytics-streams-sap-c03
- DEA-C01: Amazon Kinesis Data Streams vs Amazon MSK: choosing a streaming service (Premium), https://app.blowstack.com/lessons/amazon-kinesis-data-streams-vs-amazon-msk-choosing-a-streaming-service-dea-c01
- SAA-C03: Amazon MSK: Kafka topics and partitions (Premium), https://app.blowstack.com/lessons/amazon-msk-kafka-topics-and-partitions-saa-c03
- MLA-C02: Amazon MSK vs. Amazon Kinesis Data Streams (Premium), https://app.blowstack.com/lessons/amazon-msk-vs-amazon-kinesis-data-streams-mla-c02
- DEA-C01: Amazon MSK: Kafka's partitioned log (Premium), https://app.blowstack.com/lessons/amazon-msk-kafka-s-partitioned-log-dea-c01
