Scribd
Upload
21 views2 pages

AWS_Interview_Problems

The document discusses AWS services for senior developers, focusing on EC2 scalability, storage options (S3, EBS, EFS), IAM best practices, serverless application design, and monitoring tools. It highlights the trade-offs of EC2 instance types, the distinct purposes of different storage services, and emphasizes security and monitoring strategies. Key tools mentioned include CloudWatch, X-Ray, and CloudTrail for effective resource management and performance tracking.

Uploaded by

pbecic
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
21 views2 pages

AWS_Interview_Problems

The document discusses AWS services for senior developers, focusing on EC2 scalability, storage options (S3, EBS, EFS), IAM best practices, serverless application design, and monitoring tools. It highlights the trade-offs of EC2 instance types, the distinct purposes of different storage services, and emphasizes security and monitoring strategies. Key tools mentioned include CloudWatch, X-Ray, and CloudTrail for effective resource management and performance tracking.

Uploaded by

pbecic
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

AWS for Strong Senior Developers

How does Amazon EC2 provide scalability and what are the trade-offs of
instance types?
 EC2 provides horizontal and vertical scalability via Auto Scaling Groups and instance
resizing.
 Trade-offs between instance types:
 General purpose (e.g., t3, m5) — balanced CPU/memory.
 Compute optimized (e.g., c5) — good for CPU-intensive workloads.
 Memory optimized (e.g., r5) — suitable for in-memory databases.
 Storage optimized (e.g., i3) — high IOPS and throughput.
 Spot and reserved instances help manage cost based on workload predictability.

What are the key differences between S3, EBS, and EFS in AWS?
 S3 (Simple Storage Service):
 Object storage — scalable, durable, used for static content, backups, logs.
 EBS (Elastic Block Store):
 Block storage for EC2 — persistent volumes attached to instances.
 EFS (Elastic File System):
 Shared file storage — accessible from multiple EC2 instances concurrently.
 Each serves a distinct storage access pattern and performance profile.

How does AWS IAM work and what are best practices for managing
permissions?
 IAM (Identity and Access Management) controls access to AWS resources.
 Best practices:
 Follow principle of least privilege — minimal required access.
 Use IAM roles instead of long-term credentials.
 Use IAM policies (inline or managed) for permission granularity.
 Enable MFA (multi-factor authentication).
 Monitor with IAM Access Analyzer and CloudTrail logs.

How would you design a serverless web application on AWS?


 Typical architecture:
 Frontend — S3 static hosting + CloudFront.
 API — Amazon API Gateway + AWS Lambda functions.
 Database — DynamoDB or Aurora Serverless.
 Authentication — Amazon Cognito.
 Benefits:
 Scalability, reduced ops overhead, pay-per-use model.
 Consider cold start latency and function timeouts as limitations.
What tools and strategies do you use for monitoring and logging in AWS
environments?
 Core tools:
 Amazon CloudWatch — metrics, logs, dashboards, alarms.
 AWS X-Ray — distributed tracing for microservices.
 CloudTrail — logs all API activity for auditing.
 Strategies:
 Centralize logs using CloudWatch Logs and subscriptions.
 Set alarms on critical metrics (e.g., CPU, latency, error rates).
 Integrate third-party tools like Datadog, New Relic, or ELK.

You might also like