Assessments

Chapter 1: Azure App Service

1. Yes, App Service and Web App can be used interchangeably.
2. Currently, we have three categories: Dev/Test, Production, and Isolated.
3. Both the Free and Shared tiers will be blocked after exceeding the computer limit, making the application unavailable for users.
4. Currently, we have five different providers: Azure AD, Facebook, Google, Twitter, and Microsoft Account.
5. Yes, Premium tiers are based on new Dv2 machines, which use more powerful CPUs and newer architecture.
6. You have to enable the Application logging feature.
7. Unfortunately, you cannot do it; you need at least the Shared tier.
8. Yes, you can. App Service Plan can support more than only one App Service.
9. There are three OSes available: Window, Linux, and Docker.
10. No, you cannot—you have to recreate App Service to change the underlying operating system.
11. Where can you find the proper location...

Chapter 2: Azure WebJobs

1. Yes, it is possible to run WebJobs using the Free or Shared tier. However, it is not recommended as some jobs require that the Always On feature is enabled, which is not possible for the Free and Shared tiers.
2. We can run a job either continuously or by triggering it manually/on schedule.
3. Yes, you can. In general, WebJobs supports the same programming languages as App Services.
4. You have can we deploy the run.{extension} file.
5. If so, how to do that? Yes, you can; it is needed to archive all files as a ZIP package and deploy it.
6. It has to be created as a single instance.
7. Yes, WebJobs share application settings with App Services, which host them.

Chapter 3: Deploying Web Applications as Containers

1. Azure Container Registry is an Azure service, which acts as a Docker private registry that's hosted in the cloud. It is seamlessly integrated with other Azure container services.
2. Admin login is a feature that allows you to authenticate in ACR using the registry name as a username and a key as a password.
3. To run containers in App Service, you have to choose Docker as the OS.
4. Yes, you can—in fact, there are both possibilities (public/private) available.
5. Yes, you can—there is a specific blade available for scaling your instance.
6. To update an application in AKS cluster and limit downtime, you have to have multiple pods deployed with the same application.
7. You have to create a service principal, which will be used during authentication.

Chapter 4: Distributed Applications and Microservices with Service Fabric

1. Reliable Actors implement the Virtual Actor pattern and are designed to distribute load among thousands of stateful services. Reliable Services are the patterns in Service Fabric that are used to implement stateful services, which can be multi-threaded and do not have to be scaled to that level.
2. Stateful services store the state locally. Stateless services either do not handle the state at all or use an external storage.
3. An interface called ICommunicationListener.
4. A node type in SF is the specialized VM scale set that's designed to work on a particular workload.
5. Yes, as they are separate VMSS.
6. Yes, you can.
7. Node-to-node security and client-to-node security.
8. A cluster is the whole instance of Service Fabric—a container for all of the other concepts. An application is a logical container for multiple...

Chapter 5: Using Azure Search

1. An index is a metadata table with documents that are used by Azure Search.
2. The push model is used in applications with low-latency requirements, where your documents are indexed immediately once pushed to the service.
3. Yes, you can define a custom schedule for an indexer.
4. By default, Azure Search uses the Lucene analyzer.
5. Yes, it is possible to use a custom analyzer.
6. A replica is a physical instance of your service hosting an index while the partition is a part of it provisioning particular resources.
7. You have to use the api-key header.

Chapter 6: Mobile Notifications with Notification Hub

1. PNS stands for Push Notification Service.
2. Yes, each vendor has its own PNS.
3. The main difference is the patch capability—an installation can be updated after creation, a registration cannot.
4. No, the amount of available devices is different per tier.
5. Depending on your environment, either use Visual Studio or programmatically query the Notification Hub instance.
6. There are many possibilities: either use Azure Portal or Visual Studio or enable Test send and send a notification programmatically.
7. Rich content notifications are notifications that contain more than only text (such as an image, for example).

Chapter 7: Serverless and Azure Functions

1. In the Consumption pricing model, you pay for each execution of your functions individually.
2. GB-s is the unit of consumption on Azure Functions; it is gigabytes-per-second and defines how much memory was used in a unit of time.
3. Yes, you can, however it is not the advised model of services.
4. It is called a Function App.
5. There was experimental support for this language in the V1 version of Azure Functions. Currently (in V2), it is not supported.
6. Yes—this is how Azure Storage bindings work.
7. When your Function App is deployed automatically, it is set as read-only to avoid manual changes within the process.
8. Not really—in Azure Function, all settings are available via environmental variables.

