[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"cheat-sheet---en":3,"domain-info---en":3,"topic-info----en":3,"lesson-cloud-computing-fundamentals-security-and-reliability-cloud-security-governance-and-compliance-en":4,"prev-cloud-computing-fundamentals-security-and-reliability-cloud-security-governance-and-compliance-en":326,"next-cloud-computing-fundamentals-security-and-reliability-cloud-security-governance-and-compliance-en":544},null,{"locked":5,"reason":3,"meta":6,"item":16},false,{"title":7,"description":8,"isFree":5,"estimatedMinutes":9,"difficulty":10,"learningObjectives":11},"Governance and Compliance","How cloud governance sets an organization's own rules for resource use, how compliance proves those rules satisfy an external framework or regulation, and where a provider's certifications end and a customer's own evidence has to begin.",18,"intermediate",[12,13,14,15],"Distinguish governance from compliance and explain what each one is answering","Compare ISO 27001, SOC 2, PCI DSS, HIPAA, and GDPR by what each covers and who typically needs it","Explain what a provider's compliance report proves and what it leaves for the customer to demonstrate separately","Distinguish data residency from data sovereignty and identify which one a scenario is actually testing",{"id":17,"title":7,"body":18,"description":8,"difficulty":10,"estimatedMinutes":9,"extension":261,"infographics":262,"isFree":5,"learningObjectives":263,"meta":264,"navigation":265,"path":266,"quiz":267,"seo":323,"stem":324,"__hash__":325},"courses/courses/cloud-computing-fundamentals/en/domains/03-security-and-reliability/01-cloud-security/04-governance-and-compliance.md",{"type":19,"value":20,"toc":247},"minimark",[21,26,30,33,37,40,43,47,143,146,150,153,157,160,163,167,170,174,177,181,240,244],[22,23,25],"h2",{"id":24},"a-certificate-that-didnt-cover-what-they-thought","A certificate that didn't cover what they thought",[27,28,29],"p",{},"A healthcare startup signs up with a major cloud provider, sees the SOC 2 and ISO 27001 badges on the provider's compliance page, and tells its board the platform is HIPAA-compliant. Months later, an actual HIPAA audit asks for the startup's own access logs, its encryption configuration, and records of staff security training, none of which the provider's certifications ever claimed to cover.",[27,31,32],{},"This is the same gap the first lesson in this topic named as a misconception, now playing out in full: a provider's certification proves its own infrastructure meets a standard. Whether the application built on top of it meets that same standard is a separate question, and it's exactly what governance and compliance, as a discipline, exist to answer.",[22,34,36],{"id":35},"governance-asks-inward-compliance-points-outward","Governance asks inward, compliance points outward",[27,38,39],{},"Governance is an organization's own rulebook for how its cloud resources get configured and used: who reviews access requests, how resources get tagged, what configuration baseline every new service has to meet before it goes live. It's internally driven, and a company can have strong governance with no external framework in play at all.",[27,41,42],{},"Compliance is different: it's proving, to an auditor, a regulator, or a customer's own procurement team, that an organization's practices meet a specific external bar. That bar might be a certifiable standard a company chooses to pursue, or a law it has no choice but to satisfy. Good governance makes compliance easier to demonstrate, but the two answer different questions: governance asks \"are we doing this consistently,\" compliance asks \"can we prove it to someone outside the organization.\"",[22,44,46],{"id":45},"the-compliance-landscape-what-each-framework-actually-covers","The compliance landscape: what each framework actually covers",[48,49,50,69],"table",{},[51,52,53],"thead",{},[54,55,56,60,63,66],"tr",{},[57,58,59],"th",{},"Framework",[57,61,62],{},"What it covers",[57,64,65],{},"Who typically needs it",[57,67,68],{},"Certification or law",[70,71,72,87,101,115,129],"tbody",{},[54,73,74,78,81,84],{},[75,76,77],"td",{},"ISO 27001",[75,79,80],{},"A full information security management system: risk assessment, access control, incident management",[75,82,83],{},"Any organization, internationally recognized",[75,85,86],{},"Certification, valid 3 years",[54,88,89,92,95,98],{},[75,90,91],{},"SOC 2",[75,93,94],{},"Five trust service criteria: security, availability, processing integrity, confidentiality, privacy",[75,96,97],{},"US-focused, especially SaaS and tech vendors",[75,99,100],{},"Attestation report, an auditor's opinion",[54,102,103,106,109,112],{},[75,104,105],{},"PCI DSS",[75,107,108],{},"Protecting payment card data specifically, 12 requirements from network security to access restriction",[75,110,111],{},"Any organization that stores, processes, or transmits cardholder data",[75,113,114],{},"Certifiable standard",[54,116,117,120,123,126],{},[75,118,119],{},"HIPAA",[75,121,122],{},"Protecting patient health information (PHI)",[75,124,125],{},"US healthcare organizations and their vendors",[75,127,128],{},"US federal law",[54,130,131,134,137,140],{},[75,132,133],{},"GDPR",[75,135,136],{},"Personal data of individuals in the EU, including international transfer rules",[75,138,139],{},"Any organization handling EU residents' personal data, regardless of where the organization is based",[75,141,142],{},"EU law",[27,144,145],{},"ISO 27001 and SOC 2 overlap substantially in the controls they check, enough that a well-run compliance program can often satisfy both without duplicating the work, but they serve different audiences: SOC 2 is what a US enterprise customer usually asks for, ISO 27001 is what an international one usually expects.",[22,147,149],{"id":148},"where-to-find-the-providers-half-of-the-evidence","Where to find the provider's half of the evidence",[27,151,152],{},"A cloud provider doesn't email its compliance reports on request; it publishes them through a self-service portal. AWS's version is called AWS Artifact, giving any account on-demand access to AWS's own SOC 1/2/3, ISO, and PCI reports, each generated with a unique watermark for the requester. That portal is the customer's starting point when an auditor asks \"show me the provider's controls,\" and it's free to use. What it can never hand over is the other half of the evidence, the customer's own configuration, access logs, and internal processes, because AWS Artifact only documents AWS's side of the shared responsibility line.",[22,154,156],{"id":155},"data-residency-versus-data-sovereignty","Data residency versus data sovereignty",[27,158,159],{},"These two terms get used interchangeably, and the exam boundary between them is worth naming explicitly. Data residency is about physical location: where, geographically, is the data stored. Data sovereignty is about legal jurisdiction: whose laws govern that data, regardless of where it happens to sit.",[27,161,162],{},"GDPR is a useful case study because it clarifies which one it actually cares about. GDPR does not require EU personal data to physically stay inside the EU. What it requires, under its rules on international transfers, is that any transfer of personal data outside the EU or EEA receive protection that's essentially equivalent to what GDPR itself provides, through mechanisms like an adequacy decision covering the destination country, or standard contractual clauses between sender and receiver. A company can choose an EU cloud region for good operational reasons, lower latency to EU users, a simpler story for customers, but doing so addresses residency, a location question. It does not, by itself, satisfy the legal transfer question GDPR is actually asking if that same data later gets copied, backed up, or processed somewhere outside the EU.",[22,164,166],{"id":165},"a-worked-example-choosing-a-region-for-eu-personal-data","A worked example: choosing a region for EU personal data",[27,168,169],{},"Say a team is building a service that stores personal data belonging to EU residents. Picking an EU-based region keeps that data physically close to its users and gives a simple answer to \"where does our data live.\" But the team still has to check every place that data travels afterward: a support tool hosted outside the EU, an analytics pipeline in a US region, a backup replicated to another continent. Each of those is a transfer under GDPR's Chapter 5 rules, and each one needs its own legal basis, an adequacy decision for that destination, or contractual clauses, regardless of how carefully the primary region was chosen.",[22,171,173],{"id":172},"misconception-revisited-inheriting-a-badge","Misconception, revisited: inheriting a badge",[27,175,176],{},"The first lesson in this topic named this misconception in the context of security generally; here it is the specific, recurring compliance mistake: assuming a provider's certification transfers automatically to whatever a customer builds on top of it. It never does. AWS Artifact, or its equivalent on any provider, hands over evidence of the provider's own controls. The customer still has to assemble evidence of its own: access reviews, encryption configuration from the previous lesson, employee training, incident response processes, everything that HIPAA, PCI DSS, or a customer's own security questionnaire actually asks to see.",[22,178,180],{"id":179},"exam-cues-matching-a-scenario-to-a-framework","Exam cues: matching a scenario to a framework",[48,182,183,193],{},[51,184,185],{},[54,186,187,190],{},[57,188,189],{},"The scenario says...",[57,191,192],{},"Points to",[70,194,195,202,209,216,224,232],{},[54,196,197,200],{},[75,198,199],{},"\"Patient health information,\" \"healthcare provider\"",[75,201,119],{},[54,203,204,207],{},[75,205,206],{},"\"Credit card data,\" \"cardholder data environment\"",[75,208,105],{},[54,210,211,214],{},[75,212,213],{},"\"Personal data of EU individuals,\" \"international transfer\"",[75,215,133],{},[54,217,218,221],{},[75,219,220],{},"\"Where our data is physically stored\"",[75,222,223],{},"Data residency",[54,225,226,229],{},[75,227,228],{},"\"Whose laws apply to our data\"",[75,230,231],{},"Data sovereignty",[54,233,234,237],{},[75,235,236],{},"\"Need the provider's own audit reports\"",[75,238,239],{},"AWS Artifact, or the provider's equivalent portal",[22,241,243],{"id":242},"where-this-leaves-you","Where this leaves you",[27,245,246],{},"Compliance is never something a customer inherits wholesale from a provider's badge page; it's something assembled from the provider's certified infrastructure plus the customer's own controls layered on top, the exact same boundary the shared responsibility model drew at the start of this topic, now applied specifically to proving it to an outsider. That closes out Cloud Security: you can now name who owns which security task, how identity and encryption enforce that ownership, and how governance and compliance prove it holds up under audit. The next topic in this domain leaves security behind and asks a different question entirely: once a system is secure, how does it stay running.",{"title":248,"searchDepth":249,"depth":249,"links":250},"",3,[251,253,254,255,256,257,258,259,260],{"id":24,"depth":252,"text":25},2,{"id":35,"depth":252,"text":36},{"id":45,"depth":252,"text":46},{"id":148,"depth":252,"text":149},{"id":155,"depth":252,"text":156},{"id":165,"depth":252,"text":166},{"id":172,"depth":252,"text":173},{"id":179,"depth":252,"text":180},{"id":242,"depth":252,"text":243},"md",[],[12,13,14,15],{},true,"/courses/cloud-computing-fundamentals/en/domains/03-security-and-reliability/01-cloud-security/04-governance-and-compliance",{"passingScore":268,"questions":269},70,[270,279,287,291,297,305,313],{"question":271,"type":272,"options":273,"correctAnswer":276,"explanation":278},"A healthcare startup sees the SOC 2 and ISO 27001 badges on its cloud provider's compliance page and tells its board the platform is fully HIPAA-compliant. An auditor later asks for the startup's own access logs, encryption configuration, and staff training records. What did the startup get wrong?","single",[274,275,276,277],"Nothing; the provider's certifications cover HIPAA automatically","SOC 2 and ISO 27001 aren't real compliance frameworks","It assumed the provider's infrastructure certifications covered its own application-level controls, which HIPAA also requires evidence for","HIPAA does not apply to healthcare data stored in the cloud","This is the same boundary the shared responsibility model draws for security, applied to compliance: a provider's certification proves its own infrastructure meets a standard, but a customer's access controls, encryption configuration, and internal processes need their own separate compliance evidence.",{"question":280,"type":272,"options":281,"correctAnswer":283,"explanation":286},"What is the clearest distinction between governance and compliance in a cloud context?",[282,283,284,285],"They are two names for the same activity","Governance is an organization's own rules for how cloud resources are configured and used; compliance is proving those rules satisfy an external framework or regulation","Governance only applies to cost management, and compliance only applies to security","Compliance is optional, while governance is legally required","Governance is internally driven, an organization deciding its own policies for access review, tagging, or configuration standards. Compliance points outward, demonstrating to an auditor, regulator, or customer that those internal practices meet a specific external bar, whether that bar is a certifiable standard or a legal requirement.",{"question":288,"type":272,"options":289,"correctAnswer":105,"explanation":290},"A company processes credit card payments directly and needs to prove it protects cardholder data. Which framework specifically governs this?",[119,133,105,77],"PCI DSS is built specifically around protecting payment card data, with 12 requirements covering everything from network security to restricting access by business need to know. HIPAA covers health data, GDPR covers personal data of EU individuals, and ISO 27001 is a general information security management standard, not payment-specific.",{"question":292,"type":272,"options":293,"correctAnswer":295,"explanation":296},"ISO 27001 and SOC 2 are functionally identical, so a company that has one never needs to pursue the other.",[294,295],"True","False","ISO 27001 is an internationally recognized certification for an information security management system, valid for three years and widely expected outside the US. SOC 2 is a US-focused attestation report evaluated against five trust service criteria. Their controls overlap substantially, but a company selling into both US and international markets often ends up needing both.",{"question":298,"type":272,"options":299,"correctAnswer":300,"explanation":304},"A team wants to hand its auditor AWS's own SOC 2 and PCI reports as part of a compliance review, without contacting an AWS sales representative. Which AWS service is built exactly for this?",[300,301,302,303],"AWS Artifact","AWS IAM","AWS KMS","Amazon CloudWatch","AWS Artifact is a self-service portal giving any AWS account on-demand access to AWS's own compliance reports, including SOC 1/2/3, ISO, and PCI documentation, each generated with a unique watermark. It's the customer's way to retrieve the provider's half of the compliance evidence without a manual request process.",{"question":306,"type":272,"options":307,"correctAnswer":310,"explanation":312},"A company decides to store all EU customer data in an EU-based cloud region and concludes this alone satisfies GDPR's requirements for that data. What does this conclusion overlook?",[308,309,310,311],"GDPR does not apply to data stored in the EU","GDPR requires all data to be stored outside the EU","Data residency, where data physically sits, is different from GDPR's actual requirement, which governs international transfers and requires adequate protection wherever data eventually moves","Storing data in a specific region has no relationship to any compliance framework","GDPR itself does not mandate that personal data stay physically inside the EU. What it mandates is that any transfer outside the EU or EEA receive essentially equivalent protection, through mechanisms like an adequacy decision or standard contractual clauses. Choosing an EU region is a reasonable practice, but it addresses data residency, a physical-location question, not the legal-transfer question GDPR is actually asking.",{"question":314,"type":315,"options":316,"correctAnswers":321,"explanation":322},"Which of the following are true about NIST SP 800-144, the guidelines on security and privacy in public cloud computing? (Select all that apply.)","multiple",[317,318,319,320],"It is published by the US National Institute of Standards and Technology","It is a legally binding regulation enforced worldwide","It discusses security and privacy challenges and safeguards for organizations moving to public cloud","It is aimed at people making decisions about cloud computing initiatives, including security professionals and IT managers",[317,319,320],"NIST publications like SP 800-144 are guidance documents, widely referenced and often required for US federal systems, but not a global legal mandate in the way GDPR is. They're written for the people actually deciding how an organization approaches cloud security, from executives to system administrators.",{"title":7,"description":8},"courses/cloud-computing-fundamentals/en/domains/03-security-and-reliability/01-cloud-security/04-governance-and-compliance","_PCoeERQGlRTd0TQ-nUyl6XNcQqfriWuYbxryLMEJ28",{"locked":5,"reason":3,"meta":327,"item":337},{"title":328,"description":329,"isFree":5,"estimatedMinutes":330,"difficulty":10,"learningObjectives":331},"Encryption and Data Protection","How encryption at rest and encryption in transit protect data at different points in its journey, how key management keeps encrypted data useless to anyone without permission, and where encryption's protection ends.",19,[332,333,334,335,336],"Distinguish encryption at rest from encryption in transit and identify which point in a request each one protects","Explain how AES-256 and TLS map to at-rest and in-transit protection respectively","Describe the isolation model behind managed key services and why it separates data access from key access","Compare a managed key service against a dedicated hardware security module and identify when each fits","Correct the misconception that encryption alone replaces the need for access control",{"id":338,"title":328,"body":339,"description":329,"difficulty":10,"estimatedMinutes":330,"extension":261,"infographics":471,"isFree":5,"learningObjectives":483,"meta":484,"navigation":265,"path":485,"quiz":486,"seo":541,"stem":542,"__hash__":543},"courses/courses/cloud-computing-fundamentals/en/domains/03-security-and-reliability/01-cloud-security/03-encryption-and-data-protection.md",{"type":19,"value":340,"toc":460},[341,345,348,351,354,358,361,364,368,371,374,379,383,386,390,393,397,400,404,407,411,455,457],[22,342,344],{"id":343},"the-same-file-two-different-risks","The same file, two different risks",[27,346,347],{},"A support engineer debugging an issue captures network traffic between an app and its database while sitting in a coffee shop. If that connection is not encrypted, the engineer, or anyone else on the same Wi-Fi running the same capture, can read every password and every field moving through it, in plain text, as it happens.",[27,349,350],{},"Now picture a different moment entirely: months later, a decommissioned backup drive from that same database is sold or discarded without being wiped, and someone plugs it in. If the data on it was never encrypted, they can read it directly off the disk, no network capture required.",[27,352,353],{},"Same data, two completely different attack points, months apart. Protecting against one does nothing to protect against the other, which is why cloud platforms treat them as two separate controls: encryption in transit for data on the move, and encryption at rest for data sitting still.",[22,355,357],{"id":356},"encryption-at-rest-aes-256-and-server-side-encryption","Encryption at rest: AES-256 and server-side encryption",[27,359,360],{},"Encryption at rest protects data written to storage, disks, backups, database files, so that anyone who gains access to the physical or logical storage medium without authorization sees only unreadable ciphertext. The standard mechanism across every major cloud provider is AES-256, the 256-bit Advanced Encryption Standard block cipher, applied automatically or on request to data as it's written.",[27,362,363],{},"AWS calls its default approach server-side encryption: the storage service itself encrypts data before writing it and decrypts it on the way back out, all inside the service, using keys managed through a key management system. A customer typically doesn't touch the cipher directly; they choose a key management option and the storage service handles the rest.",[22,365,367],{"id":366},"encryption-in-transit-tls","Encryption in transit: TLS",[27,369,370],{},"Encryption in transit protects data while it's moving between two points on a network, a mobile app and a server, a load balancer and an application instance, one microservice and another. The standard mechanism is TLS, Transport Layer Security, which wraps a connection so that anyone capturing the raw network traffic sees only ciphertext, not the request or response itself.",[27,372,373],{},"As of mid-2024, every AWS API endpoint requires at least TLS 1.2 and supports TLS 1.3, the newer, faster version of the protocol. That baseline reflects an industry-wide pattern: older TLS versions and their predecessor, SSL, get retired as cryptographic weaknesses accumulate, and current guidance keeps pushing the accepted minimum forward.",[375,376],"infographic",{"alt":377,"slug":378},"A diagram tracing a request from client through network to server to storage, showing TLS protecting the network segment as data moves and AES-256 protecting the storage segment where data comes to rest.","encryption-and-data-protection-request-path",[22,380,382],{"id":381},"the-gap-in-the-middle-data-in-use","The gap in the middle: data in use",[27,384,385],{},"Notice what neither protection covers. Once a request reaches the application server, the data has to be decrypted in memory, briefly, for the application to actually do anything with it, run a calculation, render a page, check a condition. That in-memory state is sometimes called data in use, and it sits outside what standard at-rest and in-transit encryption reach. It is a narrower, more specialized problem, and it is why \"encrypted everywhere\" is a simplification: encryption at rest and in transit cover the overwhelming majority of a request's journey, but not the instant the application is actively working with the plaintext.",[22,387,389],{"id":388},"key-management-separating-who-can-decrypt-from-who-holds-the-key","Key management: separating who can decrypt from who holds the key",[27,391,392],{},"Encrypting data is only half the problem; controlling who can decrypt it is the other half, and that is what a key management service does. AWS KMS runs inside hardware security modules built so that plaintext keys never leave the module, not even for AWS's own employees. A request to encrypt or decrypt something is authorized independently through the same IAM permissions covered in the previous lesson, which means access to the data and access to the key that unlocks it are two separately controlled layers. Compromising one does not automatically hand over the other, and every use of a key gets logged, giving an auditable trail of exactly when and by whom a piece of data was decrypted.",[22,394,396],{"id":395},"the-boundary-managed-key-service-versus-dedicated-hardware","The boundary: managed key service versus dedicated hardware",[27,398,399],{},"Most workloads use a managed key service like AWS KMS: shared, multi-tenant hardware behind a simple API, with AWS handling provisioning, patching, and availability. Some workloads, usually driven by a specific regulatory requirement, need a dedicated hardware security module instead, like AWS CloudHSM, giving the customer direct administrative control over single-tenant hardware they alone manage. The decision rule is narrow: default to the managed service, and reach for dedicated hardware only when a compliance requirement specifically mandates single-tenant control, since that option trades convenience for a burden of scaling and administration the customer now owns.",[22,401,403],{"id":402},"misconception-encryption-replaces-access-control","Misconception: encryption replaces access control",[27,405,406],{},"It's tempting to treat \"everything is encrypted\" as the end of the security conversation. It is not. Encryption protects data against someone who steals the storage medium or intercepts the network traffic without authorization. It does nothing to stop someone who already holds valid, authorized credentials, whether a legitimate employee or an attacker who has phished one, from reading data they're permitted to access, because the whole point of encryption is that authorized access decrypts it correctly. That is exactly the gap the previous lesson's IAM controls exist to close, and the two protections are meant to work together, not substitute for each other.",[22,408,410],{"id":409},"exam-cues-at-rest-or-in-transit","Exam cues: at rest or in transit",[48,412,413,421],{},[51,414,415],{},[54,416,417,419],{},[57,418,189],{},[57,420,192],{},[70,422,423,431,439,447],{},[54,424,425,428],{},[75,426,427],{},"\"Data written to disk,\" \"stored,\" \"a backup file\"",[75,429,430],{},"Encryption at rest",[54,432,433,436],{},[75,434,435],{},"\"Traveling over the network,\" \"between client and server,\" \"an API call\"",[75,437,438],{},"Encryption in transit",[54,440,441,444],{},[75,442,443],{},"\"Control who can use a key,\" \"authorized to decrypt\"",[75,445,446],{},"Key management, not encryption itself",[54,448,449,452],{},[75,450,451],{},"\"Single-tenant hardware,\" \"direct administrative control of the HSM\"",[75,453,454],{},"Dedicated hardware security module",[22,456,243],{"id":242},[27,458,459],{},"Encryption at rest and encryption in transit protect the same data at two different points in its journey, and a complete design needs both, since covering one leaves the other wide open. Neither one, though, decides who is allowed to ask for that data in the first place; that job stayed with identity and access management in the previous lesson. Together, the two controls answer \"who can act\" and \"what happens if a disk or a network gets compromised anyway.\" The next lesson turns to a related question: how a team proves, to an auditor or a regulator, that both controls are actually in place.",{"title":248,"searchDepth":249,"depth":249,"links":461},[462,463,464,465,466,467,468,469,470],{"id":343,"depth":252,"text":344},{"id":356,"depth":252,"text":357},{"id":366,"depth":252,"text":367},{"id":381,"depth":252,"text":382},{"id":388,"depth":252,"text":389},{"id":395,"depth":252,"text":396},{"id":402,"depth":252,"text":403},{"id":409,"depth":252,"text":410},{"id":242,"depth":252,"text":243},[472],{"slug":378,"concept":473,"style":474,"aspectRatio":475,"labels":476},"A left-to-right diagram tracing one request across four stages: Client, Network, Server, Storage. A shield icon spans the Network stage between Client and Server, labeled with TLS and captioned 'in transit.' A lock icon sits at the Storage stage, labeled with AES-256 and captioned 'at rest.' The Server stage in the middle is visually distinct, unshaded, captioned that data is briefly decrypted in memory there to be processed. A footer strip carries the takeaway that in-transit and at-rest protections cover different points in the same journey and neither substitutes for access control.","diagram","16:9",[477,478,479,480,481,482],"Client: request originates","Network: TLS encrypts data in transit between client and server","Server: data is briefly decrypted in memory to be processed","Storage: AES-256 encrypts data at rest on disk","In transit and at rest protect different points in the same journey.","Encryption protects stolen disks and intercepted traffic, not misused valid credentials.",[332,333,334,335,336],{},"/courses/cloud-computing-fundamentals/en/domains/03-security-and-reliability/01-cloud-security/03-encryption-and-data-protection",{"passingScore":268,"questions":487},[488,496,504,512,516,524,533],{"question":489,"type":272,"options":490,"correctAnswer":493,"explanation":495},"A support engineer debugging an issue captures network traffic between an app and its database over public Wi-Fi. If that traffic isn't encrypted, what has the engineer, or anyone else running the same capture, just been able to read?",[491,492,493,494],"Nothing; network traffic cannot be captured without physical access to the server","Only the destination IP address, never the data itself","Every password and every piece of data moving through that connection, in plain text","Only encrypted data, since all cloud traffic is encrypted automatically regardless of configuration","Unencrypted network traffic is readable by anyone positioned to capture it, which is exactly why encryption in transit exists. A protocol like TLS turns that same capture into unreadable ciphertext, protecting the data for the entire trip between client and server.",{"question":497,"type":272,"options":498,"correctAnswer":500,"explanation":503},"Which pair correctly matches a protection to what it defends?",[499,500,501,502],"TLS protects data at rest; AES-256 protects data in transit","AES-256 protects data at rest; TLS protects data in transit","Both TLS and AES-256 protect only data in transit","Both TLS and AES-256 protect only data at rest","AES-256 is a block cipher applied to data written to disk, protecting it if the physical storage is ever accessed without authorization. TLS operates at the network layer, encrypting data as it travels between two endpoints, so someone intercepting the connection sees only ciphertext.",{"question":505,"type":272,"options":506,"correctAnswer":508,"explanation":511},"A managed key service like AWS KMS separates who can use a key to decrypt data from who can access the key material itself. Why does this separation matter?",[507,508,509,510],"It doesn't matter; the two are the same thing in practice","It lets the provider isolate control over data access from control over the encryption keys, adding a layer of separation even the provider's own employees cannot bypass","It only matters for compliance paperwork, not actual security","It means customers never need to manage any permissions at all","Managed key services run inside hardware security modules designed so plaintext keys never leave the module, not even for the provider's own staff. Keeping key-use permissions and data-access permissions as separate, independently controlled layers means compromising one doesn't automatically hand over the other.",{"question":513,"type":272,"options":514,"correctAnswer":295,"explanation":515},"A managed key service and a dedicated hardware security module solve the same problem the same way, so the choice between them never matters.",[294,295],"A managed key service runs on shared, multi-tenant hardware behind a convenient API, which fits most workloads. A dedicated hardware security module gives a customer direct administrative control over single-tenant hardware, which specific compliance requirements sometimes mandate. Picking the dedicated option without that requirement adds operational overhead most workloads don't need.",{"question":517,"type":272,"options":518,"correctAnswer":521,"explanation":523},"A team encrypts all of its stored customer data with AES-256, then concludes it no longer needs to review who has IAM access to that data. What is wrong with this conclusion?",[519,520,521,522],"Nothing is wrong; encryption alone is always sufficient","AES-256 is not a real encryption standard","Encryption protects the data if the storage medium is stolen, but anyone with valid, authorized access decrypts it exactly as intended, so access control is still doing separate, necessary work","Encryption should be disabled entirely once access controls are in place","Encryption defends against a stolen disk or an intercepted connection. It does nothing to stop someone who holds valid credentials, whether an authorized employee or an attacker who has stolen those credentials, from reading data they're permitted to access. That is exactly what IAM and least privilege exist to control.",{"question":525,"type":315,"options":526,"correctAnswers":531,"explanation":532},"Which of the following scenarios point toward encryption in transit rather than encryption at rest? (Select all that apply.)",[527,528,529,530],"An API call carrying a password between a mobile app and a server","A nightly backup file written to a storage bucket","A request moving between a load balancer and an application server","A database file sitting untouched on disk overnight",[527,529],"Both correct scenarios describe data actively moving across a network connection, exactly what TLS protects. The backup file and the untouched database file both describe data sitting on storage media, which is what AES-256 style at-rest encryption protects instead.",{"question":534,"type":272,"options":535,"correctAnswer":539,"explanation":540},"According to current AWS guidance, what is the minimum TLS version all AWS API endpoints require as of mid-2024?",[536,537,538,539],"TLS 1.0","SSL 3.0","TLS 1.1","TLS 1.2, with all endpoints also supporting TLS 1.3","AWS requires at least TLS 1.2 for API requests and supports TLS 1.3 across all its service endpoints, reflecting the same steady tightening of minimum encryption standards seen across the industry as older protocol versions are retired for known weaknesses.",{"title":328,"description":329},"courses/cloud-computing-fundamentals/en/domains/03-security-and-reliability/01-cloud-security/03-encryption-and-data-protection","6HexOgHCohnAScCFce6j_cjODzlA7oxo-Yt6roMKwZs",{"locked":5,"reason":3,"meta":545,"item":554},{"title":546,"description":547,"isFree":265,"estimatedMinutes":9,"difficulty":548,"learningObjectives":549},"High Availability and Fault Tolerance","Why a system that recovers from a failure in under 2 minutes and a system that never blinks at all are solving the same problem with 2 different budgets, and the redundancy patterns cloud teams use to build each.","beginner",[550,551,552,553],"Define high availability and fault tolerance and explain what separates them","Explain how spreading compute and database capacity across Availability Zones removes a single point of failure","Compare active-active and active-passive redundancy using a worked failover example","Apply the high-availability-versus-fault-tolerance distinction to a scenario and identify which pattern its requirement actually calls for",{"id":555,"title":546,"body":556,"description":547,"difficulty":548,"estimatedMinutes":9,"extension":261,"infographics":806,"isFree":265,"learningObjectives":816,"meta":817,"navigation":265,"path":818,"quiz":819,"seo":874,"stem":875,"__hash__":876},"courses/courses/cloud-computing-fundamentals/en/domains/03-security-and-reliability/02-reliability-and-operations/01-high-availability-and-fault-tolerance.md",{"type":19,"value":557,"toc":795},[558,562,565,569,572,576,579,582,586,589,592,596,600,603,664,667,671,674,723,726,730,733,737,787,790,792],[22,559,561],{"id":560},"the-2am-hardware-failure","The 2am hardware failure",[27,563,564],{},"A retailer runs its checkout API on a single virtual machine. At 2am, the physical host underneath that instance fails, silently and completely, the way hardware eventually does no matter whose logo is on the rack. The instance is gone, and so is checkout, until someone notices and launches a replacement. That lone instance was a single point of failure: 1 resource whose failure alone took the whole system down with it. Removing single points of failure like it is what the rest of this lesson is about, and it turns out there are 2 different levels of \"removed,\" not 1.",[22,566,568],{"id":567},"recall-the-building-blocks-you-already-have","Recall: the building blocks you already have",[27,570,571],{},"You already have the 2 tools that make removal possible. Availability Zones give you physically separate locations to spread instances across, so 1 data center's bad night doesn't take out everything at once. A load balancer sits in front of those instances, health-checks each one, and routes traffic only to the ones still responding. Put the 2 together, instances spread across multiple AZs behind a load balancer, and a repeat of the 2am failure stops being catastrophic. What it becomes next, a brief hiccup or nothing at all, depends on how much spare capacity was already running the moment the failure hit.",[22,573,575],{"id":574},"high-availability-staying-up-through-a-brief-interruption","High availability: staying up through a brief interruption",[27,577,578],{},"Amazon RDS Multi-AZ deployments show this pattern clearly. A primary database instance handles every read and write, while a standby in a different Availability Zone stays synchronously updated in the background, ready but idle. If the primary fails, RDS detects it, promotes the standby, and repoints the database's DNS record to it, typically in 60 to 120 seconds, with 0 data loss. For those 60 to 120 seconds, though, connections to the database do drop or queue.",[27,580,581],{},"That is high availability: the system recovers automatically and quickly, but the recovery itself is a visible, if brief, gap. Most applications only need this. A minute of connection errors during a rare zone failure is a very different problem than the outright outage the single-instance retailer suffered.",[22,583,585],{"id":584},"fault-tolerance-staying-up-with-no-interruption-at-all","Fault tolerance: staying up with no interruption at all",[27,587,588],{},"Now go back to the checkout API, but redesigned. Say it needs 6 running instances to handle its normal load. Spread across 2 Availability Zones, 3 instances each, that is already highly available: lose 1 zone, and the surviving 3 instances keep checkout running, just at half capacity until new instances launch behind them. Spread across 3 Availability Zones instead, with 3 instances in each, 9 instances total, and losing any 1 zone still leaves 6 instances live, exactly the capacity checkout needs. Nothing about the user experience changes. That is fault tolerance: the system was never actually short of capacity, because the \"spare\" instances were already running and already serving traffic before the failure happened.",[27,590,591],{},"The comparison is the entire distinction in 1 image: a highly available design has enough redundancy to survive a failure, and a fault-tolerant design has enough redundancy that surviving it produces no dip to survive. Fault tolerance is closer to a self-sealing tire that keeps a car driving at full speed through a puncture than to a spare tire that gets the car moving again after a stop to change it, which is what high availability's recovery window looks like. Push the analogy further than that single point, though, and it breaks: a spare tire is cheap to carry unused, while fault-tolerant capacity bills you every hour it sits idle, waiting for a failure that may never come.",[375,593],{"alt":594,"slug":595},"A side-by-side comparison showing a highly available setup of 6 instances across 2 zones losing half its capacity when 1 zone fails, next to a fault-tolerant setup of 9 instances across 3 zones keeping its full 6-instance capacity when 1 zone fails.","high-availability-and-fault-tolerance-redundancy-capacity",[22,597,599],{"id":598},"where-redundancy-has-to-reach-every-layer-not-just-compute","Where redundancy has to reach: every layer, not just compute",[27,601,602],{},"A system is only as available as its least redundant layer. Spreading the compute tier across zones does nothing if the database, the load balancer, or DNS is still a single point of failure underneath it.",[48,604,605,618],{},[51,606,607],{},[54,608,609,612,615],{},[57,610,611],{},"Layer",[57,613,614],{},"Single point of failure",[57,616,617],{},"Redundancy pattern",[70,619,620,631,642,653],{},[54,621,622,625,628],{},[75,623,624],{},"Compute",[75,626,627],{},"1 instance",[75,629,630],{},"Multiple instances across AZs behind a load balancer",[54,632,633,636,639],{},[75,634,635],{},"Load balancer",[75,637,638],{},"1 load balancer node",[75,640,641],{},"Managed load balancers run redundantly across AZs by default",[54,643,644,647,650],{},[75,645,646],{},"Database",[75,648,649],{},"1 database instance",[75,651,652],{},"Multi-AZ deployment with automatic failover",[54,654,655,658,661],{},[75,656,657],{},"DNS",[75,659,660],{},"1 static record with no health awareness",[75,662,663],{},"Health-checked DNS routing that stops pointing at a failed target",[27,665,666],{},"Cloud providers build managed load balancers and managed DNS health checks to already be redundant, so the layers a team usually has to design for explicitly are compute and database.",[22,668,670],{"id":669},"active-active-versus-active-passive","Active-active versus active-passive",[27,672,673],{},"The 2 redundancy patterns above have names, and the difference between them shows up again later in this topic. Active-active means every replica is serving traffic at the same time, the way a load balancer spreads requests across all healthy compute instances right now, not just when something fails. Active-passive means 1 side does the work while the other stays synchronized and idle, ready to take over, the way an RDS Multi-AZ standby behaves.",[48,675,676,688],{},[51,677,678],{},[54,679,680,682,685],{},[57,681],{},[57,683,684],{},"Active-active",[57,686,687],{},"Active-passive",[70,689,690,701,712],{},[54,691,692,695,698],{},[75,693,694],{},"Who serves traffic normally",[75,696,697],{},"All replicas, simultaneously",[75,699,700],{},"1 primary only",[54,702,703,706,709],{},[75,704,705],{},"What a failure looks like",[75,707,708],{},"Remaining replicas absorb the load already",[75,710,711],{},"A failover promotes the standby",[54,713,714,717,720],{},[75,715,716],{},"Typical use",[75,718,719],{},"Load-balanced compute tiers",[75,721,722],{},"Multi-AZ managed databases",[27,724,725],{},"Neither pattern is inherently better. Compute tiers are usually active-active because splitting stateless requests across many identical instances is straightforward. Databases are more often active-passive because keeping every replica simultaneously writable raises hard consistency questions that a single active writer avoids.",[22,727,729],{"id":728},"misconception-multi-az-does-not-automatically-mean-fault-tolerant","Misconception: \"multi-AZ\" does not automatically mean \"fault-tolerant\"",[27,731,732],{},"It is tempting to hear \"deployed across multiple Availability Zones\" and assume that settles the reliability question. It settles only half of it. Multi-AZ tells you a failure in 1 zone will not take down every instance. It says nothing about whether the surviving capacity is enough to keep serving your full load without a dip. A team that spreads 6 instances across 2 zones has genuinely improved its availability over a single-AZ deployment, but it has not made itself fault-tolerant, and assuming otherwise is exactly the gap that shows up as an unplanned capacity shortage during the next zone-level event.",[22,734,736],{"id":735},"exam-cues-reading-a-high-availability-versus-fault-tolerance-question","Exam cues: reading a high-availability-versus-fault-tolerance question",[48,738,739,747],{},[51,740,741],{},[54,742,743,745],{},[57,744,189],{},[57,746,192],{},[70,748,749,757,765,773,780],{},[54,750,751,754],{},[75,752,753],{},"\"Brief interruption is acceptable,\" \"automatic recovery,\" \"minimal downtime\"",[75,755,756],{},"High availability",[54,758,759,762],{},[75,760,761],{},"\"No interruption at all,\" \"seamless,\" \"users must never notice\"",[75,763,764],{},"Fault tolerance",[54,766,767,770],{},[75,768,769],{},"\"1 instance,\" \"1 data center,\" \"no redundancy\"",[75,771,772],{},"A single point of failure to remove first",[54,774,775,778],{},[75,776,777],{},"\"Standby,\" \"failover,\" \"promoted\"",[75,779,687],{},[54,781,782,785],{},[75,783,784],{},"\"All instances serve traffic simultaneously\"",[75,786,684],{},[27,788,789],{},"The trap to watch for: a scenario that describes a solid multi-AZ setup and asks whether it is fault-tolerant. Check the capacity math, not just the zone count, before answering.",[22,791,243],{"id":242},[27,793,794],{},"Both patterns start from the same move, removing a single point of failure, and then diverge on how much spare capacity you are willing to run and pay for around the clock. High availability tolerates a short, automated recovery window; fault tolerance eliminates that window by keeping the redundant capacity already live. Most applications only need the first. The next lesson turns from staying up during a failure to a related but separate question: once you have decided how much capacity a system needs, who decides when to add more of it, and when to take it away again.",{"title":248,"searchDepth":249,"depth":249,"links":796},[797,798,799,800,801,802,803,804,805],{"id":560,"depth":252,"text":561},{"id":567,"depth":252,"text":568},{"id":574,"depth":252,"text":575},{"id":584,"depth":252,"text":585},{"id":598,"depth":252,"text":599},{"id":669,"depth":252,"text":670},{"id":728,"depth":252,"text":729},{"id":735,"depth":252,"text":736},{"id":242,"depth":252,"text":243},[807],{"slug":595,"concept":808,"style":809,"aspectRatio":475,"labels":810},"A 2-panel side-by-side comparison. Left panel titled Highly Available shows 2 Availability Zone boxes, each holding 3 instance icons, 6 total, with 1 zone grayed out as failed and a capacity bar dropping from 6 to 3. Right panel titled Fault Tolerant shows 3 Availability Zone boxes, each holding 3 instance icons, 9 total, with 1 zone grayed out as failed and a capacity bar staying flat at 6. A footer strip carries the cost takeaway.","comparison",[811,812,813,814,815],"Highly Available: 6 instances across 2 zones","1 zone fails: capacity drops to 3 until new instances launch","Fault Tolerant: 9 instances across 3 zones","1 zone fails: 6 instances keep serving traffic, no drop","Fault tolerance means paying for capacity that sits idle, just to buy zero interruption.",[550,551,552,553],{},"/courses/cloud-computing-fundamentals/en/domains/03-security-and-reliability/02-reliability-and-operations/01-high-availability-and-fault-tolerance",{"passingScore":268,"questions":820},[821,829,837,845,854,858,866],{"question":822,"type":272,"options":823,"correctAnswer":825,"explanation":828},"A retailer runs its checkout API on a single virtual machine. At 2am, the physical host underneath it fails and checkout goes down until someone notices and launches a replacement. What term describes the instance in this scenario?",[824,825,826,827],"A load balancer target","A single point of failure","A fault-tolerant resource","An Availability Zone","A single point of failure is any one resource whose failure alone takes the whole system down. The instance qualifies because nothing else was running to absorb checkout traffic when it disappeared. Removing single points of failure, not making any one resource perfectly reliable, is the actual goal of this lesson.",{"question":830,"type":272,"options":831,"correctAnswer":833,"explanation":836},"An Amazon RDS Multi-AZ database fails over from its primary to its standby in 90 seconds, with zero data loss but a brief drop in database connections during the switch. This is an example of which pattern?",[832,833,834,835],"Fault tolerance, since no data was lost","High availability, since the interruption was brief rather than absent","Elasticity, since capacity changed automatically","A single point of failure, since only 1 instance was serving traffic beforehand","High availability tolerates a brief interruption while a standby takes over. The RDS standby was not already serving traffic, so the switch itself, however fast, is a visible gap. Fault tolerance requires that spare capacity already be live and absorbing load, so a failure produces no gap at all, not just a short one.",{"question":838,"type":272,"options":839,"correctAnswer":841,"explanation":844},"A team needs 6 running instances to handle its normal checkout load. Which of the following setups is fault-tolerant against the loss of any single Availability Zone, not just highly available?",[840,841,842,843],"6 instances split across 2 Availability Zones, 3 in each","9 instances split across 3 Availability Zones, 3 in each","6 instances all placed in a single Availability Zone","6 instances split across 2 Availability Zones is already fault-tolerant, since it uses more than 1 zone","Losing 1 of 3 zones in the 9-instance setup still leaves 6 instances running, exactly the capacity the checkout load needs, so nothing about the user experience changes. The 6-instance, 2-zone setup is highly available (it survives the failure) but not fault-tolerant: losing 1 zone drops capacity to 3, a visible degradation until new instances launch.",{"question":846,"type":315,"options":847,"correctAnswers":852,"explanation":853},"Which of the following are true about fault tolerance compared to high availability? (Select all that apply.)",[848,849,850,851],"Fault tolerance requires redundant capacity that is already running and absorbing load before a failure happens","Fault tolerance always costs less than high availability, since it prevents outages entirely","High availability allows a brief, automatic recovery window that users may notice","Both patterns require removing single points of failure as a starting point",[848,850,851],"Fault tolerance costs more, not less, because it means running extra capacity around the clock that only earns its keep during a failure. High availability's defining trait is that a failure is survivable but not invisible. Neither pattern is possible without first removing the single point of failure that a lone instance or lone AZ represents.",{"question":855,"type":272,"options":856,"correctAnswer":295,"explanation":857},"A highly available architecture and a fault-tolerant architecture both always use exactly the same number of running instances.",[294,295],"A fault-tolerant architecture needs enough spare, already-running capacity that losing 1 zone still leaves full capacity in place, which typically means more total instances than a highly available setup built for the same normal load. The 6-versus-9 instance comparison in this lesson is exactly that gap.",{"question":859,"type":272,"options":860,"correctAnswer":862,"explanation":865},"In an active-passive database setup like Amazon RDS Multi-AZ, what is the standby instance doing while the primary is healthy?",[861,862,863,864],"Serving read traffic to reduce load on the primary","Nothing visible to users; it stays synchronized but does not serve read or write traffic","Running a separate, unrelated workload to avoid wasting capacity","Actively load-balancing writes with the primary","Active-passive means exactly 1 side is doing the work at any moment. The standby stays synchronously updated so it can take over quickly, but it sits idle from a traffic standpoint until a failover promotes it. Active-active is the pattern where multiple replicas serve traffic simultaneously, which is what a load balancer already does across your compute instances.",{"question":867,"type":272,"options":868,"correctAnswer":870,"explanation":873},"An exam scenario describes a payment-processing system that cannot show users any interruption, even a few seconds, during a single Availability Zone outage. Which pattern does the scenario call for?",[869,870,871,872],"High availability, since a short automated recovery is normally acceptable","Fault tolerance, since the requirement rules out any visible gap at all","Elasticity, since the system needs to grow with demand","A backup and restore strategy, since data loss is the main concern","The phrase \"cannot show users any interruption, even a few seconds\" is the exact keyword pattern that rules out high availability, which by definition tolerates a brief automated recovery. Only a fault-tolerant design, with spare capacity already live before the failure, meets a zero-visible-gap requirement.",{"title":546,"description":547},"courses/cloud-computing-fundamentals/en/domains/03-security-and-reliability/02-reliability-and-operations/01-high-availability-and-fault-tolerance","5Xh9o9PQt0Yepp0K4AUTkTESOZ1VsXntBg5JLaS6IlI"]