nerdexam
Amazon

DBS-C01 · Question #357

A company has a reporting application that runs on an Amazon EC2 instance in an isolated developer account on AWS. The application needs to retrieve data during non-peak company hours from an Amazon…

The correct answer is A. Add an inbound security group rule to the database security group that allows access from the. To complete connectivity for an EC2 instance in a developer account to an Aurora PostgreSQL database in a production account after VPC peering and route tables are configured, the database administrator must configure the database's security group.

Submitted by yousef_jo· Mar 6, 2026Database Security

Question

A company has a reporting application that runs on an Amazon EC2 instance in an isolated developer account on AWS. The application needs to retrieve data during non-peak company hours from an Amazon Aurora PostgreSQL database that runs in the company's production account. The company's security team requires that access to production resources complies with AWS best security practices. A database administrator needs to provide the reporting application with access to the production database. The company has already configured VPC peering between the production account and developer account. The company has also updated the route tables in both accounts with the necessary entries to correctly set up VPC peering. What must the database administrator do to finish providing connectivity to the reporting application?

Options

  • AAdd an inbound security group rule to the database security group that allows access from the
  • BAdd an outbound security group rule to the database security group that allows access from the
  • CAdd an inbound security group rule to the database security group that allows access from the
  • DAdd an inbound security group rule to the database security group that allows access from the

How the community answered

(37 responses)
  • A
    76% (28)
  • B
    14% (5)
  • C
    8% (3)
  • D
    3% (1)

Why each option

To complete connectivity for an EC2 instance in a developer account to an Aurora PostgreSQL database in a production account after VPC peering and route tables are configured, the database administrator must configure the database's security group.

AAdd an inbound security group rule to the database security group that allows access from theCorrect

To establish connectivity to the Aurora PostgreSQL database, an inbound security group rule must be added to the database's security group. This rule specifically allows incoming traffic on the PostgreSQL port (e.g., 5432) from the security group associated with the EC2 instance, enabling the application to initiate connections to the database.

BAdd an outbound security group rule to the database security group that allows access from the

An outbound security group rule on the database security group controls traffic originating *from* the database, not traffic *to* the database for initial connection setup.

CAdd an inbound security group rule to the database security group that allows access from the

Without the full choice text, it is not possible to determine the specific technical reason, but choice A explicitly addresses the inbound access required.

DAdd an inbound security group rule to the database security group that allows access from the

Without the full choice text, it is not possible to determine the specific technical reason, but choice A explicitly addresses the inbound access required.

Concept tested: VPC peering security group configuration for RDS/Aurora access

Source: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.ConnectRG.html

Topics

#VPC peering#security groups#Aurora PostgreSQL#cross-account access

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full DBS-C01 Practice