AZ900 Flashcards
What is the storage option best for unstructured Data?
Blob Storage - Azure Blob Storage is unstructured, object storage solution meaning that there are no restrictions on the kinds of data it can hold. Blobs are highly scalable and apps work with blobs in much the same way as they would work with files on a disk, such as reading and writing data. Blob Storage can manage thousands of simultaneous uploads, massive amounts of video data, constantly growing log files, and can be reached from anywhere with an internet connection.
For more information see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-data-in-azure/3-how-azure-storage-meets-your-business-storage-needs
What is Azure Cosmos DB?
Azure Cosmos DB is a globally distributed noSQL database service. As a noSQL database service, this work well with non-relational or semi-structured data. This is part of the back-end for solutions like Xbox - It supports noSQL API (like MongoDB, Cassandra, Tables, or Gremlins) that lets you build highly responsive and Always On applications to support constantly changing data.
For more info see:
https://docs.microsoft.com/en-us/azure/cosmos-db/introduction
What are the three types of data types Azure is set-up to store?
Structured or relational - Data fits neatly in tables (i.e. is structured) and the rows/columns define relationships between the data (i.e. relational); e.g. sensor or financial data
Semi-structured, NoSQL or non-relational: Data that has a schema for organization like tags or keys, but couldn’t work in a table.
Unstructured Data: Unstructured data is everything else. There’s no restrictions on file type.
For more info see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-data-in-azure/2-benefits-of-using-azure-to-store-data
What data is best stored in Azure SQL database? and what are the benefits to its use?
SQL is a clue; The Azure SQL database is a DaaS (database as a service) that stores relational (or structured) data, using the MS SQL server database engine that can leverage serverless computing for easier scalability.
Benefits:
- Cloud-native
- Completely managed by MS
- Easy data migration
For more info see:
https://azure.microsoft.com/en-us/services/sql-database/#features
When you need to store “Big data” - what Azure solution comes to mind and why?
Azure Data Lake Storage - A storage solution built specifically for big data as it integrates with Data lake analytics, a cloud-native analytic tool that dynamically sources compute ressources and uses languages commonly used in data science (like R, Python) and more uniquely, U-SQL (SQL + C#)
Alternatively, you could use a SQL data Warehouse depending on the structure of your data.
What is the cloud-native file storage solution within Azure?
Azure Files - kind of like OneDrive but Azure-centric and can be mapped to a local drive. Used for sharing common file types like .docx or pdfs
For more information see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-data-in-azure/3-how-azure-storage-meets-your-business-storage-needs
If you were building a globally-distributed messaging platform that required high-availability, what storage solution might you use?
Azure Queue - This is a service for storing large numbers of messages that can be accessed from anywhere in the world. This system can dynamically distribute load to connected servers, while offering increase availibility.
For more information see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-data-in-azure/3-how-azure-storage-meets-your-business-storage-needs
What is the cloud storage solution (commonly associated with VMs) most closely mimics local storage solutions?
Azure Disk storage - Similar to a local hard drive, Azure can deploy disk storages in a range of configurations, from managed - unmanaged, and of performance, from Solid-state drives (SSD) - traditional Hard disk drive (HDD).
For more information see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-data-in-azure/3-how-azure-storage-meets-your-business-storage-needs
What are the three tiers of file accessibility within blob storage?
Hot storage tier: optimized for storing data that is accessed frequently.
Cool storage tier: optimized for data that are infrequently accessed and stored for at least 30 days.
Archive storage tier: for data that are rarely accessed and stored for at least 180 days with flexible latency requirements.
For more information see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-data-in-azure/3-how-azure-storage-meets-your-business-storage-needs
Suppose you work at a startup with limited funding. Why might you prefer Azure data storage over an on-premises solution?
A. To ensure you run on a specific brand of hardware, which will let you form a marketing partnership with that hardware vendor.
B. The Azure pay-as-you-go billing model lets you avoid buying expensive hardware.
C. To get exact control over the location of your data store.
Answer: B
Which of the following situations would yield the most benefits from relocating an on-premises data store to Azure?
A. Unpredictable storage demand that increases and decreases multiple times throughout the year.
B. Long-term, steady growth in storage demand.
C. Consistent, unchanging storage demand.
Answer: A
A newly released mobile app using Azure data storage has just been mentioned by a celebrity on social media, seeing a huge spike in user volume. To meet the unexpected new user demand, what feature of pay-as-you-go storage will be most beneficial?
A. The ability to provision and deploy new infrastructure quickly
B. The ability to predict the service costs in advance
C. The ability to meet compliance requirements for data storage
Answer: A
When considering security using Azure products as a SaaS offering, which of the following security concerns are your resposibility? (i.e. not Microsoft’s). Pick as many options below as necessary:
A. Physical security of data centers B. The data itself C. Authentication (access management) D. The Azure platform E. VMs deployed F. Endpoints G. Accounts H. Applications
Correct answer: B, C, F and G
You own (and assume responsibility for) your data, endpoints, accounts and the authentication of access to the platform. These will always be your responsibility. B, C, F and G are correct.
The Azure platform will always be secured by MS; E is not correct
The others depend on your deployment of Azure, if using a hybrid or private model, you may have physical security concerns. If using a IAAS offering, securing applications and VMs may be a split responsibility between you and MS. In this case, A, D and H are not correct.
For more info see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-security-in-azure/2-shared-responsibility
What is “Defence in Depth”? If you were to pick a Shrek quote to best describe it, what might that be?
“I’m like an onion; I have layers” - Shrek
Defence in Depth is a security design philosophy that employs redundant layers of security where your data is ‘at the centre of the onion’.
For more info see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-security-in-azure/2-shared-responsibility
Which of the following things is not a function of Azure Security Center?
A. Provide security recommendations
B. Monitor and identify potential vulnerabilities
C. Give a list of authenticated users
D. Provide just-in-time access control for ports
E. Use machine learning to detect and block malware
F. Define a list of allowed applications
Answer = C.
The Azure security center, as part of Azure working within the CIS (Center for Internet Security) framework, it offers all the other functionality listed but doesn’t control user authentication. Note for full functionality, a Standard (as opposed to a Free) account is required.
For more information see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-security-in-azure/2a-azure-security-center
What’s the difference between Authorization and Authentication?
Authentication is the process of establishing the identity of a person or service looking to access a resource. It involves the act of challenging a party for legitimate credentials, and provides the basis for creating a security principal for identity and access control use. It establishes if they are who they say they are.
Authorization is the process of establishing what level of access an authenticated person or service has. It specifies what data they’re allowed to access and what they can do with it.
For more info see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-security-in-azure/3-identity-and-access
What are the advantages of SSO? Within Azure, where is this managed?
Single sign-on (SSO) is managed within Azure AD.
Benefits:
- Reduces load on help desk
- Simplifies user account management
- Reduces attack surface
What are the three elements used in MFA, that a user may be asked for in addition to credentials?
In Multi-factor authentication (MFA) the following may be asked for:
Something you know: like a security question
Something you possess: like an email or app confirmation
Someting you are: Like biometrics
https://docs.microsoft.com/en-us/learn/modules/intro-to-security-in-azure/3-identity-and-access
What is RBAC and how is that implemented in Azure?
Role-based access control is a security control measure where permissions are given on a perscribed hierarchy, like seniority within a corporate environment, or admin/developer/user or Contributor/Read-only. RBAC defines the capabilities, ressource access, and permissions within each group.
For more information see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-security-in-azure/3-identity-and-access
Define Identity, Principal, and Service Principle:
An identity is something that can be authenticated. Obviously, this includes users with a user name and password, but it can also include applications or other servers, which might authenticate with secret keys or certificates.
A principal is an identity acting with certain roles or claims. Usually, it is not useful to consider identity and principal separately, but think of using ‘sudo’ on a Bash prompt in Linux or on Windows using “run as Administrator.” In both those cases, you are still logged in as the same identity as before, but you’ve changed the role under which you are executing. Groups are often also considered principals because they can have rights assigned.
A service principal is an identity that is used by a service or application. And like other identities, it can be assigned roles.
What is the primary difference between symmetric and asymmetric encryption? Which does TLS use?
Both cases involve securing transfered data and include a set of keys that can either encrypt or decrypt the data. In Symmetric, both keys can encrypt and decrypt the data transfered. In asymmetric, each key can encrypt the data, but can only decrypt data that the other encrypted–This is the encryption used in Transport Layer Security.
For more info see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-security-in-azure/4-encryption
What encryption service are employed for each of the following Azure products?
- Azure Files
- Azure Data Warehouse
- VM VHDs
- Blob Storage
- SQL Databases
- encryption keys
Azure Files, Blob storage (and Azure Queue) = Azure storage service encryption when stored and decrypted when accessed
VM Data = Azure Disk Encryption uses BitLocker (PC) and dm-crypt (Linux) to secure virtual hard drives
Data Warehouse and SQL database = Transparent Data Encryption (TDE) is used for relational databases
Encryption keys = Azure Key vault
For more info see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-security-in-azure/4-encryption
Which of the following are stored within the Azure Key Vault? Select all that apply:
A. API keys B. Certificates (including SSL/TLS) C. HSM-backed secrets D. identity tokens E. Passwords F. Encryption keys G. All of the above
G. All of the above
Note. SSL/TLS = Secure Sockets Layer/ Transport Layer Security, HRM = hardware security modules
For more info see:
https://docs.microsoft.com/en-us/learn/modules/intro-to-security-in-azure/4-encryption
What are the benefits of Azure Key Vault?
- Secrets are centralized in a secure location
- Improved monitoring
- Integrates easily with Azure AD