[{"id":"microsoftaz900-101","courseId":"microsoft-az-900","domain":"cloud-concepts","topic":"Shared responsibility","prompt":"Which TWO responsibilities always remain with the customer, whether the workload is on-premises, IaaS, PaaS or SaaS? Choose TWO.","hint":"Consider what a provider can never decide on your behalf.","explain":"Shared responsibility divides duties by layer. Moving from on-premises to SaaS hands more layers to the provider, beginning with physical facilities. Ask which duties depend on the organization's own choices.","source":"https://learn.microsoft.com/en-us/azure/security/fundamentals/shared-responsibility","interaction":{"type":"multiple","tellCount":true},"options":[{"id":"a","text":"Managing user accounts and identities","why":"Accounts and identities stay with the customer in on-premises, IaaS, PaaS and SaaS, even though the provider may run the sign-in platform."},{"id":"b","text":"Maintaining the physical hosts","whyNot":"Physical hosts are managed by Microsoft in IaaS, PaaS and SaaS; only in an on-premises datacenter does the customer own them."},{"id":"c","text":"Protecting the organization's data","why":"Microsoft's responsibility matrix lists customer data as the customer's duty in every deployment type, including classification and protection decisions."},{"id":"d","text":"Securing the datacenter building","whyNot":"Physical datacenter security belongs to Microsoft once workloads move to the cloud, so it is not retained in every deployment type."}],"answer":"ac","explanation":"Customers always retain responsibility for their data, endpoints, accounts and access management, regardless of the service type.","concept":"Customers always retain responsibility for their data, endpoints, accounts and access management, regardless of the service type.","rev":1,"kind":"scenario","takeaways":["Data, endpoints, accounts and access management are always the customer's job, in every service type."]},{"id":"microsoftaz900-102","courseId":"microsoft-az-900","domain":"cloud-concepts","topic":"Shared responsibility","prompt":"A company adopts a SaaS email service from a vendor. Which task is still the company's responsibility?","hint":"Even fully managed software needs someone to decide who may sign in.","explain":"Responsibility shrinks as the stack passes to the provider, and SaaS hands over the most layers. Consider which tasks depend on knowing the company's own staff rather than the software's internals.","source":"https://learn.microsoft.com/en-us/azure/security/fundamentals/shared-responsibility","interaction":{"type":"single"},"options":[{"id":"a","text":"Updating the email application code","whyNot":"The vendor maintains and updates the SaaS application itself; customers only configure it and manage their own data and access."},{"id":"b","text":"Replacing failed physical disks in the datacenter","whyNot":"Hardware maintenance, including disk replacement, is handled by the provider in every cloud service type."},{"id":"c","text":"Deciding which employees have accounts and what they can access","why":"In SaaS the customer still manages identities, users and access settings, while the vendor runs the application and infrastructure."},{"id":"d","text":"Patching the server operating system","whyNot":"In SaaS the operating system is managed by the provider, so the company does not patch the servers behind the email service."}],"answer":"c","explanation":"In SaaS, the provider runs the application and infrastructure, while the customer manages data, users and access.","concept":"In SaaS, the provider runs the application and infrastructure, while the customer manages data, users and access.","rev":1,"kind":"scenario","takeaways":["SaaS: provider runs app and infrastructure; you still own your data, users and access."]},{"id":"microsoftaz900-103","courseId":"microsoft-az-900","domain":"cloud-concepts","topic":"Manageability","prompt":"Which TWO are examples of management of the cloud, where the cloud handles resource management for you? Choose TWO.","hint":"Look for automated capabilities rather than tools that people use.","explain":"Cloud management covers both interfaces people use and built-in capabilities that reduce manual work. Ask whether each option describes a person doing the work or a built-in capability reducing it.","source":"https://learn.microsoft.com/en-us/training/modules/describe-benefits-use-cloud-services/5-manageability-cloud","interaction":{"type":"multiple","tellCount":true},"options":[{"id":"a","text":"Automatically scaling resource deployment based on need","why":"Autoscaling adjusts resources automatically without manual intervention."},{"id":"b","text":"Deploying resources from a preconfigured template","why":"Templates remove manual configuration and are listed as management of the cloud."},{"id":"c","text":"Administering resources through a command line interface","whyNot":"This is management in the cloud, which concerns the tools used to manage."},{"id":"d","text":"Administering resources through a web portal","whyNot":"The portal is a management interface, an example of management in the cloud."}],"answer":"ab","explanation":"Management of the cloud includes autoscale, templates, health monitoring and alerts.","concept":"Management of the cloud includes autoscale, templates, health monitoring and alerts.","rev":1,"kind":"scenario","takeaways":["Cloud manageability means autoscale, template deployment, health monitoring and alerts."]},{"id":"microsoftaz900-104","courseId":"microsoft-az-900","domain":"cloud-concepts","topic":"Shared responsibility","prompt":"A team hosts its data in Azure SQL Database. Which activity does Microsoft perform for them?","hint":"A managed database service removes work at the layer beneath the data.","explain":"Services differ in how much of the stack the provider operates, from raw infrastructure to managed platforms. Consider which options fall beneath the data, and which concern the data or its users.","source":"https://learn.microsoft.com/en-us/azure/security/fundamentals/shared-responsibility","interaction":{"type":"single"},"options":[{"id":"a","text":"Classifying the data stored in the database","whyNot":"Data classification and protection decisions are customer duties regardless of who runs the database engine."},{"id":"b","text":"Patching the operating system that hosts the database engine","why":"Azure SQL Database is PaaS, and the matrix lists the operating system as a Microsoft responsibility in PaaS."},{"id":"c","text":"Deciding which people are allowed to query the data","whyNot":"Access decisions and identities remain with the customer in every service type, including PaaS."},{"id":"d","text":"Securing the laptops that employees use to connect","whyNot":"Client devices and endpoints remain the customer's responsibility in PaaS, so Microsoft does not secure them."}],"answer":"b","explanation":"In PaaS, Microsoft manages the operating system and platform while the customer is responsible for data, identities and access.","concept":"In PaaS, Microsoft manages the operating system and platform while the customer is responsible for data, identities and access.","rev":1,"kind":"scenario","takeaways":["PaaS: Microsoft handles OS and platform; you handle data, identities and access."]},{"id":"microsoftaz900-105","courseId":"microsoft-az-900","domain":"cloud-concepts","topic":"Cloud computing","prompt":"A retailer expects a spike in traffic for a seasonal launch in six weeks. Ordering and installing extra physical servers would take longer than that. Which cloud characteristic best solves this problem?","hint":"Think about how quickly capacity can appear without building anything.","explain":"Peak capacity can come from hardware bought ahead of time, or from services provisioned when needed. Compare each route's lead time with the deadline, and what happens to the capacity afterward.","source":"https://learn.microsoft.com/en-us/training/modules/describe-cloud-compute/3-what-cloud-compute","interaction":{"type":"single"},"options":[{"id":"a","text":"Resources can be provisioned on demand and released afterward, without building new datacenter capacity","why":"Cloud services let teams expand their IT footprint rapidly and scale back later, so the launch does not wait on hardware procurement."},{"id":"b","text":"Relying on the existing servers and accepting slower response times","whyNot":"Accepting degraded performance avoids cost but fails the stated goal of handling the launch traffic, which on-demand cloud capacity is designed to address."},{"id":"c","text":"Moving all workloads to a private cloud hosted in the retailer's own datacenter","whyNot":"A private cloud in the retailer's own datacenter still relies on purchasing and installing hardware, so it would not meet a six-week deadline."},{"id":"d","text":"Requiring a long-term capacity contract signed a year in advance","whyNot":"Annual capacity commitments are a traditional planning approach, not an on-demand cloud benefit, and they would not help with a short seasonal spike."}],"answer":"a","explanation":"Because cloud capacity is delivered over the internet, organizations can add resources quickly for peaks and remove them afterward instead of waiting on hardware procurement.","concept":"Because cloud capacity is delivered over the internet, organizations can add resources quickly for peaks and remove them afterward instead of waiting on hardware procurement.","rev":1,"kind":"scenario","takeaways":["Elasticity: add capacity for peaks and release it later, with no hardware procurement wait."]}]