Week 2 – Linux + Cloud In-Depth Study
Guide
Comprehensive 7-Day Study Plan with Linux Basics, Troubleshooting, Azure SQL, AWS RDS,
Cloud Migration, Hands-on Labs, Real-Time Scenarios, Interview Q&A, and Quick Revision
Sheet.
Prepared for: Cloud & Database Administrator (3 Yrs Experience)
Table of Contents
1. Day 8–9: Linux Basics
2. Day 10: Linux Troubleshooting
3. Day 11–12: Azure SQL Database
4. Day 13: AWS RDS
5. Day 14: Cloud Migration
6. Quick Revision Sheet
Day 8–9: Linux Basics
Essential Commands
- `ls -l` → List files with details
- `pwd` → Print working directory
- `cd /path` → Change directory
- `df -h` → Show disk space usage in human readable format
- `du -sh *` → Disk usage of folders
- `top` or `htop` → View running processes
- `ps -ef | grep process` → Find process
- `chmod 755 [Link]` → Change permissions
- `chown user:group [Link]` → Change ownership
- `crontab -e` → Schedule tasks
Hands-on Task
1. Create a directory `/data/backups`.
2. Create a cron job to run a backup script every night at 2 AM.
3. Change permissions to make script executable.
4. Verify space usage using `df -h` and `du -sh`.
Real-Time Scenario
📌 A production server shows 95% disk usage.
- Run `du -sh *` to find which directory is large.
- Identify `/var/log/` consuming space.
- Compress and archive old logs.
- Set up logrotate to manage future growth.
Interview Q&A
Q: How do you find the top 5 CPU consuming processes?
A: Use `top` or `ps -eo pid,ppid,cmd,%mem,%cpu --sort=-%cpu | head -5`.
Checklist
☐ Practiced Linux commands
☐ Scheduled cron job
☐ Solved disk usage scenario
☐ Revised Q&A
Day 10: Linux Troubleshooting
- CPU Troubleshooting → `top`, `uptime`
- Memory Usage → `free -m`, `vmstat`
- Disk I/O → `iostat -xz 1`
- Logs → `/var/log/syslog`, `/var/log/messages`
Scenario
📌 High CPU reported on DB server:
- Run `top` to identify process.
- Use `kill -9 PID` if runaway process.
- Check queries running on DB with DMVs.
Checklist
☐ Practiced CPU/memory/disk checks
☐ Reviewed logs
☐ Simulated troubleshooting
Day 11–12: Azure SQL Database
Provisioning
Steps:
1. Go to Azure Portal → SQL Databases → Create.
2. Choose resource group, DB name, server, compute tier.
3. Configure DTU or vCore.
4. Set backup redundancy (LRS/GRS).
5. Deploy.
Scaling
In Azure SQL you can scale vertically (increase DTUs/vCores) or use elastic pools for
multiple DBs.
HA/DR
Azure SQL provides geo-replication and auto-failover groups for HA/DR.
Monitoring
Use Azure Monitor and Query Performance Insight to detect slow queries.
Scenario
📌 A critical DB must failover to secondary region.
- Enable geo-replication.
- Test failover using Azure Portal.
Interview Q&A
Q: Difference between DTU and vCore models?
A: DTU = bundled measure, vCore = CPU + memory model.
Day 13: AWS RDS
- Supports MySQL, PostgreSQL, SQL Server, Oracle.
- Snapshots (manual & automated).
- PIT Restore (up to 5 mins).
Hands-on
1. Launch RDS instance with Multi-AZ.
2. Take snapshot.
3. Perform PIT restore.
Scenario
📌 Primary instance fails → automatic failover to standby in Multi-AZ.
Day 14: Cloud Migration
Azure DMS / AWS DMS steps:
1. Assess source DB.
2. Create migration task.
3. Run continuous replication.
4. Perform cutover.
5. Validate data.
Checklist
☐ Reviewed migration steps
☐ Understood rollback strategy
☐ Practiced migration tool basics
Quick Revision Sheet – Week 2 Linux + Cloud
- Linux: df, du, top, ps, chmod, chown, crontab.
- Troubleshooting: CPU (top), Memory (free -m), Disk (iostat).
- Azure SQL: DTU vs vCore, Geo-replication, Failover groups.
- AWS RDS: Multi-AZ, Snapshots, PIT restore.
- Migration: DMS workflow = Assess → Migrate → Cutover.