Chapter 8: Integrating Different Components with Logic Apps

1. Azure Logic Apps leverage the serverless pricing model where you pay for each execution individually, considering all blocks used for this particular app.
2. Yes, it is possible.
3. You need an extra extension called Azure Logic Apps for Visual Studio.
4. Once the execution is finished, you can access it and see the evaluated values that are used during the execution of the flow.
5. Yes, there is a special connector to work with these services.
6. Azure Logic Apps can be exported to JSON files and stored inside your version control system.

Chapter 9: Swiss Army Knife – CosmosDB

1. Azure Cosmos DB supports SQL, MongoDB, Cassandra, Azure Table, and Gremlin.
2. Yes—in the Azure Cosmos DB Table API, you have almost infinite scaling capabilities, a failover feature, and better performance.
3. Strict, bounded-staleness, session, consistent-prefix, and eventual.
4. Out of those two, bounded staleness is more strict.
5. Yes, by configuring the firewall rules.
6. No, SQL API for Azure Cosmos DB is quite different from the SQL Server.
7. Stored procedures in Azure Cosmos DB are for performing extra logic during your queries.
8. Yes, it is possible.

Chapter 10: Reactive Architecture with Event Grid

1. Currently, it is possible to use either the Event Grid schema or the Cloud Events schema.
2. You have to use either the aeg-sas-key or aeg-sas-token header.
3. You have to respond with a correct JSON containing validation code.

4. An endpoint does not have to be validated if it is an Azure service.
5. When an event cannot be delivered, the delivery will be retried after a predefined interval.
6. During a subscription creation, you can define filters using the Subject field.
7. The Local Azure Functions runtime implements the Event Grid endpoint, which can be used to test your application.

Chapter 11: Using Azure Storage – Tables, Queues, Files, and Blobs

1. Hot and cold—the archive can be selected on a blob level once the account is created.
2. You must include both a Partition Key and a Row Key.
3. The following models are available: LRS, ZRS, GRS, and RA-GRS.
4. File Storage works more like a file share while Blob Storage acts as storage for application and user data. They also have different pricing models.
5. Yes, you can.
6. A message will be available for up to a maximum of 7 days.
7. The maximum size of a message is 64 KBs.
8. The maximum size of the Partition Key is 1 KB.
9. In Table Storage, we work with the optimistic concurrency model.
10. With Azure Files, you can easily scale out your shares by adding additional accounts. When using on-premises shares, you have to buy, install, and configure the hardware before you use it.

...

Chapter 12: Big Data Pipeline – Azure Event Hub

1. Consumer groups are used to allow for parallel events processing using a different processor, which are unrelated to each other.
2. 1TU allows you to process 1,000 messages per second.
3. It depends on your requirements—the only thing to remember is the fact that you cannot change the number of partitions once the hub is created.
4. TUs are assigned to a namespace and shared by hubs.

5. Send, Listen, and Manage.
6. Yes, it can.
7. Some consumers may lose the lease and become idle.

Chapter 13: Real-Time Data Analysis – Azure Stream Analytics

1. In Azure Stream Analytics, you pay for the Streaming Units (SUs).
2. Stream input lets you digest data directly from a stream. With reference input, you can select a service such as Azure Storage, which will be digested in intervals.
3. Application time is the time when an event was generated. Arrival time tells you when an event was received by the service.
4. SELECT Id INTO [output-alias] FROM [input-alias].
5. Yes, it is possible to work with multiple input values.
6. An event is out of order if you apply event ordering based on the arrival time, which will perturb the actual order of events.
7. Yes, you can—to do so, you have to use the SUBSTRING function.

Chapter 14: Enterprise Integration – Azure Service Bus

1. In queue, once a message is read, it will not be sent to another reader. A topic allows you to implement multiple readers that are focused on the same set of messages.
2. No, you have to use at least the Standard tier to use topics.
3. Dead letter queue is used to avoid blocking your queue by an invalid message.
4. In Azure Service Bus, sessions are used to ensure the FIFO message processing.
5. The maximum size of a queue with partitioning is 80 GBs.
6. In the active replication, you are sending a message to both namespaces. In the passive model, you send a message to the secondary namespace, but only if it can be delivered to the primary one.
7. You have to define the primary and secondary regions, pair them, and define a trigger for failover.

