Developing Microsoft Azure Solutions Free Sample Questions

Azure Active Directory (AD) B2C is a customer identity and access management (CIAM) solution designed for consumer-facing applications. It allows users to sign up and sign in using social accounts or local accounts and provides customizable user flows for these processes. Azure AD B2B is for partner collaboration, standard Azure AD is for organizational identities, and AD Domain Services is for managed domain services for VMs.

Append Blobs are optimized for append operations, making them ideal for logging and telemetry scenarios where data is continuously added to the end of a file. Block Blobs are for general-purpose storage of discrete objects, and Page Blobs are designed for random read/write access, such as virtual hard disk files.

Azure File Storage (Azure Files) provides fully managed file shares in the cloud that are accessible via the industry-standard Server Message Block (SMB) protocol. This allows multiple Azure VMs to mount and access the same file share concurrently, providing a shared file system without the need for a dedicated file server.

Azure Functions is a serverless compute service designed for running small pieces of code in response to events (triggers). It has built-in triggers for services like Azure Storage Queues, abstracting away the infrastructure and allowing developers to focus solely on the business logic. WebJobs are a valid alternative but typically involve more setup within an App Service Plan, while VMs and Web Apps are overkill for this simple, event-driven task.

In the context of Azure App Service Plans and Virtual Machine Availability Sets, a Fault Domain is a group of virtual machines that share a common power source and network switch. When you deploy multiple instances, the Azure platform automatically distributes them across different Fault Domains to mitigate the risk of a localized hardware failure (e.g., a rack failure) taking down all instances. Update Domains relate to planned maintenance, and Availability Zones provide datacenter-level redundancy, which is a broader concept.

The goal of a custom retry policy is to define the conditions under which it should retry. The method should return true to retry and false to fail. The requirement is to retry ONLY on a 409 Conflict. Therefore, if the status code is anything OTHER than Conflict, the method should return false to stop the retry loop.

Azure Service Bus Topics and Subscriptions are designed for the publish/subscribe (pub/sub) pattern. The front-end publishes a single message to a topic. Multiple back-end services each listen on their own subscription to that topic, and each subscription receives a copy of the message. This allows for one-to-many message distribution. Service Bus Queues are for one-to-one delivery, and Event Hubs are for high-throughput event streaming, not individual message processing by distinct consumers.

NSGs have default rules. One default rule allows all traffic from the 'VirtualNetwork' source. Another default rule with a high priority number (65500) denies all inbound traffic from the 'Internet'. To meet the requirements, you only need to add one new inbound rule with a lower priority number (e.g., 100) that allows traffic on port 443 from the 'Internet' source. This rule will be processed before the default deny rule, allowing HTTPS traffic while the default rules correctly handle VNet traffic and deny all other internet traffic.

A Shared Access Signature (SAS) provides delegated access to resources in a storage account. It allows for granular control over permissions (read, write, delete), expiry time, and the specific resource (e.g., a single blob). This is the standard and secure way to grant temporary, limited access without exposing the account keys.

The best practice for multi-tier applications is to place the VMs for each tier into their own separate Availability Set. An Availability Set distributes VMs across Update Domains and Fault Domains. By using separate sets, you ensure that planned maintenance (which targets one Update Domain at a time) will only affect a subset of VMs within a single tier, not across different tiers simultaneously. This maintains the availability of the entire application.