PK `\_rels/PK `\ docProps/PK `\ppt/PK `\ ppt/_rels/PK `\ ppt/charts/PK `\ppt/charts/_rels/PK `\ppt/embeddings/PK `\ ppt/media/PK `\ppt/slideLayouts/PK `\ppt/slideLayouts/_rels/PK `\ppt/slideMasters/PK `\ppt/slideMasters/_rels/PK `\ ppt/slides/PK `\ppt/slides/_rels/PK `\ ppt/theme/PK `\ppt/notesMasters/PK `\ppt/notesMasters/_rels/PK `\ppt/notesSlides/PK `\ppt/notesSlides/_rels/PK `\撾[Content_Types].xml PK `\]] _rels/.rels PK `\|--docProps/app.xml 0 0 Microsoft Office PowerPoint On-screen Show (16:9) 0 114 114 0 0 false Fonts Used 2 Theme 1 Slide Titles 114 Arial Calibri Office Theme Slide 1Slide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Slide 22Slide 23Slide 24Slide 25Slide 26Slide 27Slide 28Slide 29Slide 30Slide 31Slide 32Slide 33Slide 34Slide 35Slide 36Slide 37Slide 38Slide 39Slide 40Slide 41Slide 42Slide 43Slide 44Slide 45Slide 46Slide 47Slide 48Slide 49Slide 50Slide 51Slide 52Slide 53Slide 54Slide 55Slide 56Slide 57Slide 58Slide 59Slide 60Slide 61Slide 62Slide 63Slide 64Slide 65Slide 66Slide 67Slide 68Slide 69Slide 70Slide 71Slide 72Slide 73Slide 74Slide 75Slide 76Slide 77Slide 78Slide 79Slide 80Slide 81Slide 82Slide 83Slide 84Slide 85Slide 86Slide 87Slide 88Slide 89Slide 90Slide 91Slide 92Slide 93Slide 94Slide 95Slide 96Slide 97Slide 98Slide 99Slide 100Slide 101Slide 102Slide 103Slide 104Slide 105Slide 106Slide 107Slide 108Slide 109Slide 110Slide 111Slide 112Slide 113Slide 114 PptxGenJS false false false 16.0000 PK `\=docProps/core.xml PptxGenJS Presentation PptxGenJS Presentation PptxGenJS PptxGenJS 1 2026-07-16T12:05:44Z 2026-07-16T12:05:44Z PK `\k@@ppt/_rels/presentation.xml.rels PK `\Oݨ ppt/theme/theme1.xmlPK `\9ppt/presentation.xml PK `\Xppt/presProps.xml PK `\ppt/tableStyles.xml PK `\D >00ppt/viewProps.xml PK `\H7t!ppt/slideLayouts/slideLayout1.xml PK `\ђ77,ppt/slideLayouts/_rels/slideLayout1.xml.rels PK `\Zo4o4ppt/slides/slide1.xml AITrustEDTrusted AI & Cloud Education for Every IndustryAWS DevOps Engineer45-Day Job-Ready ProgramFrom Linux fundamentals to production-grade CI/CD, containers, Infrastructure as Code and Kubernetes — a complete, hands-on path to your first Cloud / DevOps role.45Days67.5Training Hours10Modules1Capstone Projectwww.aitrusted.in1PK `\3 ppt/slides/_rels/slide1.xml.rels PK `\.ppt/notesSlides/notesSlide1.xml 1PK `\:A*ppt/notesSlides/_rels/notesSlide1.xml.rels PK `\c33ppt/slides/slide2.xml About AITrustEDTrusted AI & Cloud Education for Every Industry AITrustED designs and delivers industry-oriented AI, Cloud, and DevOps training for engineering colleges, corporate teams, and career-switchers.Programs are built around one goal: making learners genuinely job-ready — not just certificate-ready.Every module blends conceptual clarity with real hands-on labs mirroring day-one tasks at a DevOps desk.Curriculum is refreshed continuously to track the AWS console, tooling versions, and current hiring bar for Cloud/DevOps roles.Delivered in both classroom (engineering faculty & student batches) and corporate upskilling formats. aitrusted.inAI Literacy & Prompt EngineeringClaude AI Enablement ProgramsPower BI & Data AnalyticsCloud & DevOps (AWS / Azure / GCP)Faculty Development Programs (FDP)Corporate Upskilling CohortsAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program2PK `\2- ppt/slides/_rels/slide2.xml.rels PK `\ppt/notesSlides/notesSlide2.xml 2PK `\xշ*ppt/notesSlides/_rels/notesSlide2.xml.rels PK `\]cOOppt/slides/slide3.xml Program OverviewA structured, full-time-equivalent path from fundamentals to a portfolio-ready capstone Duration45 Days Daily Class1 Hour 30 Minutes Total Duration67.5 Hours Delivery ModeOnline / Offline Teaching StyleIndustry-oriented, Hands-on, Interactive Target RolesAWS DevOps Engineer, Cloud Engineer, Cloud Support Engineer, Junior SREAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program3PK `\W/ ppt/slides/_rels/slide3.xml.rels PK `\K |Őppt/notesSlides/notesSlide3.xml 3PK `\9 Y*ppt/notesSlides/_rels/notesSlide3.xml.rels PK `\O;hDhDppt/slides/slide4.xml Who Should AttendDesigned for learners starting from basic computer knowledge upward 1Freshers entering the IT / Cloud job market 2Final-year engineering students (CSE, IT, ECE and allied branches) 3BCA / B.Sc / MCA graduates 4IT professionals switching into DevOps 5Anyone with basic computer knowledge and a will to build hands-on skillsAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program4PK `\` ppt/slides/_rels/slide4.xml.rels PK `\vsppt/notesSlides/notesSlide4.xml 4PK `\J *ppt/notesSlides/_rels/notesSlide4.xml.rels PK `\ L66ppt/slides/slide5.xml Where This Program Takes YouJob roles this curriculum prepares you for1AWS DevOps Engineer2Cloud Engineer3Cloud Support Engineer4Junior Site Reliability Engineer (SRE)AITrustED • AWS DevOps Engineer — 45-Day Job Ready Program5PK `\5 ppt/slides/_rels/slide5.xml.rels PK `\W8ppt/notesSlides/notesSlide5.xml 5PK `\Qe*ppt/notesSlides/_rels/notesSlide5.xml.rels PK `\omppt/slides/slide6.xml 45-Day Program RoadmapTen modules, each building directly on the last 1D1-2DevOps & AWS Intro▸ 2D3-7Linux Admin▸ 3D8-10Git & GitHub▸ 4D11-18AWS Core Services▸ 5D19-24Docker 6D25-30Jenkins CI/CD▸ 7D31-35Terraform▸ 8D36-41Kubernetes▸ 9D42-43Monitoring & DevSecOps▸ 10D44-45Capstone & Interview PrepAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program6PK `\ج+ ppt/slides/_rels/slide6.xml.rels PK `\zppt/notesSlides/notesSlide6.xml 6PK `\=|*ppt/notesSlides/_rels/notesSlide6.xml.rels PK `\` ,{m{mppt/slides/slide7.xml How Every Module Is StructuredThe same reliable rhythm, module after module1LearningObjectives2ConceptExplanation3Architecture /Workflow4Real IndustryExample5Hands-OnLab6BestPractices7InterviewQuestions8Summary& QuizEvery topic within a module also covers: definitions, why it's used, an industry use case, CLI commands, common mistakes, security considerations, and cost-optimization notes where relevant.AITrustED • AWS DevOps Engineer — 45-Day Job Ready Program7PK `\F ppt/slides/_rels/slide7.xml.rels PK `\)lppt/notesSlides/notesSlide7.xml 7PK `\|g*ppt/notesSlides/_rels/notesSlide7.xml.rels PK `\xi#i#ppt/slides/slide8.xml 1MODULE 1Days 1 - 2Introduction to DevOps & AWSWhat is DevOps, SDLC, Waterfall vs Agile, ScrumCI/CD and the DevOps lifecycleDevOps roles, responsibilities & the 2026 roadmapIntroduction to AWS, global infrastructure, shared responsibility modelAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program8PK `\6 ppt/slides/_rels/slide8.xml.rels PK `\iސppt/notesSlides/notesSlide8.xml 8PK `\pO*ppt/notesSlides/_rels/notesSlide8.xml.rels PK `\uY^6^6ppt/slides/slide9.xml MODULE 1Introduction to DevOps & AWS — Learning ObjectivesFoundational vocabulary and mindset every following module builds on By the end of this module you canExplain what DevOps is and why organizations adopt itCompare the SDLC, Waterfall, Agile and Scrum modelsDescribe the CI/CD pipeline and the full DevOps lifecycle...and apply it hands-on toList core DevOps Engineer responsibilities and 2026 role trendsExplain AWS global infrastructure and the Shared Responsibility ModelCreate an AWS Free Tier account and your first IAM userAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 19PK `\>$ ppt/slides/_rels/slide9.xml.rels PK `\qppt/notesSlides/notesSlide9.xml 9PK `\1*ppt/notesSlides/_rels/notesSlide9.xml.rels PK `\Ot‡77ppt/slides/slide10.xml MODULE 1What is DevOps? & the SDLCDevOps = Development + Operations, unified around fast, reliable delivery DevOps in one lineA culture and set of practices that unifies software development and IT operations to ship faster, with fewer failures.Why it's used: manual releases were slow and error-prone; DevOps automates build, test, and deployment.Industry example: e-commerce platforms deploy dozens of times a day using DevOps pipelines instead of a single risky monthly release.Software Development Life Cycle (SDLC)Requirements -> Design -> Development -> Testing -> Deployment -> MaintenanceDevOps compresses and automates the Testing -> Deployment -> Maintenance stages.Security consideration: 'Shift Left' means testing and security checks start early in the SDLC, not just before release.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 110PK `\Ѳ!ppt/slides/_rels/slide10.xml.rels PK `\O ppt/notesSlides/notesSlide10.xml 10PK `\T+ppt/notesSlides/_rels/notesSlide10.xml.rels PK `\0Y66ppt/slides/slide11.xml MODULE 1Waterfall vs Agile vs ScrumChoosing a delivery model shapes how DevOps practices are applied WaterfallSequential phases; each stage completes before the next begins.Best for fixed-scope, low-change projects (e.g. regulated hardware builds).Common mistake: applying Waterfall thinking to fast-moving cloud products causes slow releases.Agile & ScrumAgile: iterative delivery in small increments with continuous feedback.Scrum: a specific Agile framework - Sprints, Daily Stand-ups, Sprint Review, Retrospective.Industry example: most SaaS teams run 2-week Scrum sprints feeding a CI/CD pipeline.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 111PK `\;!ppt/slides/_rels/slide11.xml.rels PK `\s6ӑ ppt/notesSlides/notesSlide11.xml 11PK `\O+ppt/notesSlides/_rels/notesSlide11.xml.rels PK `\0JHыыppt/slides/slide12.xml MODULE 1CI/CD & the DevOps LifecycleContinuous Integration and Continuous Delivery/Deployment in practice 1Plan▸ 2Code▸ 3Build▸ 4Test▸ 5Release▸ 6Deploy▸ 7Operate▸ 8MonitorCI (Continuous Integration): every code commit is automatically built and tested.CD (Continuous Delivery/Deployment): tested builds are automatically released to staging or production.Industry example: a Jenkins pipeline triggers on every GitHub push, runs unit tests, then deploys to a staging environment automatically.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 112PK `\c!ppt/slides/_rels/slide12.xml.rels PK `\*)@ ppt/notesSlides/notesSlide12.xml 12PK `\Fb+ppt/notesSlides/_rels/notesSlide12.xml.rels PK `\!(J(Jppt/slides/slide13.xml MODULE 1DevOps Roles & the 2026 RoadmapWhere a DevOps Engineer sits, and how the role is evolving Core ResponsibilitiesCI/CD pipeline designInfra automation (IaC)Monitoring & alertingIncident response Common RolesDevOps EngineerSite Reliability EngineerCloud EngineerPlatform Engineer 2026 Roadmap TrendsPlatform EngineeringGitOps & policy-as-codeAI-assisted operationsFinOps / cost governanceAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 113PK `\x!ppt/slides/_rels/slide13.xml.rels PK `\Ї ppt/notesSlides/notesSlide13.xml 13PK `\yv+ppt/notesSlides/_rels/notesSlide13.xml.rels PK `\#2727ppt/slides/slide14.xml MODULE 1AWS Introduction & Global InfrastructureThe building blocks every later module depends on AWS at a glanceAWS: on-demand cloud computing platform - compute, storage, networking, databases, and 200+ services.Global Infrastructure: Regions (geographic areas) each with multiple Availability Zones (isolated data centers).Why it matters: deploying across Availability Zones gives high availability if one data center fails.Shared Responsibility ModelAWS secures 'the cloud' - hardware, network, facilities, virtualization layer.You secure 'in the cloud' - your data, IAM permissions, OS patching, application configuration.Common mistake: assuming AWS automatically secures your S3 buckets or IAM permissions - it does not.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 114PK `\O!ppt/slides/_rels/slide14.xml.rels PK `\0 ppt/notesSlides/notesSlide14.xml 14PK `\?ݤ+ppt/notesSlides/_rels/notesSlide14.xml.rels PK `\ (BBppt/slides/slide15.xml MODULE 1Hands-On Lab: AWS Account Setup & IAM UserGet a working, secured AWS login before touching any service 1Sign up for an AWS Free Tier account using a personal email and enable MFA on the root user. 2Open IAM and create a new administrative user - never use the root account for daily work. 3Attach the AdministratorAccess policy (for the lab environment) and generate console + CLI credentials. 4Install and configure the AWS CLI locally with `aws configure`, then verify with `aws sts get-caller-identity`.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 115PK `\*R!ppt/slides/_rels/slide15.xml.rels PK `\Qz ppt/notesSlides/notesSlide15.xml 15PK `\$Q+ppt/notesSlides/_rels/notesSlide15.xml.rels PK `\}`~M/M/ppt/slides/slide16.xml Introduction to DevOps & AWS — Best Practices & Pitfalls Best PracticesEnable MFA on the root account immediately after sign-upCreate individual IAM users - never share root credentialsAutomate repetitive release steps instead of manual runbooksTreat 'DevOps' as a culture shift, not just a toolchainCommon Mistakes to AvoidUsing the root account for everyday tasksSkipping budget alerts on a new Free Tier accountAssuming Agile automatically means 'no documentation'Confusing CI (integration) with CD (delivery/deployment)AITrustED • AWS DevOps Engineer — 45-Day Job Ready Program16PK `\ !ppt/slides/_rels/slide16.xml.rels PK `\  ppt/notesSlides/notesSlide16.xml 16PK `\ y+ppt/notesSlides/_rels/notesSlide16.xml.rels PK `\'SG==ppt/slides/slide17.xml MODULE 1Introduction to DevOps & AWS — Interview Questions Q1. What problem does DevOps actually solve?It removes the hand-off friction between Dev and Ops teams, replacing slow manual releases with automated, tested, repeatable pipelines. Q2. Difference between Continuous Delivery and Continuous Deployment?Delivery stops at a manual approval gate before production; Deployment pushes every passing build straight to production automatically. Q3. Explain the AWS Shared Responsibility Model in one sentence.AWS secures the underlying cloud infrastructure; the customer is responsible for securing their data, access, and configuration within it. Q4. Why use multiple Availability Zones?To survive the failure of a single data center by spreading redundant resources across physically isolated facilities in the same Region.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 117PK `\檋!ppt/slides/_rels/slide17.xml.rels PK `\r. ppt/notesSlides/notesSlide17.xml 17PK `\BI+ppt/notesSlides/_rels/notesSlide17.xml.rels PK `\G2tV::ppt/slides/slide18.xml MODULE 1Introduction to DevOps & AWS — Summary & Quiz Key TakeawaysDevOps unifies Dev and Ops around fast, automated, reliable delivery.Agile/Scrum provide the iterative cadence DevOps pipelines automate.CI/CD automates build, test, and release.AWS Regions and AZs are the foundation of highly available architecture.Security is a shared responsibility between AWS and you.Quick Quiz1. What does the 'CI' in CI/CD stand for, and what problem does it solve?2. Name the four Scrum ceremonies.3. What is an Availability Zone, and why do architectures use more than one?4. Under the Shared Responsibility Model, who patches your EC2 operating system?5. Why should you avoid using the AWS root account daily?AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 118PK `\Yh!ppt/slides/_rels/slide18.xml.rels PK `\ ppt/notesSlides/notesSlide18.xml 18PK `\N+ppt/notesSlides/_rels/notesSlide18.xml.rels PK `\N':#:#ppt/slides/slide19.xml 2MODULE 2Days 3 - 7Linux AdministrationLinux architecture, file system, essential commandsUsers, groups, permissions, processes & servicesSSH, SCP, cron jobs, package managementShell scripting basicsAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program19PK `\~!ppt/slides/_rels/slide19.xml.rels PK `\0[ ppt/notesSlides/notesSlide19.xml 19PK `\i+ppt/notesSlides/_rels/notesSlide19.xml.rels PK `\cc|a6a6ppt/slides/slide20.xml MODULE 2Linux Administration — Learning ObjectivesEvery AWS EC2 instance you touch runs on Linux - this is the daily-driver skillset By the end of this module you canNavigate the Linux file system and kernel/shell architecture confidentlyRun essential file, process, and network commands from the terminalManage users, groups, and file permissions securely...and apply it hands-on toControl services and schedule jobs with cronConnect to remote servers with SSH/SCP and manage packagesWrite a basic Bash script to automate a repeatable taskAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 220PK `\g_!ppt/slides/_rels/slide20.xml.rels PK `\7 ppt/notesSlides/notesSlide20.xml 20PK `\SB+ppt/notesSlides/_rels/notesSlide20.xml.rels PK `\+{66ppt/slides/slide21.xml MODULE 2Linux Architecture & File SystemUnderstanding what's under the hood before running commands blindly ArchitectureKernel: manages hardware, memory, and processes.Shell (Bash): the command interpreter between you and the kernel.Why it's used: nearly all cloud servers (including EC2) run Linux for its stability and open licensing.File System Hierarchy/ (root), /home, /etc (configs), /var (logs), /bin, /usr, /tmpEverything is a file - devices, sockets, and processes included.Industry example: application logs almost always live under /var/log for centralized monitoring tools to scrape.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 221PK `\z!ppt/slides/_rels/slide21.xml.rels PK `\89| ppt/notesSlides/notesSlide21.xml 21PK `\HΩ+ppt/notesSlides/_rels/notesSlide21.xml.rels PK `\xIIppt/slides/slide22.xml MODULE 2Essential Commands Cheat-SheetThe muscle-memory commands used every single day Navigation & Filesls, cd, pwdcp, mv, rmmkdir, touchcat, less, tail -f Search & Textgrep, findawk, sedwc, sort, uniqchmod, chown System & Networktop, ps, df -hfree -m, uptimecurl, wget, netstatsystemctl statusAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 222PK `\dV!ppt/slides/_rels/slide22.xml.rels PK `\cQc ppt/notesSlides/notesSlide22.xml 22PK `\aeZ+ppt/notesSlides/_rels/notesSlide22.xml.rels PK `\66ppt/slides/slide23.xml MODULE 2Users, Groups, Permissions & ProcessesAccess control and runtime visibility - core to securing any server Users, Groups & Permissionsuseradd, usermod, groupadd manage identities.rwx permissions for owner / group / others; chmod 750 restricts access tightly.Security consideration: never chmod 777 in production - it grants world write access.Processes & Servicesps aux / top show running processes and resource use.systemctl start|stop|enable manages background services (e.g. nginx, docker).Common mistake: killing a process with SIGKILL (-9) before trying a graceful SIGTERM.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 223PK `\A!ppt/slides/_rels/slide23.xml.rels PK `\] ppt/notesSlides/notesSlide23.xml 23PK `\ ~t+ppt/notesSlides/_rels/notesSlide23.xml.rels PK `\8$66ppt/slides/slide24.xml MODULE 2SSH, SCP, Cron & Package ManagementRemote access, scheduled automation, and installing software safely SSH, SCP & Packagesssh user@host for secure remote login using key-pairs (never passwords in production).scp file.txt user@host:/path copies files securely over SSH.apt/yum install manages packages; always apt update before installing.Cron Jobscrontab -e schedules recurring tasks, e.g. `0 2 * * * /scripts/backup.sh` runs nightly at 2 AM.Industry example: log rotation and database backup scripts are almost always cron-driven.Best practice: redirect cron output to a log file so failures are visible.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 224PK `\Y!ppt/slides/_rels/slide24.xml.rels PK `\`z ppt/notesSlides/notesSlide24.xml 24PK `\8+ppt/notesSlides/_rels/notesSlide24.xml.rels PK `\mmppt/slides/slide25.xml MODULE 2Shell Scripting BasicsTurning repetitive manual steps into a reusable script 1#!/bin/bash▸ 2Variables▸ 3Conditionals▸ 4Loops▸ 5Functions▸ 6Exit codesEvery script starts with a shebang (#!/bin/bash) telling the OS which interpreter to use.Industry example: a backup script checks disk space (conditional), loops through directories, and exits non-zero on failure so monitoring tools can alert on it.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 225PK `\̜|g!ppt/slides/_rels/slide25.xml.rels PK `\Y ppt/notesSlides/notesSlide25.xml 25PK `\#+ppt/notesSlides/_rels/notesSlide25.xml.rels PK `\wLLppt/slides/slide26.xml MODULE 2Hands-On Lab: Linux on AWS EC2Five hands-on labs building real server-admin muscle memory 1Launch an EC2 instance (Amazon Linux/Ubuntu) from the AWS Console with a key-pair. 2SSH into the instance from your local terminal using the downloaded .pem key. 3Install and start the Apache web server; confirm it's reachable over HTTP. 4Create two Linux users with restricted permissions and test access boundaries. 5Write and cron-schedule a Bash script that backs up a directory nightly.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 226PK `\5b?!ppt/slides/_rels/slide26.xml.rels PK `\Aʑ ppt/notesSlides/notesSlide26.xml 26PK `\${+ppt/notesSlides/_rels/notesSlide26.xml.rels PK `\| / /ppt/slides/slide27.xml Linux Administration — Best Practices & Pitfalls Best PracticesUse SSH key-pairs, disable password authenticationApply the principle of least privilege on file permissionsAutomate routine maintenance with cron + scriptsKeep packages patched with regular apt/yum updatesCommon Mistakes to AvoidRunning production services as the root userchmod 777 as a quick 'fix' for permission errorsIgnoring cron job failures because output isn't loggedEditing production configs without a backup copyAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program27PK `\PG!ppt/slides/_rels/slide27.xml.rels PK `\W  ppt/notesSlides/notesSlide27.xml 27PK `\e+ppt/notesSlides/_rels/notesSlide27.xml.rels PK `\O|'J=J=ppt/slides/slide28.xml MODULE 2Linux Administration — Interview Questions Q1. How do you check disk space and memory usage on Linux?df -h shows disk space per filesystem; free -m shows memory usage in megabytes. Q2. What's the difference between a hard link and a soft (symbolic) link?A hard link points directly to the same inode as the original file; a symlink is a separate file that references the original's path. Q3. How would you find all files modified in the last 24 hours?find / -mtime -1 searches the filesystem for files modified within the last day. Q4. Why prefer SSH keys over password authentication?Keys are far harder to brute-force, can't be reused across accidental leaks the same way passwords are, and support automation without storing secrets in scripts.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 228PK `\ [R]!ppt/slides/_rels/slide28.xml.rels PK `\\ ppt/notesSlides/notesSlide28.xml 28PK `\i+ppt/notesSlides/_rels/notesSlide28.xml.rels PK `\?CzR:R:ppt/slides/slide29.xml MODULE 2Linux Administration — Summary & Quiz Key TakeawaysLinux is the OS foundation for almost every cloud server.Permissions and user/group management enforce least privilege.SSH/SCP enable secure remote access and file transfer.Cron automates recurring operational tasks.Shell scripts turn manual runbooks into repeatable automation.Quick Quiz1. What command shows real-time process and CPU usage?2. How do you grant execute permission to a script's owner only?3. What's the cron syntax for 'every day at 2 AM'?4. Which command copies a file to a remote server over SSH?5. Why should cron script output be redirected to a log file?AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 229PK `\->w!ppt/slides/_rels/slide29.xml.rels PK `\zx ppt/notesSlides/notesSlide29.xml 29PK `\(Lk+ppt/notesSlides/_rels/notesSlide29.xml.rels PK `\0;#;#ppt/slides/slide30.xml 3MODULE 3Days 8 - 10Git & GitHubVersion control fundamentals & the Git workflowClone, commit, push, pull, branch, merge, rebaseConflict resolution & Pull RequestsGitHub collaboration for teamsAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program30PK `\*!ppt/slides/_rels/slide30.xml.rels PK `\ q) ppt/notesSlides/notesSlide30.xml 30PK `\+ppt/notesSlides/_rels/notesSlide30.xml.rels PK `\,p`W6W6ppt/slides/slide31.xml MODULE 3Git & GitHub — Learning ObjectivesGit is the substrate every CI/CD pipeline in this course triggers from By the end of this module you canExplain why version control is non-negotiable in modern engineeringPerform the full local Git workflow: clone, commit, push, pullCreate branches and merge or rebase them safely...and apply it hands-on toResolve merge conflicts confidently instead of fearing themOpen, review, and merge Pull Requests on GitHubBuild a GitHub profile that doubles as a portfolio for job applicationsAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 331PK `\!ppt/slides/_rels/slide31.xml.rels PK `\ ppt/notesSlides/notesSlide31.xml 31PK `\{+ppt/notesSlides/_rels/notesSlide31.xml.rels PK `\v\y6y6ppt/slides/slide32.xml MODULE 3Version Control & the Git WorkflowWhy every team - and every pipeline - starts here Why Version ControlTracks every change to code with full history and attribution.Why it's used: enables safe collaboration, rollback, and audit trails.Industry example: a bad deploy is rolled back in seconds via `git revert`, not hours of manual fixes.Core Workflowgit init/clone -> git add -> git commit -> git pushgit pull fetches and merges remote changes into your local branch.Common mistake: committing directly to `main` instead of a feature branch.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 332PK `\;!ppt/slides/_rels/slide32.xml.rels PK `\lZ} ppt/notesSlides/notesSlide32.xml 32PK `\|+ppt/notesSlides/_rels/notesSlide32.xml.rels PK `\ߏ!D!Dppt/slides/slide33.xml MODULE 3Branching, Merging & RebasingThe three operations every Git workflow revolves around Branchgit branch feature-xgit checkout -b feature-xIsolates in-progress work Mergegit merge feature-xCombines histories, keeps all commitsSafe for shared branches Rebasegit rebase mainReplays commits for a linear historyAvoid rebasing shared branchesAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 333PK `\^r!ppt/slides/_rels/slide33.xml.rels PK `\\ ppt/notesSlides/notesSlide33.xml 33PK `\=cu+ppt/notesSlides/_rels/notesSlide33.xml.rels PK `\ 2o66ppt/slides/slide34.xml MODULE 3Conflict Resolution & Pull RequestsWhere most beginners lose confidence - and how to gain it back Resolving ConflictsConflicts appear as <<<<<<< / ======= / >>>>>>> markers in the file.Manually choose the correct code, remove markers, then `git add` and commit.Best practice: pull frequently and keep branches short-lived to minimize conflicts.Pull Requests (PRs)A PR proposes merging a feature branch into main, with review and CI checks attached.Industry example: PRs typically require at least one approval and a passing pipeline before merge.GitHub Collaboration: Issues, PR templates, and code owners keep teams aligned.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 334PK `\iC!ppt/slides/_rels/slide34.xml.rels PK `\鼀 ppt/notesSlides/notesSlide34.xml 34PK `\Ŷ+ppt/notesSlides/_rels/notesSlide34.xml.rels PK `\vAAppt/slides/slide35.xml MODULE 3Hands-On Lab: Team Git CollaborationPracticing the exact workflow used on a real engineering team 1Fork a shared repository and clone it locally. 2Create a feature branch, make changes, and open a Pull Request. 3Deliberately create and then resolve a merge conflict with a teammate's branch. 4Publish a polished GitHub profile README as your portfolio.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 335PK `\ !ppt/slides/_rels/slide35.xml.rels PK `\Q"wG ppt/notesSlides/notesSlide35.xml 35PK `\:+ppt/notesSlides/_rels/notesSlide35.xml.rels PK `\ؒT//ppt/slides/slide36.xml Git & GitHub — Best Practices & Pitfalls Best PracticesCommit small, focused changes with clear messagesAlways work in feature branches, never on main directlyPull before you push to reduce conflictsUse Pull Requests for review, even solo projectsCommon Mistakes to AvoidForce-pushing to a shared branch without warning teammatesCommitting secrets or .env files into the repoRebasing a branch other people are actively usingWriting vague commit messages like 'fix stuff'AITrustED • AWS DevOps Engineer — 45-Day Job Ready Program36PK `\!ppt/slides/_rels/slide36.xml.rels PK `\xZԑ ppt/notesSlides/notesSlide36.xml 36PK `\9z+ppt/notesSlides/_rels/notesSlide36.xml.rels PK `\#&i=i=ppt/slides/slide37.xml MODULE 3Git & GitHub — Interview Questions Q1. What's the difference between git merge and git rebase?Merge preserves both histories and adds a merge commit; rebase replays your commits on top of the target branch for a linear, cleaner history. Q2. How do you undo a commit that's already been pushed?git revert creates a new commit undoing the changes safely; resetting and force-pushing rewrites history and is riskier on shared branches. Q3. What causes a merge conflict?Git can't automatically reconcile two branches because the same lines were changed differently in each - manual resolution is required. Q4. What's the purpose of a Pull Request?It's a review gate: teammates and automated CI checks validate the change before it's merged into the shared branch.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 337PK `\!ppt/slides/_rels/slide37.xml.rels PK `\4 ppt/notesSlides/notesSlide37.xml 37PK `\x"+ppt/notesSlides/_rels/notesSlide37.xml.rels PK `\M^F:F:ppt/slides/slide38.xml MODULE 3Git & GitHub — Summary & Quiz Key TakeawaysGit tracks every change with full, auditable history.Feature branches isolate work until it's ready to merge.Merge conflicts are normal and resolvable, not something to fear.Pull Requests add review and CI gates before code reaches main.A strong GitHub profile is itself a hiring asset.Quick Quiz1. What command creates and switches to a new branch in one step?2. What do the <<<<<<< markers in a file indicate?3. Why is rebasing a shared branch risky?4. What typically must pass before a PR can be merged?5. Name one reason to avoid committing directly to main.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 338PK `\!ppt/slides/_rels/slide38.xml.rels PK `\܈ ppt/notesSlides/notesSlide38.xml 38PK `\txu+ppt/notesSlides/_rels/notesSlide38.xml.rels PK `\vS#S#ppt/slides/slide39.xml 4MODULE 4Days 11 - 18AWS Core ServicesIAM, EC2, EBS & Security GroupsVPC, Subnets, Route Tables, IGW, NAT, Elastic IPApplication Load Balancer & Auto ScalingS3, RDS, CloudWatch, SNS, SQS, Parameter Store, Secrets ManagerAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program39PK `\#y!ppt/slides/_rels/slide39.xml.rels PK `\NCQf ppt/notesSlides/notesSlide39.xml 39PK `\5cj+ppt/notesSlides/_rels/notesSlide39.xml.rels PK `\n}a6a6ppt/slides/slide40.xml MODULE 4AWS Core Services — Learning ObjectivesThe single biggest module - the AWS services that make up 80% of real DevOps day-to-day work By the end of this module you canSecure accounts and resources correctly with IAMLaunch, size, and attach storage to EC2 instancesDesign a custom VPC with public and private subnets...and apply it hands-on toRoute traffic safely with Security Groups, IGW, and NAT GatewayDistribute load and auto-scale a web tier with ALB + Auto ScalingUse S3, RDS, CloudWatch, SNS/SQS, and secrets services correctlyAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 440PK `\ !ppt/slides/_rels/slide40.xml.rels PK `\`g#q ppt/notesSlides/notesSlide40.xml 40PK `\]+ppt/notesSlides/_rels/notesSlide40.xml.rels PK `\)lǏ66ppt/slides/slide41.xml MODULE 4IAM & EC2Identity, access control, and your first compute resource IAM (Identity & Access Management)Users, Groups, Roles, and Policies (JSON documents defining allow/deny actions).Why it's used: enforces least-privilege access to every AWS resource.Best practice: attach policies to Roles/Groups, not individual users directly.EC2 & EBSEC2: resizable virtual servers billed by instance type and hour/second.EBS: persistent block storage volumes attached to an EC2 instance.Cost tip: stop (don't just leave running) idle EC2 instances outside business hours.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 441PK `\5ne!ppt/slides/_rels/slide41.xml.rels PK `\趑 ppt/notesSlides/notesSlide41.xml 41PK `\Fr+ppt/notesSlides/_rels/notesSlide41.xml.rels PK `\U(I66ppt/slides/slide42.xml MODULE 4Security Groups & VPC NetworkingThe firewall rules and network fabric everything else sits inside Security GroupsStateful, instance-level virtual firewalls - allow rules only, no explicit deny.Industry example: a web server SG allows inbound 443 from anywhere but SSH (22) only from a bastion host IP.Common mistake: opening port 22 or 3389 to 0.0.0.0/0 in production.VPC, Subnets & Route TablesVPC: your own isolated virtual network within an AWS Region.Public subnet routes to an Internet Gateway; private subnet does not.Route tables decide where each subnet's traffic goes next.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 442PK `\ǿ=!ppt/slides/_rels/slide42.xml.rels PK `\% ppt/notesSlides/notesSlide42.xml 42PK `\/k+ppt/notesSlides/_rels/notesSlide42.xml.rels PK `\$p4p4ppt/slides/slide43.xml MODULE 4Internet Gateway, NAT Gateway & Elastic IPGetting traffic in and out safely Internet Gateway (IGW)Attached to the VPC; allows public subnet resources direct internet access.Required for any resource that needs a public IP to be reachable.NAT Gateway & Elastic IPNAT Gateway: lets private-subnet instances reach the internet (e.g. for updates) without being reachable from it.Elastic IP: a static public IP you can remap between instances.Cost consideration: NAT Gateways bill hourly plus per-GB - a common surprise line item.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 443PK `\:!ppt/slides/_rels/slide43.xml.rels PK `\= ppt/notesSlides/notesSlide43.xml 43PK `\npjq+ppt/notesSlides/_rels/notesSlide43.xml.rels PK `\V6eeppt/slides/slide44.xml MODULE 4Architecture: Highly Available Web ApplicationThe reference architecture this module builds toward 1Route 53▸ 2ALB▸ 3Auto ScalingGroup (EC2)▸ 4RDS(Multi-AZ)▸ 5CloudWatchApplication Load Balancer distributes traffic across EC2 instances in multiple Availability Zones.Auto Scaling Group adds/removes instances automatically based on load, keeping cost and performance balanced.Industry example: this is the standard pattern behind most production web tiers on AWS, from startups to enterprises.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 444PK `\M!ppt/slides/_rels/slide44.xml.rels PK `\Eؑ ppt/notesSlides/notesSlide44.xml 44PK `\6+ppt/notesSlides/_rels/notesSlide44.xml.rels PK `\SψtzDzDppt/slides/slide45.xml MODULE 4Storage, Database & Messaging ServicesThe services that hold and move your application's data S3 (Storage)Object storage, 11 9's durabilityStatic website hostingLifecycle rules for cost control RDS (Database)Managed MySQL/Postgres/etc.Multi-AZ for automatic failoverAutomated backups & patching CloudWatch / SNS / SQSCloudWatch: metrics, logs, alarmsSNS: pub/sub notificationsSQS: decoupling via message queuesAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 445PK `\j !ppt/slides/_rels/slide45.xml.rels PK `\8% ppt/notesSlides/notesSlide45.xml 45PK `\-3+ppt/notesSlides/_rels/notesSlide45.xml.rels PK `\nm44ppt/slides/slide46.xml MODULE 4Parameter Store & Secrets ManagerNever hard-code a credential into your code or pipeline again Systems Manager Parameter StoreStores configuration values and (optionally encrypted) secrets as key-value pairs.Free tier available; ideal for non-rotating configuration values.Secrets ManagerPurpose-built for credentials - supports automatic rotation.Security consideration: reference secrets by ARN in code/pipelines, never paste plaintext values into a repo.Industry example: an RDS password is stored in Secrets Manager and rotated every 30 days automatically.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 446PK `\BYT!ppt/slides/_rels/slide46.xml.rels PK `\ ppt/notesSlides/notesSlide46.xml 46PK `\j~+ppt/notesSlides/_rels/notesSlide46.xml.rels PK `\ţ(B(Bppt/slides/slide47.xml MODULE 4Hands-On Lab: Build a Highly Available Web AppThe flagship lab of the entire AWS Core Services module 1Design and build a custom VPC with public and private subnets across two AZs. 2Launch EC2 instances in an Auto Scaling Group behind an Application Load Balancer. 3Host a static site on S3 and connect it to the same architecture. 4Configure CloudWatch alarms to monitor CPU and trigger scaling policies.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 447PK `\e<!ppt/slides/_rels/slide47.xml.rels PK `\]K ppt/notesSlides/notesSlide47.xml 47PK `\+++ppt/notesSlides/_rels/notesSlide47.xml.rels PK `\U5/5/ppt/slides/slide48.xml AWS Core Services — Best Practices & Pitfalls Best PracticesUse least-privilege IAM policies scoped to specific resourcesPlace databases in private subnets, never publicly exposedEnable Multi-AZ for production RDS instancesStore all secrets in Secrets Manager, not environment filesCommon Mistakes to AvoidOpening Security Groups to 0.0.0.0/0 for convenienceLeaving unattached EBS volumes and Elastic IPs running (billed)Skipping CloudWatch alarms until after an incidentHard-coding access keys directly in application codeAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program48PK `\76!ppt/slides/_rels/slide48.xml.rels PK `\$ ppt/notesSlides/notesSlide48.xml 48PK `\'|+ppt/notesSlides/_rels/notesSlide48.xml.rels PK `\Tv=v=ppt/slides/slide49.xml MODULE 4AWS Core Services — Interview Questions Q1. What's the difference between a Security Group and a Network ACL?Security Groups are stateful and operate at the instance level (allow rules only); NACLs are stateless and operate at the subnet level (allow and deny rules). Q2. Why does a private subnet need a NAT Gateway?So instances without public IPs can reach the internet for updates while remaining unreachable from inbound internet traffic. Q3. How does an Auto Scaling Group decide to add instances?It evaluates a scaling policy, typically tied to a CloudWatch alarm such as average CPU utilization crossing a threshold. Q4. Where should application secrets be stored on AWS?In AWS Secrets Manager or Parameter Store (SecureString), referenced by ARN at runtime - never committed to source control.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 449PK `\R!ppt/slides/_rels/slide49.xml.rels PK `\'> ppt/notesSlides/notesSlide49.xml 49PK `\fn+ppt/notesSlides/_rels/notesSlide49.xml.rels PK `\@w:w:ppt/slides/slide50.xml MODULE 4AWS Core Services — Summary & Quiz Key TakeawaysIAM enforces least-privilege access across every AWS resource.VPCs, subnets, and route tables form the network foundation.ALB + Auto Scaling gives a web tier elasticity and resilience.S3, RDS, and CloudWatch cover storage, database, and observability.Secrets Manager and Parameter Store remove hard-coded credentials.Quick Quiz1. What's the purpose of an Internet Gateway versus a NAT Gateway?2. Which AWS service provides automatic database failover across AZs?3. What triggers an Auto Scaling Group to launch a new instance?4. Name one cost-optimization tip for idle EC2 instances.5. Why is it risky to open port 22 to 0.0.0.0/0?AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 450PK `\A!ppt/slides/_rels/slide50.xml.rels PK `\^o ppt/notesSlides/notesSlide50.xml 50PK `\K+ppt/notesSlides/_rels/notesSlide50.xml.rels PK `\x##ppt/slides/slide51.xml 5MODULE 5Days 19 - 24DockerContainers vs Virtual MachinesDocker architecture, images & DockerfileDocker Compose, networking & volumesMulti-stage builds & Docker HubAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program51PK `\;*!ppt/slides/_rels/slide51.xml.rels PK `\Q. ppt/notesSlides/notesSlide51.xml 51PK `\ǭ+ppt/notesSlides/_rels/notesSlide51.xml.rels PK `\<7@6@6ppt/slides/slide52.xml MODULE 5Docker — Learning ObjectivesThe packaging format every downstream pipeline - Jenkins, Kubernetes - assumes you already know By the end of this module you canExplain why containers replaced VMs for most application packagingWrite a Dockerfile that builds a lean, production-ready imageRun multi-container applications with Docker Compose...and apply it hands-on toConfigure container networking and persistent volumesOptimize image size using multi-stage buildsPush and pull images through Docker HubAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 552PK `\W4!ppt/slides/_rels/slide52.xml.rels PK `\; ppt/notesSlides/notesSlide52.xml 52PK `\2S+ppt/notesSlides/_rels/notesSlide52.xml.rels PK `\WB44ppt/slides/slide53.xml MODULE 5Containers vs Virtual MachinesWhy the industry shifted from VMs to containers Virtual MachinesEach VM includes a full guest OS - heavier, slower to boot.Strong isolation, useful when running fully different OS kernels.ContainersShare the host OS kernel; package only the app + its dependencies.Boot in seconds, far lighter than VMs - ideal for microservices.Industry example: a team runs 50 containers on hardware that would host only 5-6 VMs.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 553PK `\42!ppt/slides/_rels/slide53.xml.rels PK `\4 ppt/notesSlides/notesSlide53.xml 53PK `\sp+ppt/notesSlides/_rels/notesSlide53.xml.rels PK `\%66ppt/slides/slide54.xml MODULE 5Docker Architecture, Images & DockerfileHow Docker builds and runs a container Architecture & ImagesDocker Engine (daemon) builds, runs, and manages containers from images.An image is a read-only, layered template; a container is a running instance of it.docker build, docker run, docker ps are the core daily commands.DockerfileA text file of instructions: FROM, COPY, RUN, EXPOSE, CMD.Best practice: order instructions so rarely-changing layers (like dependency installs) come before frequently-changing code.Common mistake: using a bloated base image (e.g. full Ubuntu) instead of a slim/alpine variant.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 554PK `\C (!ppt/slides/_rels/slide54.xml.rels PK `\ |(Ƒ ppt/notesSlides/notesSlide54.xml 54PK `\ +ppt/notesSlides/_rels/notesSlide54.xml.rels PK `\ X4X4ppt/slides/slide55.xml MODULE 5Docker Compose, Networking & VolumesRunning realistic, multi-service applications locally Docker ComposeA single docker-compose.yml defines and links multiple services (e.g. app + database).docker-compose up starts the entire stack with one command.Networking & VolumesBridge networks let containers discover each other by service name.Volumes persist data outside the container's writable layer - critical for databases.Security consideration: never store secrets directly inside an image layer.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 555PK `\d`,!ppt/slides/_rels/slide55.xml.rels PK `\ ppt/notesSlides/notesSlide55.xml 55PK `\І+ppt/notesSlides/_rels/notesSlide55.xml.rels PK `\JhJhppt/slides/slide56.xml MODULE 5Multi-Stage Builds & Docker HubProducing a small, secure final image and distributing it 1Buildstage▸ 2Compile /install deps▸ 3Copy onlyartifacts▸ 4Final slimimage▸ 5Push toDocker HubMulti-stage builds keep build tools out of the final image, shrinking size and attack surface.Industry example: a Node.js app built with dev dependencies in stage one ships only the compiled output and runtime in the final image.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 556PK `\L2!ppt/slides/_rels/slide56.xml.rels PK `\lΒ ppt/notesSlides/notesSlide56.xml 56PK `\w+ppt/notesSlides/_rels/notesSlide56.xml.rels PK `\yAAppt/slides/slide57.xml MODULE 5Hands-On Lab: Containerize a Python AppFrom source code to a published image on Docker Hub 1Write a Dockerfile for a simple Python (Flask) application. 2Build the image locally and run it, verifying the app responds on the exposed port. 3Add a second service (e.g. Redis) via Docker Compose and connect the two. 4Tag and push the final image to Docker Hub.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 557PK `\kp!ppt/slides/_rels/slide57.xml.rels PK `\&U ppt/notesSlides/notesSlide57.xml 57PK `\6+ppt/notesSlides/_rels/notesSlide57.xml.rels PK `\ײn)/)/ppt/slides/slide58.xml Docker — Best Practices & Pitfalls Best PracticesUse slim/alpine base images to reduce size and attack surfaceLeverage multi-stage builds to exclude build-time toolsPin explicit image versions instead of `latest`Store secrets via environment injection, never in the imageCommon Mistakes to AvoidRunning containers as the root user by defaultBaking API keys or passwords into a Dockerfile layerIgnoring the .dockerignore file, bloating build contextUsing one giant container instead of composing focused servicesAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program58PK `\!ppt/slides/_rels/slide58.xml.rels PK `\ ppt/notesSlides/notesSlide58.xml 58PK `\:v+ppt/notesSlides/_rels/notesSlide58.xml.rels PK `\!.==ppt/slides/slide59.xml MODULE 5Docker — Interview Questions Q1. What's the difference between a Docker image and a container?An image is an immutable, layered template; a container is a running (or stopped) instance created from that image. Q2. Why use multi-stage Docker builds?To keep build-time dependencies out of the final image, producing a smaller, more secure runtime artifact. Q3. How do containers on the same Docker network communicate?They resolve each other by service/container name over Docker's internal DNS on a shared bridge network. Q4. Why avoid tagging images as `latest` in production?It's ambiguous and mutable - deployments should reference an explicit, immutable version tag for reproducibility.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 559PK `\'!ppt/slides/_rels/slide59.xml.rels PK `\  ppt/notesSlides/notesSlide59.xml 59PK `\{mEo+ppt/notesSlides/_rels/notesSlide59.xml.rels PK `\vAQ:Q:ppt/slides/slide60.xml MODULE 5Docker — Summary & Quiz Key TakeawaysContainers share the host kernel, making them far lighter than VMs.A Dockerfile defines exactly how an image is built, layer by layer.Docker Compose orchestrates multi-container applications locally.Volumes persist data beyond a container's lifecycle.Multi-stage builds produce smaller, more secure final images.Quick Quiz1. What Dockerfile instruction defines the base image?2. What command starts every service in a docker-compose.yml?3. Why do databases inside containers need volumes?4. What's the security risk of running a container as root?5. Name one benefit of pushing images to Docker Hub.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 560PK `\O-t!ppt/slides/_rels/slide60.xml.rels PK `\&L ppt/notesSlides/notesSlide60.xml 60PK `\+ppt/notesSlides/_rels/notesSlide60.xml.rels PK `\!ir##ppt/slides/slide61.xml 6MODULE 6Days 25 - 30Jenkins CI/CDJenkins installation & architectureFreestyle jobs vs Declarative PipelinesWebhooks, credentials & pluginsEnd-to-end CI/CD pipelineAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program61PK `\hH!ppt/slides/_rels/slide61.xml.rels PK `\d ppt/notesSlides/notesSlide61.xml 61PK `\ּ+ppt/notesSlides/_rels/notesSlide61.xml.rels PK `\'2626ppt/slides/slide62.xml MODULE 6Jenkins CI/CD — Learning ObjectivesThe automation engine that turns every earlier module into one continuous flow By the end of this module you canInstall and configure a Jenkins controllerUnderstand Jenkins' master/agent architectureWrite a Declarative Pipeline (Jenkinsfile) from scratch...and apply it hands-on toTrigger builds automatically via GitHub webhooksManage credentials and extend Jenkins with pluginsAssemble a complete GitHub -> Jenkins -> Docker Hub pipelineAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 662PK `\@٭!ppt/slides/_rels/slide62.xml.rels PK `\CI ppt/notesSlides/notesSlide62.xml 62PK `\+ppt/notesSlides/_rels/notesSlide62.xml.rels PK `\r2@66ppt/slides/slide63.xml MODULE 6Jenkins Installation & ArchitectureUnderstanding the automation server before scripting pipelines ArchitectureController (master): schedules jobs, serves the UI, stores configuration.Agents (nodes): execute the actual build/test/deploy steps, often in parallel.Why it's used: decouples orchestration from execution, scaling builds across many agents.InstallationTypically installed on an EC2 instance or as a Docker container.Runs on port 8080 by default; unlocked via an initial admin password.Best practice: run Jenkins behind HTTPS with role-based access control enabled.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 663PK `\g,!ppt/slides/_rels/slide63.xml.rels PK `\Nߑ ppt/notesSlides/notesSlide63.xml 63PK `\Tr+ppt/notesSlides/_rels/notesSlide63.xml.rels PK `\Q1%T4T4ppt/slides/slide64.xml MODULE 6Freestyle Jobs vs Declarative PipelinesTwo ways to define a Jenkins job - only one scales well Freestyle JobsConfigured through the UI - quick to set up, hard to version or review.Common mistake: relying on Freestyle jobs for complex, multi-stage pipelines.Declarative PipelinesDefined as code in a Jenkinsfile, checked into the same repo as the app.Structured with stages: Checkout, Build, Test, Push, Deploy.Industry example: teams review Jenkinsfile changes in Pull Requests just like application code.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 664PK `\!ppt/slides/_rels/slide64.xml.rels PK `\6b ppt/notesSlides/notesSlide64.xml 64PK `\Ԡ+ppt/notesSlides/_rels/notesSlide64.xml.rels PK `\ϥGqDqDppt/slides/slide65.xml MODULE 6Webhooks, Credentials & PluginsThe wiring that connects Jenkins to the rest of your toolchain WebhooksGitHub push -> webhook -> JenkinsRemoves need for manual pollingNear-instant build triggers CredentialsStores tokens, SSH keys, secretsInjected into pipeline steps securelyNever hard-coded in Jenkinsfile PluginsDocker, Git, Slack notificationsExtend Jenkins to any toolSecurity: only install trusted pluginsAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 665PK `\7!ppt/slides/_rels/slide65.xml.rels PK `\~" ppt/notesSlides/notesSlide65.xml 65PK `\X+ppt/notesSlides/_rels/notesSlide65.xml.rels PK `\yȩ_t_tppt/slides/slide66.xml MODULE 6End-to-End CI/CD FlowThe exact pipeline this module's lab implements 1GitHubPush▸ 2JenkinsTrigger▸ 3Build▸ 4Test▸ 5DockerBuild▸ 6Push toDocker HubEach stage runs as a discrete step in the Jenkinsfile, with the pipeline failing fast if any stage errors out.Industry example: a failed test stage blocks the Docker build entirely, preventing a broken image from ever reaching the registry.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 666PK `\!ppt/slides/_rels/slide66.xml.rels PK `\ ppt/notesSlides/notesSlide66.xml 66PK `\P}+ppt/notesSlides/_rels/notesSlide66.xml.rels PK `\3-B-Bppt/slides/slide67.xml MODULE 6Hands-On Lab: Complete CI/CD PipelineWiring GitHub, Jenkins, and Docker Hub into one automated flow 1Install Jenkins on an EC2 instance and install the Docker + Git plugins. 2Connect a GitHub repository and configure a webhook to trigger builds on push. 3Write a Jenkinsfile with Checkout, Build, Test, Docker Build, and Push stages. 4Trigger a real push and verify the image lands in Docker Hub automatically.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 667PK `\8E!ppt/slides/_rels/slide67.xml.rels PK `\lOv ppt/notesSlides/notesSlide67.xml 67PK `\@+ppt/notesSlides/_rels/notesSlide67.xml.rels PK `\C?/?/ppt/slides/slide68.xml Jenkins CI/CD — Best Practices & Pitfalls Best PracticesDefine pipelines as code (Jenkinsfile) in the same repoStore all secrets in Jenkins Credentials, injected at runtimeFail the pipeline fast on the first failing stageKeep agents disposable and rebuild them from a known imageCommon Mistakes to AvoidHard-coding tokens or passwords inside the JenkinsfileRelying only on UI-configured Freestyle jobs for critical pipelinesLetting Jenkins plugins go unpatched for monthsSkipping the test stage 'to save time' before deployAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program68PK `\!ppt/slides/_rels/slide68.xml.rels PK `\WDđ ppt/notesSlides/notesSlide68.xml 68PK `\q+ppt/notesSlides/_rels/notesSlide68.xml.rels PK `\t=t=ppt/slides/slide69.xml MODULE 6Jenkins CI/CD — Interview Questions Q1. What's the benefit of a Declarative Pipeline over a Freestyle job?It's version-controlled as code alongside the application, reviewable in Pull Requests, and far easier to reproduce or roll back. Q2. How does a GitHub webhook trigger a Jenkins build?GitHub sends an HTTP POST to Jenkins on a configured event (like a push), and Jenkins' GitHub plugin starts the matching job immediately. Q3. Where should pipeline secrets be stored?In Jenkins' built-in Credentials store, referenced by ID in the Jenkinsfile - never hard-coded as plaintext. Q4. What happens if the Test stage fails in a well-designed pipeline?The pipeline stops immediately, and later stages like Docker Build and Push never execute, preventing a broken artifact from shipping.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 669PK `\t'!ppt/slides/_rels/slide69.xml.rels PK `\a ppt/notesSlides/notesSlide69.xml 69PK `\\jm+ppt/notesSlides/_rels/notesSlide69.xml.rels PK `\dYH:H:ppt/slides/slide70.xml MODULE 6Jenkins CI/CD — Summary & Quiz Key TakeawaysJenkins' controller/agent architecture scales builds across nodes.Declarative Pipelines define CI/CD as reviewable code.Webhooks trigger builds instantly on a GitHub push.Credentials keep secrets out of pipeline source code.A well-designed pipeline fails fast before a bad build ships.Quick Quiz1. What file defines a Declarative Pipeline?2. What triggers a Jenkins build automatically after a git push?3. Where should an API token used in a pipeline be stored?4. Name the five stages in the GitHub-to-Docker-Hub pipeline.5. Why avoid relying only on Freestyle jobs for complex pipelines?AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 670PK `\Ai!ppt/slides/_rels/slide70.xml.rels PK `\-iR ppt/notesSlides/notesSlide70.xml 70PK `\Z +ppt/notesSlides/_rels/notesSlide70.xml.rels PK `\LY##ppt/slides/slide71.xml 7MODULE 7Days 31 - 35TerraformInfrastructure as Code fundamentalsProviders, variables & outputsModules, state files & remote backendProvisioning real AWS infrastructureAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program71PK `\fLP!ppt/slides/_rels/slide71.xml.rels PK `\梕 ppt/notesSlides/notesSlide71.xml 71PK `\A+ppt/notesSlides/_rels/notesSlide71.xml.rels PK `\9t6t6ppt/slides/slide72.xml MODULE 7Terraform — Learning ObjectivesThe same architecture built manually in Module 4, now defined, versioned, and repeatable as code By the end of this module you canExplain what Infrastructure as Code (IaC) solves versus manual console clicksWrite Terraform configuration using providers, variables, and outputsOrganize reusable infrastructure with modules...and apply it hands-on toUnderstand state files and configure a remote backend safelyProvision an EC2 instance and a VPC entirely from codeDeploy a small multi-resource stack with `terraform apply`AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 772PK `\NqR!ppt/slides/_rels/slide72.xml.rels PK `\༏ ppt/notesSlides/notesSlide72.xml 72PK `\l8+ppt/notesSlides/_rels/notesSlide72.xml.rels PK `\.[66ppt/slides/slide73.xml MODULE 7Infrastructure as CodeWhy teams stopped clicking through the AWS Console for production infra What is IaCInfrastructure defined in code (HCL) instead of manual console configuration.Why it's used: repeatable, versioned, reviewable infrastructure changes - just like application code.Industry example: an entire environment can be recreated identically in minutes after a disaster.Terraform Workflowterraform init -> plan -> apply -> destroy`plan` shows exactly what will change before anything is touched.Best practice: always review `terraform plan` output before `apply` in production.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 773PK `\iw!ppt/slides/_rels/slide73.xml.rels PK `\rwD ppt/notesSlides/notesSlide73.xml 73PK `\Iws+ppt/notesSlides/_rels/notesSlide73.xml.rels PK `\\2b4b4ppt/slides/slide74.xml MODULE 7Providers, Variables & OutputsThe building blocks of every Terraform configuration file Providers & ResourcesThe `aws` provider lets Terraform talk to AWS APIs.`resource` blocks declare exactly what should exist (e.g. aws_instance, aws_vpc).Variables & OutputsVariables parameterize configs (e.g. instance_type, region) for reuse across environments.Outputs expose values (like a public IP) after apply completes.Common mistake: hard-coding values instead of variables, breaking reuse across dev/stage/prod.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 774PK `\#o!ppt/slides/_rels/slide74.xml.rels PK `\O ppt/notesSlides/notesSlide74.xml 74PK `\1a+ppt/notesSlides/_rels/notesSlide74.xml.rels PK `\k$44ppt/slides/slide75.xml MODULE 7Modules, State Files & Remote BackendScaling Terraform from a single file to a team-managed platform ModulesReusable, self-contained bundles of resources (e.g. a 'vpc' module used across projects).Industry example: a company-wide 'standard-vpc' module enforces consistent networking everywhere.State & Remote BackendThe state file tracks what Terraform believes exists in real infrastructure.Remote backend (e.g. S3 + DynamoDB lock) enables safe team collaboration.Security consideration: state files can contain sensitive data - never commit them to Git.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 775PK `\9FJ9!ppt/slides/_rels/slide75.xml.rels PK `\o< ppt/notesSlides/notesSlide75.xml 75PK `\*+ppt/notesSlides/_rels/notesSlide75.xml.rels PK `\T:BBppt/slides/slide76.xml MODULE 7Hands-On Lab: Provision AWS Infrastructure with TerraformFrom zero to a running, code-defined environment 1Write Terraform configuration to create a VPC with public/private subnets. 2Provision an EC2 instance inside that VPC using variables for size and AMI. 3Configure a remote S3 backend with state locking via DynamoDB. 4Run terraform plan and apply, then safely destroy the stack when done.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 776PK `\Ta!ppt/slides/_rels/slide76.xml.rels PK `\*B ppt/notesSlides/notesSlide76.xml 76PK `\My|+ppt/notesSlides/_rels/notesSlide76.xml.rels PK `\zO/O/ppt/slides/slide77.xml Terraform — Best Practices & Pitfalls Best PracticesAlways run and review `terraform plan` before `apply`Use a remote backend with state locking for team environmentsParameterize configuration with variables, not hard-coded valuesOrganize repeated infrastructure patterns into modulesCommon Mistakes to AvoidCommitting .tfstate files to version controlManually editing resources in the AWS Console after they're Terraform-managedSkipping `terraform plan` and applying blind in productionSharing one local state file across multiple team membersAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program77PK `\6q!ppt/slides/_rels/slide77.xml.rels PK `\Uh ppt/notesSlides/notesSlide77.xml 77PK `\ +ppt/notesSlides/_rels/notesSlide77.xml.rels PK `\U=U=ppt/slides/slide78.xml MODULE 7Terraform — Interview Questions Q1. What problem does Infrastructure as Code solve?It replaces manual, undocumented console changes with versioned, reviewable, and repeatable infrastructure definitions. Q2. What is the Terraform state file, and why is it sensitive?It tracks the real-world resources Terraform manages and can contain resource attributes or secrets, so it must never be committed to Git. Q3. Why use a remote backend instead of local state?It enables state locking and shared access so multiple engineers don't overwrite each other's changes or apply from stale state. Q4. What does `terraform plan` do?It compares the current state against the configuration and shows exactly what will be created, changed, or destroyed - before anything happens.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 778PK `\d!ppt/slides/_rels/slide78.xml.rels PK `\Pnڑ ppt/notesSlides/notesSlide78.xml 78PK `\+ppt/notesSlides/_rels/notesSlide78.xml.rels PK `\ipBp:p:ppt/slides/slide79.xml MODULE 7Terraform — Summary & Quiz Key TakeawaysIaC makes infrastructure versioned, repeatable, and reviewable.Providers and resources declare what infrastructure should exist.Variables and outputs make configurations reusable and informative.Modules package repeated infrastructure patterns for reuse.Remote backends with state locking are essential for team use.Quick Quiz1. What are the four core Terraform CLI commands in order?2. Why should the .tfstate file never be committed to Git?3. What does a Terraform 'module' let you do?4. Name one risk of manually editing Terraform-managed resources in the console.5. What locks a remote state file during concurrent applies?AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 779PK `\A!ppt/slides/_rels/slide79.xml.rels PK `\¥I ppt/notesSlides/notesSlide79.xml 79PK `\A.l+ppt/notesSlides/_rels/notesSlide79.xml.rels PK `\mY##ppt/slides/slide80.xml 8MODULE 8Days 36 - 41KubernetesKubernetes architecture, Pods & ReplicaSetsDeployments, Services, ConfigMaps & SecretsIngress & Persistent VolumesHelm basicsAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program80PK `\^23!ppt/slides/_rels/slide80.xml.rels PK `\L  ppt/notesSlides/notesSlide80.xml 80PK `\1A+ppt/notesSlides/_rels/notesSlide80.xml.rels PK `\G&p6p6ppt/slides/slide81.xml MODULE 8Kubernetes — Learning ObjectivesWhere the containers from Module 5 get orchestrated at production scale By the end of this module you canExplain the Kubernetes control plane and worker node architectureDeploy and scale application Pods using Deployments and ReplicaSetsExpose applications internally and externally with Services and Ingress...and apply it hands-on toManage configuration and secrets separately from application codePersist data beyond a Pod's lifecycle with Persistent VolumesPackage and deploy applications using Helm chartsAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 881PK `\y!ppt/slides/_rels/slide81.xml.rels PK `\f; ppt/notesSlides/notesSlide81.xml 81PK `\pZ +ppt/notesSlides/_rels/notesSlide81.xml.rels PK `\%66ppt/slides/slide82.xml MODULE 8Kubernetes ArchitectureThe control plane and workers that run every container at scale Control PlaneAPI Server: the front door for every kubectl command.Scheduler: decides which node a Pod runs on.etcd: the cluster's consistent key-value state store.Worker Nodeskubelet: the agent that runs Pods on each node.Container runtime: actually executes the containers (e.g. containerd).Why it's used: automatically reschedules failed Pods onto healthy nodes.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 882PK `\Q !ppt/slides/_rels/slide82.xml.rels PK `\쨑 ppt/notesSlides/notesSlide82.xml 82PK `\w+ppt/notesSlides/_rels/notesSlide82.xml.rels PK `\b1414ppt/slides/slide83.xml MODULE 8Pods, ReplicaSets & DeploymentsThe core building blocks of running workloads Pods & ReplicaSetsA Pod is the smallest deployable unit - one or more tightly-coupled containers.A ReplicaSet ensures a specified number of identical Pods are always running.DeploymentsManage ReplicaSets and enable rolling updates and rollbacks.Industry example: `kubectl rollout undo` instantly reverts a bad release.Best practice: define resource requests/limits on every Deployment.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 883PK `\v{,k!ppt/slides/_rels/slide83.xml.rels PK `\'o ppt/notesSlides/notesSlide83.xml 83PK `\lz+ppt/notesSlides/_rels/notesSlide83.xml.rels PK `\5RdnDnDppt/slides/slide84.xml MODULE 8Services, ConfigMaps & SecretsNetworking and configuration, decoupled from application code ServicesStable network identity for PodsClusterIP, NodePort, LoadBalancerLoad-balances across replicas ConfigMapsNon-sensitive config, injected as env varsDecouples config from imageUpdate config without rebuilding SecretsBase64-encoded sensitive valuesMounted as files or env varsPair with a vault/KMS for real securityAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 884PK `\L4Z!ppt/slides/_rels/slide84.xml.rels PK `\>nU ppt/notesSlides/notesSlide84.xml 84PK `\t*Ǩ+ppt/notesSlides/_rels/notesSlide84.xml.rels PK `\-J2J2ppt/slides/slide85.xml MODULE 8Ingress & Persistent VolumesExternal access and durable storage for stateful workloads IngressRoutes external HTTP/HTTPS traffic to internal Services based on host/path rules.Industry example: a single Ingress routes /api to one Service and /app to another.Persistent Volumes (PV/PVC)PV: a piece of storage provisioned in the cluster; PVC: a Pod's request for that storage.Common mistake: storing stateful data (like a database) inside a Pod's ephemeral filesystem.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 885PK `\&)!ppt/slides/_rels/slide85.xml.rels PK `\  ppt/notesSlides/notesSlide85.xml 85PK `\51K+ppt/notesSlides/_rels/notesSlide85.xml.rels PK `\ 0__ppt/slides/slide86.xml MODULE 8Helm BasicsPackaging Kubernetes manifests for repeatable deployment 1Chart▸ 2Values.yaml▸ 3Templates▸ 4helm install▸ 5ReleaseA Helm Chart bundles Kubernetes manifests as templates, parameterized by values.yaml for different environments.Industry example: the same chart deploys to dev, staging, and production with only the values file changing.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 886PK `\!ppt/slides/_rels/slide86.xml.rels PK `\[! ppt/notesSlides/notesSlide86.xml 86PK `\u+ppt/notesSlides/_rels/notesSlide86.xml.rels PK `\BE,B,Bppt/slides/slide87.xml MODULE 8Hands-On Lab: Deploy, Scale & Roll Out on KubernetesTaking a containerized app from a single Pod to a resilient service 1Deploy the Dockerized app from Module 5 to a Kubernetes cluster. 2Scale the Deployment to multiple replicas and verify load balancing via a Service. 3Perform a rolling update, then intentionally roll it back. 4Package the application as a Helm chart and install it via `helm install`.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 887PK `\)*!ppt/slides/_rels/slide87.xml.rels PK `\4Ƒ ppt/notesSlides/notesSlide87.xml 87PK `\S+ppt/notesSlides/_rels/notesSlide87.xml.rels PK `\'x+/+/ppt/slides/slide88.xml Kubernetes — Best Practices & Pitfalls Best PracticesAlways set resource requests/limits on PodsUse ConfigMaps and Secrets to decouple config from imagesUse readiness/liveness probes for self-healingPackage repeatable deployments as Helm chartsCommon Mistakes to AvoidRunning stateful workloads without Persistent VolumesStoring real secrets as plain Kubernetes Secrets without a vault/KMSSkipping resource limits, letting one Pod starve the nodeManually editing live cluster objects instead of updating manifestsAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program88PK `\?!ppt/slides/_rels/slide88.xml.rels PK `\!t ppt/notesSlides/notesSlide88.xml 88PK `\ +ppt/notesSlides/_rels/notesSlide88.xml.rels PK `\6q=q=ppt/slides/slide89.xml MODULE 8Kubernetes — Interview Questions Q1. What's the difference between a Pod and a Deployment?A Pod is the smallest running unit; a Deployment manages ReplicaSets of Pods, enabling scaling, rolling updates, and rollbacks. Q2. How does a Kubernetes Service find the right Pods?Through label selectors - the Service routes traffic to any Pod whose labels match its selector, regardless of which node it's on. Q3. Why separate ConfigMaps/Secrets from the container image?So the same image can be promoted across environments unchanged, with only configuration and secrets varying per environment. Q4. What's the role of a Persistent Volume Claim?It's a Pod's request for storage matching certain criteria (size, access mode), which Kubernetes binds to an available Persistent Volume.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 889PK `\Nj`!ppt/slides/_rels/slide89.xml.rels PK `\* ppt/notesSlides/notesSlide89.xml 89PK `\e+ppt/notesSlides/_rels/notesSlide89.xml.rels PK `\DI::ppt/slides/slide90.xml MODULE 8Kubernetes — Summary & Quiz Key TakeawaysThe control plane schedules and manages Pods across worker nodes.Deployments enable rolling updates and easy rollbacks.Services and Ingress expose applications internally and externally.ConfigMaps/Secrets decouple configuration from the container image.Helm packages manifests for repeatable, parameterized deployment.Quick Quiz1. What Kubernetes component decides which node a Pod runs on?2. How do you roll back a bad Deployment release?3. What's the difference between a ClusterIP and a LoadBalancer Service?4. Why shouldn't a database's data live in a Pod's ephemeral storage?5. What file in a Helm chart holds environment-specific values?AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 890PK `\PB!ppt/slides/_rels/slide90.xml.rels PK `\Wu ppt/notesSlides/notesSlide90.xml 90PK `\,3+ppt/notesSlides/_rels/notesSlide90.xml.rels PK `\ ! !ppt/slides/slide91.xml 9MODULE 9Days 42 - 43Monitoring & DevSecOpsPrometheus & GrafanaCloudWatch, SonarQube & TrivyIAM security & secret managementAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program91PK `\w'!ppt/slides/_rels/slide91.xml.rels PK `\ž% ppt/notesSlides/notesSlide91.xml 91PK `\m+ppt/notesSlides/_rels/notesSlide91.xml.rels PK `\8ֹP4P4ppt/slides/slide92.xml MODULE 9Monitoring & DevSecOps — Learning ObjectivesClosing the loop: knowing when something breaks, and catching risk before it ships By the end of this module you canCollect and visualize metrics with Prometheus and GrafanaUse CloudWatch alongside third-party tools for full-stack observabilityScan code quality with SonarQube and container images with Trivy...and apply it hands-on toApply IAM security best practices across the whole stackManage secrets consistently across every tool covered so farAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 992PK `\_O!ppt/slides/_rels/slide92.xml.rels PK `\2* ppt/notesSlides/notesSlide92.xml 92PK `\++ppt/notesSlides/_rels/notesSlide92.xml.rels PK `\L+2+2ppt/slides/slide93.xml MODULE 9Prometheus & GrafanaThe most widely used open-source monitoring stack in DevOps PrometheusPulls (scrapes) metrics from targets on a schedule and stores them as time series.PromQL lets you query and alert on metrics like CPU, memory, and request latency.GrafanaVisualizes Prometheus (and other) data sources as dashboards.Industry example: a Grafana dashboard shows request latency next to error rate, side by side, for fast root-cause analysis.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 993PK `\x!ppt/slides/_rels/slide93.xml.rels PK `\/q ppt/notesSlides/notesSlide93.xml 93PK `\{+ppt/notesSlides/_rels/notesSlide93.xml.rels PK `\e#2#2ppt/slides/slide94.xml MODULE 9CloudWatch, SonarQube & TrivyNative AWS monitoring plus code and image security scanning CloudWatchNative AWS metrics, logs, and alarms - often paired with Prometheus/Grafana for a fuller picture.SonarQube & TrivySonarQube: static code analysis for bugs, vulnerabilities, and code smells.Trivy: scans container images and IaC for known CVEs before deployment.Best practice: fail the CI pipeline if a critical vulnerability is found.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 994PK `\ܿ!ppt/slides/_rels/slide94.xml.rels PK `\WK ppt/notesSlides/notesSlide94.xml 94PK `\ir+ppt/notesSlides/_rels/notesSlide94.xml.rels PK `\Dn+22ppt/slides/slide95.xml MODULE 9IAM Security & Secret ManagementTying every earlier module's security practices together IAM SecurityRegularly audit IAM policies for over-permissive wildcard actions (*).Enforce MFA and rotate access keys on a schedule.Secret ManagementCentralize secrets in Secrets Manager / Parameter Store / Vault - consistently across EC2, Jenkins, Kubernetes.Common mistake: different tools each inventing their own ad-hoc secret storage.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 995PK `\(~!ppt/slides/_rels/slide95.xml.rels PK `\ʌ ppt/notesSlides/notesSlide95.xml 95PK `\(+ppt/notesSlides/_rels/notesSlide95.xml.rels PK `\_hƥ77ppt/slides/slide96.xml MODULE 9Hands-On Lab: Monitor & Scan the StackAdding observability and security scanning to the pipeline built so far 1Install Prometheus and Grafana, and build a dashboard for the EC2/Kubernetes workload. 2Add a Trivy scan stage to the Jenkins pipeline to catch vulnerable container images. 3Run a SonarQube analysis on the application codebase and review the findings.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 996PK `\&!ppt/slides/_rels/slide96.xml.rels PK `\ ppt/notesSlides/notesSlide96.xml 96PK `\jt+ppt/notesSlides/_rels/notesSlide96.xml.rels PK `\2xf/f/ppt/slides/slide97.xml Monitoring & DevSecOps — Best Practices & Pitfalls Best PracticesSet alerts on symptoms (latency, error rate), not just raw resource usageScan every container image before it reaches productionFail builds on critical vulnerabilities rather than just warningAudit IAM policies for wildcard permissions regularlyCommon Mistakes to AvoidMonitoring only CPU/memory while ignoring application-level errorsTreating security scanning as an optional, late-stage stepLetting dashboards go unused - or unmaintained - after setupRotating secrets manually instead of automating itAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program97PK `\'u!ppt/slides/_rels/slide97.xml.rels PK `\j ,ؑ ppt/notesSlides/notesSlide97.xml 97PK `\+ppt/notesSlides/_rels/notesSlide97.xml.rels PK `\!B R==ppt/slides/slide98.xml MODULE 9Monitoring & DevSecOps — Interview Questions Q1. What's the difference between Prometheus and CloudWatch?Prometheus is an open-source, pull-based metrics system popular for Kubernetes; CloudWatch is AWS-native and integrates tightly with AWS services - many teams use both. Q2. Where should a security scan run in a CI/CD pipeline, and why?As early as possible - scanning code with SonarQube and images with Trivy before deployment prevents vulnerable artifacts from ever reaching production. Q3. What is 'Shift Left' in the context of DevSecOps?Moving security and quality checks earlier in the development lifecycle instead of only testing right before release. Q4. Why rotate IAM access keys regularly?To limit the blast radius if a key is ever leaked or compromised, since an old, unrotated key remains valid indefinitely.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 998PK `\~D!ppt/slides/_rels/slide98.xml.rels PK `\6'j ppt/notesSlides/notesSlide98.xml 98PK `\j +ppt/notesSlides/_rels/notesSlide98.xml.rels PK `\[t:t:ppt/slides/slide99.xml MODULE 9Monitoring & DevSecOps — Summary & Quiz Key TakeawaysPrometheus + Grafana form a widely used open-source monitoring stack.CloudWatch provides native AWS observability, often paired with other tools.SonarQube scans code quality; Trivy scans images and IaC for CVEs.DevSecOps shifts security checks earlier in the pipeline.Consistent secret management spans every tool in the toolchain.Quick Quiz1. What does Prometheus use to query metrics?2. What kind of vulnerabilities does Trivy scan for?3. What does 'Shift Left' mean in DevSecOps?4. Name one reason to alert on error rate, not just CPU usage.5. Why centralize secrets instead of letting each tool manage its own?AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 999PK `\!ppt/slides/_rels/slide99.xml.rels PK `\쭑 ppt/notesSlides/notesSlide99.xml 99PK `\q=d+ppt/notesSlides/_rels/notesSlide99.xml.rels PK `\ Y$#$#ppt/slides/slide100.xml 10MODULE 10Days 44 - 45Capstone & Interview PreparationResume building & LinkedIn optimizationGitHub portfolioEnd-to-end capstone projectHR & technical mock interviewsAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program100PK `\"ppt/slides/_rels/slide100.xml.rels PK `\.!ppt/notesSlides/notesSlide100.xml 100PK `\,ppt/notesSlides/_rels/notesSlide100.xml.rels PK `\I66ppt/slides/slide101.xml MODULE 10Resume Building & LinkedIn OptimizationTurning 45 days of hands-on work into a job-winning story ResumeLead with measurable outcomes: 'Automated deployment, cutting release time from 2 hours to 12 minutes.'List the actual tools used: AWS, Docker, Jenkins, Terraform, Kubernetes.Link the capstone project's GitHub repo directly on the resume.LinkedInHeadline: 'AWS DevOps Engineer | CI/CD, Docker, Kubernetes, Terraform'.Post short write-ups of the capstone build to demonstrate real hands-on work.Request recommendations from trainers or peers who reviewed your project.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 10101PK `\(C"ppt/slides/_rels/slide101.xml.rels PK `\1E!ppt/notesSlides/notesSlide101.xml 101PK `\Fkk,ppt/notesSlides/_rels/notesSlide101.xml.rels PK `\kdJ2J2ppt/slides/slide102.xml MODULE 10Building a Standout GitHub PortfolioThe single most-checked artifact by hiring managers in this field What to IncludeA pinned repo for the capstone project with a clear README (architecture diagram, setup steps).Separate small repos for Terraform modules, Jenkinsfiles, and Kubernetes manifests.What Makes It Stand OutMeaningful commit history showing iterative, real progress - not one giant commit.A profile README summarizing your stack and linking your best 3-4 projects.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 10102PK `\U"ppt/slides/_rels/slide102.xml.rels PK `\+z!ppt/notesSlides/notesSlide102.xml 102PK `\,ppt/notesSlides/_rels/notesSlide102.xml.rels PK `\'Tϓqqppt/slides/slide103.xml MODULE 10Capstone Project ArchitectureThe single end-to-end pipeline that proves every module together 1GitHub▸ 2Jenkins▸ 3Docker▸ 4Terraform(AWS Infra)▸ 5Kubernetes▸ 6Prometheus+ GrafanaThe capstone project builds one complete AWS DevOps pipeline: code pushed to GitHub triggers Jenkins, which builds a Docker image, deploys Terraform-provisioned infrastructure, runs the app on Kubernetes, and is monitored via Prometheus and Grafana.This is the single project every resume bullet and interview answer in this module should reference.AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 10103PK `\'0"ppt/slides/_rels/slide103.xml.rels PK `\Tདྷ!ppt/notesSlides/notesSlide103.xml 103PK `\s,ppt/notesSlides/_rels/notesSlide103.xml.rels PK `\+gJgJppt/slides/slide104.xml MODULE 10Mock Interview PreparationPracticing both the human and the technical sides of the interview HR RoundTell me about yourselfWhy DevOps / this program?Walk through your capstoneStrengths & areas to grow Technical RoundExplain your capstone architectureTroubleshoot a failed pipelineWhiteboard a VPC designKubernetes rollback scenario Practice FormatRecorded mock interviewsPeer feedback sessionsSTAR-method answer structureTimed rapid-fire Q&A roundsAITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 10104PK `\P"ppt/slides/_rels/slide104.xml.rels PK `\i!ppt/notesSlides/notesSlide104.xml 104PK `\Bd,ppt/notesSlides/_rels/notesSlide104.xml.rels PK `\٧::ppt/slides/slide105.xml MODULE 10Capstone & Interview Preparation — Summary & Quiz Key TakeawaysA strong resume translates the program into measurable outcomes.GitHub is the portfolio hiring managers check first.The capstone project ties every module into one coherent story.HR and technical mock interviews build real interview confidence.Every artifact - resume, LinkedIn, GitHub - should point back to the same capstone.Quick Quiz1. What single project should your resume, LinkedIn, and GitHub all reference?2. Name one measurable outcome worth highlighting on a resume.3. What services make up the capstone's monitoring layer?4. What does the STAR method structure in an interview answer?5. Why does commit history matter to a hiring manager?AITrustED • AWS DevOps Engineer — 45-Day Job Ready ProgramMODULE 10105PK `\wb*"ppt/slides/_rels/slide105.xml.rels PK `\g@!ppt/notesSlides/notesSlide105.xml 105PK `\* ,ppt/notesSlides/_rels/notesSlide105.xml.rels PK `\띫PPppt/slides/slide106.xml AWS DevOps Career RoadmapThe path from this program into a growing, in-demand career track 1Junior Cloud / Support Engineer0-1 yr▸ 2DevOps Engineer1-3 yrs▸ 3Senior DevOps / SRE3-5 yrs▸ 4Platform / DevOps Architect5+ yrsThis program targets the first rung - Junior Cloud / Support Engineer and DevOps Engineer roles - with a portfolio built to support the next step too.AITrustED • AWS DevOps Engineer — 45-Day Job Ready Program106PK `\_r"ppt/slides/_rels/slide106.xml.rels PK `\ =Ӓ!ppt/notesSlides/notesSlide106.xml 106PK `\,ppt/notesSlides/_rels/notesSlide106.xml.rels PK `\$@CCppt/slides/slide107.xml DevOps Engineer Salary TrendsIndicative ranges - actual compensation varies by city, company size, and negotiation Entry Level (0-2 yrs)India: ~4-8 LPAUS: ~$70k-95kFocus: core AWS + CI/CD basics Mid Level (2-5 yrs)India: ~10-18 LPAUS: ~$100k-140kFocus: IaC, Kubernetes, ownership Senior / SRE (5+ yrs)India: ~20-35+ LPAUS: ~$150k-200k+Focus: architecture, reliability, scaleAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program107Figures are broad, illustrative ranges based on general market reporting and shift over time - verify current numbers with sources like Glassdoor, Levels.fyi, or AmbitionBox before relying on them.PK `\x"ppt/slides/_rels/slide107.xml.rels PK `\-!ppt/notesSlides/notesSlide107.xml 107PK `\2,ppt/notesSlides/_rels/notesSlide107.xml.rels PK `\<4OGOGppt/slides/slide108.xml AWS Certification RoadmapCertifications that reinforce and validate exactly what this program teaches 1AWS Certified Cloud PractitionerFoundational - great starting point 2AWS Certified Solutions Architect - AssociateValidates VPC, EC2, S3, RDS design skills 3AWS Certified DevOps Engineer - ProfessionalThe direct match for this program's outcome 4AWS Certified SysOps Administrator - AssociateStrong complement for operations-heavy rolesAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program108PK `\"ppt/slides/_rels/slide108.xml.rels PK `\v&!ppt/notesSlides/notesSlide108.xml 108PK `\3e,ppt/notesSlides/_rels/notesSlide108.xml.rels PK `\[FFppt/slides/slide109.xml Resume ChecklistRun through this before you submit a single application ✓Quantified impact statements, not just tool names (e.g. 'reduced deploy time by 80%') ✓A clear, top-of-resume skills line: AWS, Docker, Jenkins, Terraform, Kubernetes, Git ✓Capstone project linked directly with a one-line description of what it does ✓GitHub and LinkedIn URLs both present and up to date ✓No unexplained gaps - frame the 45-day program itself as an active period ✓Consistent formatting, one page, reverse-chronological, no spelling errorsAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program109PK `\ё"ppt/slides/_rels/slide109.xml.rels PK `\a!ppt/notesSlides/notesSlide109.xml 109PK `\(,ppt/notesSlides/_rels/notesSlide109.xml.rels PK `\44Ub@b@ppt/slides/slide110.xml GitHub Project IdeasBeyond the capstone - extra repos that round out a portfolio InfrastructureReusable Terraform VPC moduleMulti-environment (dev/stage/prod) IaC repoAuto-scaling web app blueprint CI/CD & ContainersJenkinsfile library for common stacksMulti-stage Dockerfile examples repoGitHub Actions vs Jenkins comparison demo Kubernetes & MonitoringHelm chart for a sample microservicePrometheus + Grafana starter dashboard repoBlue-green deployment demo on KubernetesAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program110PK `\ rg"ppt/slides/_rels/slide110.xml.rels PK `\ 0!ppt/notesSlides/notesSlide110.xml 110PK `\R,ppt/notesSlides/_rels/notesSlide110.xml.rels PK `\}RRppt/slides/slide111.xml Top DevOps Interview QuestionsA sample from the program's full 100-question interview bank 1Explain the CI/CD pipeline you built end-to-end. 2How would you troubleshoot a Pod stuck in CrashLoopBackOff? 3What's your approach to managing secrets across a toolchain? 4Walk through how you'd design a highly available 3-tier app on AWS. 5How do you handle a failed Terraform apply midway through? 6Describe a time a deployment went wrong and how you resolved it.The complete 100-question bank (with model answers) is provided as a companion lab guide to this deck.AITrustED • AWS DevOps Engineer — 45-Day Job Ready Program111PK `\&lW"ppt/slides/_rels/slide111.xml.rels PK `\|!ppt/notesSlides/notesSlide111.xml 111PK `\[j,ppt/notesSlides/_rels/notesSlide111.xml.rels PK `\E??ppt/slides/slide112.xml Learning ResourcesWhere to go deeper on any topic covered in this program Official Docsdocs.aws.amazon.comkubernetes.io/docsdeveloper.hashicorp.com/terraform Hands-On PracticeAWS Free Tier consoleKatacoda / Killercoda scenariosPlay with Docker / Play with Kubernetes Community & UpdatesAWS re:PostCNCF community (Kubernetes)AITrustED alumni networkAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program112PK `\I"ppt/slides/_rels/slide112.xml.rels PK `\e&d!ppt/notesSlides/notesSlide112.xml 112PK `\.J,ppt/notesSlides/_rels/notesSlide112.xml.rels PK `\KP]]ppt/slides/slide113.xml Course Summary45 days, 10 modules, one complete DevOps pipeline in your portfolio1DevOps & AWS Foundations2Linux Administration3Git & GitHub4AWS Core Services5Docker6Jenkins CI/CD7Terraform8Kubernetes9Monitoring & DevSecOps10Capstone & InterviewsAITrustED • AWS DevOps Engineer — 45-Day Job Ready Program113PK `\)l?"ppt/slides/_rels/slide113.xml.rels PK `\&!ppt/notesSlides/notesSlide113.xml 113PK `\5Ʒ,ppt/notesSlides/_rels/notesSlide113.xml.rels PK `\l |ppt/slides/slide114.xml Thank YouLet's build your AWS DevOps Engineer career, one module at a time.AITrustEDwww.aitrusted.in114PK `\^t"ppt/slides/_rels/slide114.xml.rels PK `\ʕƙ!ppt/notesSlides/notesSlide114.xml 114PK `\_se,ppt/notesSlides/_rels/notesSlide114.xml.rels PK `\K !ppt/slideMasters/slideMaster1.xml PK `\N),ppt/slideMasters/_rels/slideMaster1.xml.rels PK `\6TT!ppt/notesMasters/notesMaster1.xml 7/23/19Click to edit Master text stylesSecond levelThird levelFourth levelFifth level‹#›PK `\s **,ppt/notesMasters/_rels/notesMaster1.xml.rels PK `\_rels/PK `\ $docProps/PK `\Kppt/PK `\ mppt/_rels/PK `\ ppt/charts/PK `\ppt/charts/_rels/PK `\ppt/embeddings/PK `\ ppt/media/PK `\Bppt/slideLayouts/PK `\qppt/slideLayouts/_rels/PK `\ppt/slideMasters/PK `\ppt/slideMasters/_rels/PK `\  ppt/slides/PK `\3ppt/slides/_rels/PK `\ bppt/theme/PK `\ppt/notesMasters/PK `\ppt/notesMasters/_rels/PK `\ppt/notesSlides/PK `\ppt/notesSlides/_rels/PK `\撾P[Content_Types].xmlPK `\]] ?_rels/.relsPK `\|--docProps/app.xmlPK `\= docProps/core.xmlPK `\k@@?ppt/_rels/presentation.xml.relsPK `\Oݨ !ppt/theme/theme1.xmlPK `\9Bppt/presentation.xmlPK `\X]ppt/presProps.xmlPK `\^ppt/tableStyles.xmlPK `\D >00_ppt/viewProps.xmlPK `\H7t!Ecppt/slideLayouts/slideLayout1.xmlPK `\ђ77,3fppt/slideLayouts/_rels/slideLayout1.xml.relsPK `\Zo4o4gppt/slides/slide1.xmlPK `\3 Vppt/slides/_rels/slide1.xml.relsPK `\.bppt/notesSlides/notesSlide1.xmlPK `\:A*/ppt/notesSlides/_rels/notesSlide1.xml.relsPK `\c33Bppt/slides/slide2.xmlPK `\2- ppt/slides/_rels/slide2.xml.relsPK `\"ppt/notesSlides/notesSlide2.xmlPK `\xշ*ppt/notesSlides/_rels/notesSlide2.xml.relsPK `\]cOOppt/slides/slide3.xmlPK `\W/ 5ppt/slides/_rels/slide3.xml.relsPK `\K |Ő7ppt/notesSlides/notesSlide3.xmlPK `\9 Y*>ppt/notesSlides/_rels/notesSlide3.xml.relsPK `\O;hDhD@ppt/slides/slide4.xmlPK `\` =ppt/slides/_rels/slide4.xml.relsPK `\vsIppt/notesSlides/notesSlide4.xmlPK `\J *ppt/notesSlides/_rels/notesSlide4.xml.relsPK `\ L66)ppt/slides/slide5.xmlPK `\5 dppt/slides/_rels/slide5.xml.relsPK `\W8pppt/notesSlides/notesSlide5.xmlPK `\Qe*=ppt/notesSlides/_rels/notesSlide5.xml.relsPK `\omPppt/slides/slide6.xmlPK `\ج+ 2|ppt/slides/_rels/slide6.xml.relsPK `\z>~ppt/notesSlides/notesSlide6.xmlPK `\=|* ppt/notesSlides/_rels/notesSlide6.xml.relsPK `\` ,{m{mppt/slides/slide7.xmlPK `\F ppt/slides/_rels/slide7.xml.relsPK `\)lppt/notesSlides/notesSlide7.xmlPK `\|g*ppt/notesSlides/_rels/notesSlide7.xml.relsPK `\xi#i#ppt/slides/slide8.xmlPK `\6 T#ppt/slides/_rels/slide8.xml.relsPK `\iސ`%ppt/notesSlides/notesSlide8.xmlPK `\pO*-,ppt/notesSlides/_rels/notesSlide8.xml.relsPK `\uY^6^6@.ppt/slides/slide9.xmlPK `\>$ dppt/slides/_rels/slide9.xml.relsPK `\qfppt/notesSlides/notesSlide9.xmlPK `\1*mppt/notesSlides/_rels/notesSlide9.xml.relsPK `\Ot‡77oppt/slides/slide10.xmlPK `\Ѳ!xppt/slides/_rels/slide10.xml.relsPK `\O ppt/notesSlides/notesSlide10.xmlPK `\T+Uppt/notesSlides/_rels/notesSlide10.xml.relsPK `\0Y66jppt/slides/slide11.xmlPK `\;!?ppt/slides/_rels/slide11.xml.relsPK `\s6ӑ Mppt/notesSlides/notesSlide11.xmlPK `\O+ppt/notesSlides/_rels/notesSlide11.xml.relsPK `\0JHыы1ppt/slides/slide12.xmlPK `\c!6ppt/slides/_rels/slide12.xml.relsPK `\*)@ Dppt/notesSlides/notesSlide12.xmlPK `\Fb+ppt/notesSlides/_rels/notesSlide12.xml.relsPK `\!(J(J(ppt/slides/slide13.xmlPK `\x!ppt/slides/_rels/slide13.xml.relsPK `\Ї ppt/notesSlides/notesSlide13.xmlPK `\yv+appt/notesSlides/_rels/notesSlide13.xml.relsPK `\#2727vppt/slides/slide14.xmlPK `\O!ppt/slides/_rels/slide14.xml.relsPK `\0 ppt/notesSlides/notesSlide14.xmlPK `\?ݤ+ ppt/notesSlides/_rels/notesSlide14.xml.relsPK `\ (BB"ppt/slides/slide15.xmlPK `\*R!eppt/slides/_rels/slide15.xml.relsPK `\Qz gppt/notesSlides/notesSlide15.xmlPK `\$Q+pnppt/notesSlides/_rels/notesSlide15.xml.relsPK `\}`~M/M/pppt/slides/slide16.xmlPK `\ !ppt/slides/_rels/slide16.xml.relsPK `\  ppt/notesSlides/notesSlide16.xmlPK `\ y+ppt/notesSlides/_rels/notesSlide16.xml.relsPK `\'SG==ppt/slides/slide17.xmlPK `\檋!ppt/slides/_rels/slide17.xml.relsPK `\r. ppt/notesSlides/notesSlide17.xmlPK `\BI+ppt/notesSlides/_rels/notesSlide17.xml.relsPK `\G2tV::ppt/slides/slide18.xmlPK `\Yh!g.ppt/slides/_rels/slide18.xml.relsPK `\ u0ppt/notesSlides/notesSlide18.xmlPK `\N+D7ppt/notesSlides/_rels/notesSlide18.xml.relsPK `\N':#:#Y9ppt/slides/slide19.xmlPK `\~!\ppt/slides/_rels/slide19.xml.relsPK `\0[ ^ppt/notesSlides/notesSlide19.xmlPK `\i+eppt/notesSlides/_rels/notesSlide19.xml.relsPK `\cc|a6a6gppt/slides/slide20.xmlPK `\g_!Nppt/slides/_rels/slide20.xml.relsPK `\7 \ppt/notesSlides/notesSlide20.xmlPK `\SB++ppt/notesSlides/_rels/notesSlide20.xml.relsPK `\+{66@ppt/slides/slide21.xmlPK `\z!ppt/slides/_rels/slide21.xml.relsPK `\89| &ppt/notesSlides/notesSlide21.xmlPK `\HΩ+ppt/notesSlides/_rels/notesSlide21.xml.relsPK `\xII ppt/slides/slide22.xmlPK `\dV!5ppt/slides/_rels/slide22.xml.relsPK `\cQc 7ppt/notesSlides/notesSlide22.xmlPK `\aeZ+=ppt/notesSlides/_rels/notesSlide22.xml.relsPK `\66?ppt/slides/slide23.xmlPK `\A!vppt/slides/_rels/slide23.xml.relsPK `\] xppt/notesSlides/notesSlide23.xmlPK `\ ~t+ppt/notesSlides/_rels/notesSlide23.xml.relsPK `\8$66ppt/slides/slide24.xmlPK `\Y!ppt/slides/_rels/slide24.xml.relsPK `\`z ppt/notesSlides/notesSlide24.xmlPK `\8+uppt/notesSlides/_rels/notesSlide24.xml.relsPK `\mmppt/slides/slide25.xmlPK `\̜|g!1 ppt/slides/_rels/slide25.xml.relsPK `\Y 3 ppt/notesSlides/notesSlide25.xmlPK `\#+y: ppt/notesSlides/_rels/notesSlide25.xml.relsPK `\wLL< ppt/slides/slide26.xmlPK `\5b?! ppt/slides/_rels/slide26.xml.relsPK `\Aʑ ppt/notesSlides/notesSlide26.xmlPK `\${+i ppt/notesSlides/_rels/notesSlide26.xml.relsPK `\| / /~ ppt/slides/slide27.xmlPK `\PG! ppt/slides/_rels/slide27.xml.relsPK `\W  ppt/notesSlides/notesSlide27.xmlPK `\e+ ppt/notesSlides/_rels/notesSlide27.xml.relsPK `\O|'J=J= ppt/slides/slide28.xmlPK `\ [R]!B ppt/slides/_rels/slide28.xml.relsPK `\\ P ppt/notesSlides/notesSlide28.xmlPK `\i+ ppt/notesSlides/_rels/notesSlide28.xml.relsPK `\?CzR:R:4 ppt/slides/slide29.xmlPK `\->w!Q ppt/slides/_rels/slide29.xml.relsPK `\zx S ppt/notesSlides/notesSlide29.xmlPK `\(Lk+Z ppt/notesSlides/_rels/notesSlide29.xml.relsPK `\0;#;#\ ppt/slides/slide30.xmlPK `\*! ppt/slides/_rels/slide30.xml.relsPK `\ q) ) ppt/notesSlides/notesSlide30.xmlPK `\+ ppt/notesSlides/_rels/notesSlide30.xml.relsPK `\,p`W6W6 ppt/slides/slide31.xmlPK `\! ppt/slides/_rels/slide31.xml.relsPK `\ ppt/notesSlides/notesSlide31.xmlPK `\{+u ppt/notesSlides/_rels/notesSlide31.xml.relsPK `\v\y6y6 ppt/slides/slide32.xmlPK `\;!7 ppt/slides/_rels/slide32.xml.relsPK `\lZ} E ppt/notesSlides/notesSlide32.xmlPK `\|+ ppt/notesSlides/_rels/notesSlide32.xml.relsPK `\ߏ!D!D) ppt/slides/slide33.xmlPK `\^r!~R ppt/slides/_rels/slide33.xml.relsPK `\\ T ppt/notesSlides/notesSlide33.xmlPK `\=cu+[[ ppt/notesSlides/_rels/notesSlide33.xml.relsPK `\ 2o66p] ppt/slides/slide34.xmlPK `\iC! ppt/slides/_rels/slide34.xml.relsPK `\鼀 ppt/notesSlides/notesSlide34.xmlPK `\Ŷ+k ppt/notesSlides/_rels/notesSlide34.xml.relsPK `\vAA ppt/slides/slide35.xmlPK `\ ! ppt/slides/_rels/slide35.xml.relsPK `\Q"wG ppt/notesSlides/notesSlide35.xmlPK `\:+ ppt/notesSlides/_rels/notesSlide35.xml.relsPK `\ؒT// ppt/slides/slide36.xmlPK `\! ppt/slides/_rels/slide36.xml.relsPK `\xZԑ  ppt/notesSlides/notesSlide36.xmlPK `\9z+$ ppt/notesSlides/_rels/notesSlide36.xml.relsPK `\#&i=i=& ppt/slides/slide37.xmlPK `\!od ppt/slides/_rels/slide37.xml.relsPK `\4 }f ppt/notesSlides/notesSlide37.xmlPK `\x"+Lm ppt/notesSlides/_rels/notesSlide37.xml.relsPK `\M^F:F:ao ppt/slides/slide38.xmlPK `\!۩ ppt/slides/_rels/slide38.xml.relsPK `\܈ ppt/notesSlides/notesSlide38.xmlPK `\txu+ ppt/notesSlides/_rels/notesSlide38.xml.relsPK `\vS#S#ʹ ppt/slides/slide39.xmlPK `\#y!T ppt/slides/_rels/slide39.xml.relsPK `\NCQf b ppt/notesSlides/notesSlide39.xmlPK `\5cj+1 ppt/notesSlides/_rels/notesSlide39.xml.relsPK `\n}a6a6F ppt/slides/slide40.xmlPK `\ ! ppt/slides/_rels/slide40.xml.relsPK `\`g#q  ppt/notesSlides/notesSlide40.xmlPK `\]+" ppt/notesSlides/_rels/notesSlide40.xml.relsPK `\)lǏ66$ ppt/slides/slide41.xmlPK `\5ne![ ppt/slides/_rels/slide41.xml.relsPK `\趑 ] ppt/notesSlides/notesSlide41.xmlPK `\Fr+md ppt/notesSlides/_rels/notesSlide41.xml.relsPK `\U(I66f ppt/slides/slide42.xmlPK `\ǿ=!T ppt/slides/_rels/slide42.xml.relsPK `\% b ppt/notesSlides/notesSlide42.xmlPK `\/k+1 ppt/notesSlides/_rels/notesSlide42.xml.relsPK `\$p4p4F ppt/slides/slide43.xmlPK `\:! ppt/slides/_rels/slide43.xml.relsPK `\= ppt/notesSlides/notesSlide43.xmlPK `\npjq+ ppt/notesSlides/_rels/notesSlide43.xml.relsPK `\V6ee ppt/slides/slide44.xmlPK `\M!Mppt/slides/_rels/slide44.xml.relsPK `\Eؑ Oppt/notesSlides/notesSlide44.xmlPK `\6+Vppt/notesSlides/_rels/notesSlide44.xml.relsPK `\SψtzDzDXppt/slides/slide45.xmlPK `\j !Qppt/slides/_rels/slide45.xml.relsPK `\8% _ppt/notesSlides/notesSlide45.xmlPK `\-3+.ppt/notesSlides/_rels/notesSlide45.xml.relsPK `\nm44Cppt/slides/slide46.xmlPK `\BYT!ppt/slides/_rels/slide46.xml.relsPK `\ ppt/notesSlides/notesSlide46.xmlPK `\j~+ppt/notesSlides/_rels/notesSlide46.xml.relsPK `\ţ(B(Bppt/slides/slide47.xmlPK `\e<!T*ppt/slides/_rels/slide47.xml.relsPK `\]K b,ppt/notesSlides/notesSlide47.xmlPK `\+++13ppt/notesSlides/_rels/notesSlide47.xml.relsPK `\U5/5/F5ppt/slides/slide48.xmlPK `\76!dppt/slides/_rels/slide48.xml.relsPK `\$ fppt/notesSlides/notesSlide48.xmlPK `\'|+mppt/notesSlides/_rels/notesSlide48.xml.relsPK `\Tv=v=oppt/slides/slide49.xmlPK `\R!Kppt/slides/_rels/slide49.xml.relsPK `\'> Yppt/notesSlides/notesSlide49.xmlPK `\fn+(ppt/notesSlides/_rels/notesSlide49.xml.relsPK `\@w:w:=ppt/slides/slide50.xmlPK `\A!ppt/slides/_rels/slide50.xml.relsPK `\^o ppt/notesSlides/notesSlide50.xmlPK `\K+ppt/notesSlides/_rels/notesSlide50.xml.relsPK `\x##ppt/slides/slide51.xmlPK `\;*!-!ppt/slides/_rels/slide51.xml.relsPK `\Q. ;#ppt/notesSlides/notesSlide51.xmlPK `\ǭ+ *ppt/notesSlides/_rels/notesSlide51.xml.relsPK `\<7@6@6,ppt/slides/slide52.xmlPK `\W4!bppt/slides/_rels/slide52.xml.relsPK `\; dppt/notesSlides/notesSlide52.xmlPK `\2S+pkppt/notesSlides/_rels/notesSlide52.xml.relsPK `\WB44mppt/slides/slide53.xmlPK `\42!ϡppt/slides/_rels/slide53.xml.relsPK `\4 ݣppt/notesSlides/notesSlide53.xmlPK `\sp+ppt/notesSlides/_rels/notesSlide53.xml.relsPK `\%66ppt/slides/slide54.xmlPK `\C (!ppt/slides/_rels/slide54.xml.relsPK `\ |(Ƒ ppt/notesSlides/notesSlide54.xmlPK `\ +ppt/notesSlides/_rels/notesSlide54.xml.relsPK `\ X4X4ppt/slides/slide55.xmlPK `\d`,!$#ppt/slides/_rels/slide55.xml.relsPK `\ 2%ppt/notesSlides/notesSlide55.xmlPK `\І+,ppt/notesSlides/_rels/notesSlide55.xml.relsPK `\JhJh.ppt/slides/slide56.xmlPK `\L2!ppt/slides/_rels/slide56.xml.relsPK `\lΒ ppt/notesSlides/notesSlide56.xmlPK `\w+qppt/notesSlides/_rels/notesSlide56.xml.relsPK `\yAAppt/slides/slide57.xmlPK `\kp!ppt/slides/_rels/slide57.xml.relsPK `\&U ppt/notesSlides/notesSlide57.xmlPK `\6+ppt/notesSlides/_rels/notesSlide57.xml.relsPK `\ײn)/)/ppt/slides/slide58.xmlPK `\!ppt/slides/_rels/slide58.xml.relsPK `\  ppt/notesSlides/notesSlide58.xmlPK `\:v+&ppt/notesSlides/_rels/notesSlide58.xml.relsPK `\!.==(ppt/slides/slide59.xmlPK `\'!6fppt/slides/_rels/slide59.xml.relsPK `\  Dhppt/notesSlides/notesSlide59.xmlPK `\{mEo+oppt/notesSlides/_rels/notesSlide59.xml.relsPK `\vAQ:Q:(qppt/slides/slide60.xmlPK `\O-t!ppt/slides/_rels/slide60.xml.relsPK `\&L ppt/notesSlides/notesSlide60.xmlPK `\+ppt/notesSlides/_rels/notesSlide60.xml.relsPK `\!ir##ppt/slides/slide61.xmlPK `\hH!ppt/slides/_rels/slide61.xml.relsPK `\d ppt/notesSlides/notesSlide61.xmlPK `\ּ+ppt/notesSlides/_rels/notesSlide61.xml.relsPK `\'2626ppt/slides/slide62.xmlPK `\@٭!Fppt/slides/_rels/slide62.xml.relsPK `\CI Tppt/notesSlides/notesSlide62.xmlPK `\+#$ppt/notesSlides/_rels/notesSlide62.xml.relsPK `\r2@668&ppt/slides/slide63.xmlPK `\g,!\ppt/slides/_rels/slide63.xml.relsPK `\Nߑ _ppt/notesSlides/notesSlide63.xmlPK `\Tr+eppt/notesSlides/_rels/notesSlide63.xml.relsPK `\Q1%T4T4gppt/slides/slide64.xmlPK `\!xppt/slides/_rels/slide64.xml.relsPK `\6b ppt/notesSlides/notesSlide64.xmlPK `\Ԡ+Uppt/notesSlides/_rels/notesSlide64.xml.relsPK `\ϥGqDqDjppt/slides/slide65.xmlPK `\7!ppt/slides/_rels/slide65.xml.relsPK `\~" ppt/notesSlides/notesSlide65.xmlPK `\X+ppt/notesSlides/_rels/notesSlide65.xml.relsPK `\yȩ_t_tppt/slides/slide66.xmlPK `\!kppt/slides/_rels/slide66.xml.relsPK `\ mppt/notesSlides/notesSlide66.xmlPK `\P}+qtppt/notesSlides/_rels/notesSlide66.xml.relsPK `\3-B-Bvppt/slides/slide67.xmlPK `\8E!ppt/slides/_rels/slide67.xml.relsPK `\lOv ppt/notesSlides/notesSlide67.xmlPK `\@+ppt/notesSlides/_rels/notesSlide67.xml.relsPK `\C?/?/ppt/slides/slide68.xmlPK `\!Lppt/slides/_rels/slide68.xml.relsPK `\WDđ Zppt/notesSlides/notesSlide68.xmlPK `\q+)ppt/notesSlides/_rels/notesSlide68.xml.relsPK `\t=t=>ppt/slides/slide69.xmlPK `\t'!;ppt/slides/_rels/slide69.xml.relsPK `\a =ppt/notesSlides/notesSlide69.xmlPK `\\jm+Dppt/notesSlides/_rels/notesSlide69.xml.relsPK `\dYH:H:Fppt/slides/slide70.xmlPK `\Ai!Tppt/slides/_rels/slide70.xml.relsPK `\-iR bppt/notesSlides/notesSlide70.xmlPK `\Z +1ppt/notesSlides/_rels/notesSlide70.xml.relsPK `\LY##Fppt/slides/slide71.xmlPK `\fLP!ppt/slides/_rels/slide71.xml.relsPK `\梕 ppt/notesSlides/notesSlide71.xmlPK `\A+vppt/notesSlides/_rels/notesSlide71.xml.relsPK `\9t6t6ppt/slides/slide72.xmlPK `\NqR!3ppt/slides/_rels/slide72.xml.relsPK `\༏ Appt/notesSlides/notesSlide72.xmlPK `\l8+ppt/notesSlides/_rels/notesSlide72.xml.relsPK `\.[66%ppt/slides/slide73.xmlPK `\iw!2ppt/slides/_rels/slide73.xml.relsPK `\rwD 5ppt/notesSlides/notesSlide73.xmlPK `\Iws+;ppt/notesSlides/_rels/notesSlide73.xml.relsPK `\\2b4b4=ppt/slides/slide74.xmlPK `\#o!rppt/slides/_rels/slide74.xml.relsPK `\O tppt/notesSlides/notesSlide74.xmlPK `\1a+b{ppt/notesSlides/_rels/notesSlide74.xml.relsPK `\k$44w}ppt/slides/slide75.xmlPK `\9FJ9!Mppt/slides/_rels/slide75.xml.relsPK `\o< [ppt/notesSlides/notesSlide75.xmlPK `\*+*ppt/notesSlides/_rels/notesSlide75.xml.relsPK `\T:BB?ppt/slides/slide76.xmlPK `\Ta!ppt/slides/_rels/slide76.xml.relsPK `\*B ppt/notesSlides/notesSlide76.xmlPK `\My|+mppt/notesSlides/_rels/notesSlide76.xml.relsPK `\zO/O/ ppt/slides/slide77.xmlPK `\6q!:ppt/slides/_rels/slide77.xml.relsPK `\Uh <ppt/notesSlides/notesSlide77.xmlPK `\ +Bppt/notesSlides/_rels/notesSlide77.xml.relsPK `\U=U=Dppt/slides/slide78.xmlPK `\d!ppt/slides/_rels/slide78.xml.relsPK `\Pnڑ ppt/notesSlides/notesSlide78.xmlPK `\+]ppt/notesSlides/_rels/notesSlide78.xml.relsPK `\ipBp:p:rppt/slides/slide79.xmlPK `\A!ppt/slides/_rels/slide79.xml.relsPK `\¥I $ppt/notesSlides/notesSlide79.xmlPK `\A.l+ppt/notesSlides/_rels/notesSlide79.xml.relsPK `\mY##ppt/slides/slide80.xmlPK `\^23!Sppt/slides/_rels/slide80.xml.relsPK `\L  appt/notesSlides/notesSlide80.xmlPK `\1A+0ppt/notesSlides/_rels/notesSlide80.xml.relsPK `\G&p6p6Eppt/slides/slide81.xmlPK `\y!7ppt/slides/_rels/slide81.xml.relsPK `\f; 9ppt/notesSlides/notesSlide81.xmlPK `\pZ +@ppt/notesSlides/_rels/notesSlide81.xml.relsPK `\%66Bppt/slides/slide82.xmlPK `\Q !'yppt/slides/_rels/slide82.xml.relsPK `\쨑 5{ppt/notesSlides/notesSlide82.xmlPK `\w+ppt/notesSlides/_rels/notesSlide82.xml.relsPK `\b1414ppt/slides/slide83.xmlPK `\v{,k!~ppt/slides/_rels/slide83.xml.relsPK `\'o ppt/notesSlides/notesSlide83.xmlPK `\lz+[ppt/notesSlides/_rels/notesSlide83.xml.relsPK `\5RdnDnDpppt/slides/slide84.xmlPK `\L4Z!ppt/slides/_rels/slide84.xml.relsPK `\>nU ppt/notesSlides/notesSlide84.xmlPK `\t*Ǩ+ppt/notesSlides/_rels/notesSlide84.xml.relsPK `\-J2J2ppt/slides/slide85.xmlPK `\&)!Eppt/slides/_rels/slide85.xml.relsPK `\  Gppt/notesSlides/notesSlide85.xmlPK `\51K+_Nppt/notesSlides/_rels/notesSlide85.xml.relsPK `\ 0__tPppt/slides/slide86.xmlPK `\!ppt/slides/_rels/slide86.xml.relsPK `\[! ppt/notesSlides/notesSlide86.xmlPK `\u+^ppt/notesSlides/_rels/notesSlide86.xml.relsPK `\BE,B,Bsppt/slides/slide87.xmlPK `\)*!ppt/slides/_rels/slide87.xml.relsPK `\4Ƒ ppt/notesSlides/notesSlide87.xmlPK `\S+ppt/notesSlides/_rels/notesSlide87.xml.relsPK `\'x+/+/ppt/slides/slide88.xmlPK `\?!$8ppt/slides/_rels/slide88.xml.relsPK `\!t 2:ppt/notesSlides/notesSlide88.xmlPK `\ +Appt/notesSlides/_rels/notesSlide88.xml.relsPK `\6q=q=Cppt/slides/slide89.xmlPK `\Nj`!ppt/slides/_rels/slide89.xml.relsPK `\* ɂppt/notesSlides/notesSlide89.xmlPK `\e+ppt/notesSlides/_rels/notesSlide89.xml.relsPK `\DI::ppt/slides/slide90.xmlPK `\PB!lppt/slides/_rels/slide90.xml.relsPK `\Wu zppt/notesSlides/notesSlide90.xmlPK `\,3+Ippt/notesSlides/_rels/notesSlide90.xml.relsPK `\ ! !^ppt/slides/slide91.xmlPK `\w'!ppt/slides/_rels/slide91.xml.relsPK `\ž% ppt/notesSlides/notesSlide91.xmlPK `\m+{ppt/notesSlides/_rels/notesSlide91.xml.relsPK `\8ֹP4P4ppt/slides/slide92.xmlPK `\_O!2ppt/slides/_rels/slide92.xml.relsPK `\2* "4ppt/notesSlides/notesSlide92.xmlPK `\++:ppt/notesSlides/_rels/notesSlide92.xml.relsPK `\L+2+2=ppt/slides/slide93.xmlPK `\x!eoppt/slides/_rels/slide93.xml.relsPK `\/q sqppt/notesSlides/notesSlide93.xmlPK `\{+Bxppt/notesSlides/_rels/notesSlide93.xml.relsPK `\e#2#2Wzppt/slides/slide94.xmlPK `\ܿ!ppt/slides/_rels/slide94.xml.relsPK `\WK ppt/notesSlides/notesSlide94.xmlPK `\ir+ppt/notesSlides/_rels/notesSlide94.xml.relsPK `\Dn+22ppt/slides/slide95.xmlPK `\(~!ppt/slides/_rels/slide95.xml.relsPK `\ʌ ppt/notesSlides/notesSlide95.xmlPK `\(+ppt/notesSlides/_rels/notesSlide95.xml.relsPK `\_hƥ77ppt/slides/slide96.xmlPK `\&!,ppt/slides/_rels/slide96.xml.relsPK `\ .ppt/notesSlides/notesSlide96.xmlPK `\jt+5ppt/notesSlides/_rels/notesSlide96.xml.relsPK `\2xf/f/7ppt/slides/slide97.xmlPK `\'u!Jgppt/slides/_rels/slide97.xml.relsPK `\j ,ؑ Xippt/notesSlides/notesSlide97.xmlPK `\+'pppt/notesSlides/_rels/notesSlide97.xml.relsPK `\!B R==