Drag a concept onto its matching description — or click a concept then click the description.
Concepts
Matches
3306
6379
5432
11211
1521
DVA-C02 Deployment Practice Question
Match each AWS service to its port number (if applicable).
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Amazon RDS (MySQL engine): 3306
Default ports are important for configuring security groups and connecting to databases.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Amazon RDS (MySQL engine): 3306
Why this is correct
When you provision an Amazon RDS instance running the MySQL engine, the DB engine listens on TCP port 3306 by default, matching the standard MySQL community server port. This means your connection string, client tool, and VPC security group inbound rule must all reference port 3306 to reach the database. The RDS service deliberately preserves the familiar MySQL port to make connections feel like a native on-prem MySQL deployment.
- ✓
Amazon Redshift: 5439
Why this is correct
Amazon Redshift uses 5439 as its default port for JDBC, ODBC, and psql-style connections, not the 5432 you might expect from its PostgreSQL lineage. When you create a Redshift cluster, the endpoint is provided as a hostname with this port, and you must open inbound TCP 5439 in the cluster's security group. Even though Redshift is built on a fork of PostgreSQL 8.x, AWS assigned a distinct port to avoid conflicts and signal its unique mass-parallel-processing architecture.
- ✓
Amazon RDS (PostgreSQL engine): 5432
Why this is correct
Amazon RDS for PostgreSQL adheres to the IANA-registered default port 5432, which is the same port used by a standard PostgreSQL server. When connecting with pgAdmin, psql, or any application driver, you specify the endpoint plus 5432, and the RDS security group must allow traffic on that port. This consistency reduces friction for developers moving from a self-managed PostgreSQL database to RDS.
- ✗
Amazon RDS (MySQL engine): 5439
Why it's wrong here
Setting an RDS MySQL connection to port 5439 fails because 5439 is reserved for Amazon Redshift, not for MySQL. The MySQL engine in RDS listens on 3306, so a client attempting 5439 will receive a connection refused or timeout error from the load balancer or TCP layer. This mix-up typically happens when a user works with both Redshift and MySQL and accidentally cross-applies the Redshift endpoint port to the RDS MySQL database.
- ✗
Amazon Redshift: 3306
Why it's wrong here
Attempting to connect to Amazon Redshift on port 3306 is invalid because 3306 belongs to MySQL and MariaDB, not Redshift. Redshift clusters are provisioned with the listener on 5439, so even if you enable inbound security group rules for 3306, the request never reaches the query engine. The error will be a timeout or 'could not connect to server' as the cluster's network interface simply has no service bound to that port.
Go deeper
Related to this question
About these practice questions
This DVA-C02 question is part of Courseiva's 724-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DVA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DVA-C02 exam.