Chapter 15: Using Application Insights to Monitor Your Applications

1. You need an instrumentation key.
2. Yes—Azure Application Insights can be used with a variety of different programming languages.
3. Smart Analytics is a set of functionalities that incorporate machine learning and data analysis to extend the capabilities of Application Insights.
4. You can use the Analytics module to perform queries against collected logs.
5. You can use ARM template to create alerts during a resource provisioning.
6. Yes, this is one of the available options.

Chapter 16: SQL in Azure – Azure SQL

1. Azure SQL is constantly updated and gets the updates faster than Microsoft SQL Server.
2. Sharding is dividing your data and database into smaller chunks, which can be distributed evenly, and handle only their part of the load.
3. By default, the connection is blocked by the firewall—you have to add your IP address to the whitelist.
4. DTU-based and vCore-based.
5. The elastic pool is a model of scaling where instead of having a single database with provisioned throughput, you have a pool, which you can dynamically assign to a set of databases.
6. eDTU is the elastic-DTU that is used with elastic pools.
7. You can use the feature called Dynamic Data Masking.
8. You have three option available: Azure Storage, Azure Log Analytics, and Azure Event Hub.

Chapter 17: Big Data Storage – Azure Data Lake

1. In general, it is easier to manage security groups—in that case, you do not have to add an individual entity each time a new user is granted access.
2. RBAC is based on roles, while POSIX ACL is based on computing the set of permissions based on the actions assigned to a user or a group.
3. There are no file size limits in ADLS.
4. It depends on your requirements—while the particular structure may not affect the performance, file sizes may.
5. Yes, ADLS will work with any language that is able to connect to it.
6. Azure Storage introduces file size limits and capacity limits. It also offers a much simpler security model than Azure Data Lake Storage.
7. You have to implement replication to a secondary region.

Chapter 18: Scaling Azure Applications

1. Scaling out scales your application horizontally (by adding additional instances), while scaling up scales your application vertically (so better hardware is provisioned).
2. In most cases, you scale out rather than scale up. This is because the performance of the hardware is limited and it is easier to add another machine to the set rather than provision a new CPU and memory.
3. Not really—while conceptually it could be possible, serverless services avoid scaling up.
4. Yes—if you scale out Azure App Service, the price for the service will be multiplied by the number of instances currently working.
5. In SF, scaling out is perfectly fine. The dangerous operations are scaling up as it requires you to take your workload from one place and migrate it to another one.
6. Manual scaling can be problematic when the traffic your application handles...

Chapter 19: Serving Static Content Using Azure CDN

1. Azure CDN is designed to cache to improve the performance of your application while serving static content to multiple users.
2. Currently, Azure CDN supports Verizon, Akamai, and Microsoft.
3. Origin is an endpoint that caches resources.
4. In Azure CDN, the compression feature allows you to compress files on the fly, reducing their size and network latencies.
5. The default TTL for files is set to seven days.

Chapter 20: Distributing Load with Azure Traffic Manager

1. Supported routing methods are Performance, Weighted, Geographic, MultiValue, and Subnet.
2. To use the real user measurement feature, you have to inject a custom script into your website, which will send the updated values for latencies regarding network calls.
3. Of course—in that scenario, you will get a nested profile.
4. Yes, it is possible to use an external endpoint.
5. Once the DNS name is resolved (so that Azure Traffic Manager is pointed to the correct endpoint), a client connects directly with the endpoint.
6. Azure Traffic Manager works on the DNS level, while the gateway is a pattern that enables you to load balance requests, but acts as a single entry to your system.
7. Yes, you can use Azure Traffic Manager to achieve HA—in that scenario, you have to implement a profile, which enables you to failover to other...

Chapter 21: Tips and Tricks for Azure

1. The Subscription level locks and Resource level locks are available.
2. Of course—Azure CLI is available inside Cloud Shell as part of the service.
3. To get the detailed information, you can access the Resource Explorer application.
4. In general: better resources management, quicker filtering, and easier development.
5. It uses a storage account to persist files between different sessions.