Amazon Neptune for Social Graph Connections

SAA-C03 By islever Editorial Last updated

Determine appropriate data security controls.

Short answer

B Use Amazon Neptune to store the datasets with edges and vertices and query the data to find connections.

Question

A company has 5 TB of datasets. The datasets consist of 1 million user profiles and 10 million connections. The user profiles have connections as many-to-many relationships. The company needs a performance efficient way to find mutual connections up to five levels. Which solution will meet these requirements?
  1. Use an Amazon S3 bucket to store the datasets. Use Amazon Athena to perform SQL JOIN queries to find connections.
  2. Use Amazon Neptune to store the datasets with edges and vertices. Query the data to find connections. Correct Answer
  3. Use an Amazon S3 bucket to store the datasets. Use Amazon QuickSight to visualize connections.
  4. Use Amazon RDS to store the datasets with multiple tables. Perform SQL JOIN queries to find connections.

Key Takeaways

The question tests the ability to match complex relationship queries (social networks) with a NoSQL graph database, avoiding the performance traps of relational JOINs or object storage.

This page analyzes the optimal database solution for storing and querying highly connected social graph data, specifically identifying Amazon Neptune as the correct choice for handling many-to-many relationships.

Common mistake: Candidates often choose Amazon RDS because it is familiar, but SQL JOINs on millions of rows across multiple levels become prohibitively slow and resource-intensive for graph traversal.

Expert Analysis

Why the Answer Is Correct

Amazon Neptune is a fully managed graph database service optimized for connecting and querying highly connected datasets. The scenario describes user profiles and connections with many-to-many relationships, which is a classic graph use case. Neptune uses property graph models (Gremlin) or RDF (SPARQL) to traverse edges efficiently, allowing you to find mutual connections up to five levels without the exponential cost increase associated with deep SQL joins.

Why the Other Options Are Wrong

Option A (S3/Athena) involves scanning large objects and performing complex SQL joins, which is inefficient for iterative graph traversal. Option C (QuickSight) is a visualization tool, not a database engine capable of executing complex connection logic. Option D (RDS) uses relational tables; while possible, finding paths up to five levels deep requires recursive CTEs that perform poorly at scale compared to native graph indexing in Neptune.

Community Comment Notes

Community consensus strongly supports Neptune, with users noting that "everytime i see some social network related qns i immediately look for amazon neptune". Others highlight that "Neptune: A Graph database stores nodes and relationships instead of tables or documents", emphasizing the structural fit for this problem.

Exam Strategy

When you see keywords like 'connections', 'relationships', 'social network', or 'hops/levels' between entities, immediately consider Amazon Neptune. Relational databases struggle with variable-depth relationship queries, whereas graph databases are built for this specific workload.

Frequently Asked Questions

Why not use RDS with recursive SQL for connections?

RDS struggles with performance when traversing multiple levels of relationships due to the computational cost of repeated JOINs or recursive CTEs.

Is Athena suitable for graph traversal?

No, Athena is designed for serverless interactive SQL queries on S3 data, not for low-latency graph traversal algorithms.

More SAA-C03 FAQ →

Community Votes

B
100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. Kaula 👍 5 Answered B
    https://docs.aws.amazon.com/neptune/latest/userguide/notebooks-visualization.html
  2. alawada 👍 3 Answered B
    Neptune automatically scales storage and compute resources based on workload demands, ensuring optimal performance even as the dataset grows over time.
  3. sandordini 👍 3 Answered B
    Neptune: A Graph database stores nodes and relationships instead of tables or documents
  4. mk168898 👍 2 Answered B
    everytime i see some social network related qns i immediately look for amazon neptune

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

S3 Multi-Region Access Point and Replication Strategy

S-grade

Securing NLB with Security Groups for Minimal Change

S-grade

Most Cost-Effective 7-Year Retention for EBS Snapshots?

S-grade

AWS Forecast vs SageMaker for Time-Series Prediction

S-grade

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide