Senior questions
Cloud 2 questions
- #1Build a Serverless API with Lambda, API Gateway, and DynamoDB
An internal serverless API is needed for order management. Orders must be stored in a DynamoDB table with all access routed through a Lambda function — never direct database access. The Lambda execution role should follow least-privilege principles, limiting permissions to only what's necessary.
- #2Deploy an Internal Web Application with VPC, EC2, ALB, and Route 53
You need to deploy a web application accessible only within a VPC. EC2 instances run in private subnets behind an Application Load Balancer in public subnets. A startup script at
/tmp/userdata.shruns a simple HTTP server with a/healthendpoint on port 80.
Containers 1 question
- #3Docker Network Configuration Fix
You have created a macvlan network called
mymacvlanto give containers their own MAC addresses on the physical network. However, containersmac1andmac2started on this network cannot ping the host or the gateway at192.168.50.1.
Kubernetes 1 question
- #4CRD Schema Validation
You manage a CustomResourceDefinition (CRD) for "Widgets". Currently, the API allows users to create widgets with missing or invalid configuration, which causes the controller to crash.
Linux 4 questions
- #5Automated Archive and Retention
Configuration files in
/etcare at risk of being lost due to accidental changes or deletions, and there's currently no automated backup process in place. - #6Manage Service Failure Recovery
You have a shell script at
/usr/local/bin/check_app.shthat runs periodically and exits with a non-zero code. The script is currently failing due to a simulated error condition. - #7Rapid Disk Growth on Var
Disk usage on the
/varpartition is at 92% and increasing rapidly. You need to identify the largest files consuming space and determine if they're actively used by processes or need log rotation. - #8Trace Process Service Ownership
A process is consuming excessive resources, but its origin is unclear.
Networking 1 question
- #9Nginx Rate Limit Calculation
Your Nginx web server has recently experienced performance issues caused by excessive traffic from a few aggressive clients. You've decided to enable rate limiting based on the recent traffic pattern. To determine the proper limit, you first need to analyze request frequency.