🇬🇧 Microsoft Azure Certifications (e.g. AZ-104, AZ-900) · flashcards

Microsoft Azure Certifications (e.g. AZ-104, AZ-900) Azure Management, Governance, Pricing and Trust (AZ-900) Flashcards

51 question-and-answer cards covering Azure Management, Governance, Pricing and Trust (AZ-900) as it is examined in Microsoft Azure Certifications (e.g. AZ-104, AZ-900). 24 of them are printed below, taken from across the deck — no signup, no paywall on the preview.

51Cards in deck
24Free preview
12Syllabus topics
~167Chars per answer
FreePrice

24 sample cards from the Azure Management, Governance, Pricing and Trust (AZ-900) deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

  1. What is Azure Monitor?

    A comprehensive monitoring solution that collects, analyses and acts on telemetry (metrics and logs) from Azure, on-premises and other cloud environments to maximise availability and performance.

  2. What are the two fundamental types of data collected by Azure Monitor?

    Metrics (numerical values describing a system aspect at a point in time) and Logs (event records and trace data queried with Kusto Query Language in Log Analytics).

  3. What is Log Analytics within Azure Monitor?

    A tool used to write and run queries (using Kusto Query Language, KQL) against log data collected by Azure Monitor to analyse and visualise it.

  4. What is Application Insights?

    A feature of Azure Monitor that provides application performance management (APM) by monitoring live web applications for availability, performance, usage and failures/exceptions.

  5. What is the role of Azure Monitor alerts?

    Alerts proactively notify you (or trigger automated actions) when a defined metric threshold is crossed or a specific log/event condition occurs, using action groups to deliver notifications.

  6. What is a Service Level Agreement (SLA) in Azure?

    A formal Microsoft commitment describing the guaranteed performance and uptime (availability) standards for an Azure service, including the service credits owed if those targets are not met.

  7. How is the composite SLA of a multi-service application calculated?

    By multiplying the SLA percentages of each component in the critical path: $$\text{Composite SLA} = \text{SLA}_{1} \times \text{SLA}_{2} \times \dots \times \text{SLA}_{n}$$ which yields a lower combined availability than any single component.

  8. If a web app (99.95%) depends on a database (99.99%) in series, what is the approximate composite SLA?

    $$0.9995 \times 0.9999 \approx 0.9994 = 99.94\%$$ — lower than either individual component.

  9. How can adding redundant components in parallel affect the effective SLA?

    Running independent instances in parallel increases availability because the combined chance of all failing is the product of their failure probabilities: $$\text{SLA}_{\text{parallel}} = 1 - (1 - \text{SLA})^{n}$$ for $n$ identical instances.

  10. Do free Azure services (e.g. free-tier products) come with a financially backed SLA?

    No. Free and preview-tier Azure services generally do not include a financially backed SLA; SLAs apply to paid, generally available services.

  11. What downtime per month does an SLA of 99.9% ("three nines") roughly permit?

    About 43.2 minutes per month (and roughly 8.76 hours per year).

  12. What downtime per year does an SLA of 99.99% ("four nines") roughly permit?

    About 52.6 minutes per year (roughly 4.38 minutes per month).

  13. What is the Azure portal?

    A web-based, unified graphical console (GUI) for building, managing and monitoring Azure resources, from simple web apps to complex deployments, using a browser without command-line tools.

  14. What is Azure Cloud Shell?

    A browser-based, authenticated, interactive command-line shell hosted in Azure, available in Bash or PowerShell modes, with common Azure tools pre-installed and no local setup required.

  15. Which two shell experiences can you choose between in Azure Cloud Shell?

    Bash (Linux-style, used with the Azure CLI) and PowerShell (used with Azure PowerShell / Az module).

  16. What is the Azure CLI?

    A cross-platform command-line tool (using commands beginning with "az") for creating and managing Azure resources, scriptable in Bash and other shells on Windows, macOS and Linux.

  17. What is Azure PowerShell?

    A set of cmdlets (the Az module) for managing Azure resources directly from the PowerShell command line, available cross-platform and in Cloud Shell.

  18. When might you choose an Azure SDK over the CLI or portal?

    When you need to manage or integrate Azure resources programmatically from within application code, using a preferred language such as .NET, Python, Java, JavaScript or Go.

  19. What is Infrastructure as Code (IaC)?

    The practice of defining and provisioning infrastructure through machine-readable definition/configuration files rather than manual processes, enabling consistent, repeatable and version-controlled deployments.

  20. What is an Azure Resource Manager (ARM) template?

    A JSON file that declaratively defines the infrastructure and configuration for an Azure deployment, enabling repeatable, idempotent deployment of resources as a single coordinated operation.

  21. What is Bicep and how does it relate to ARM templates?

    Bicep is a domain-specific declarative language that offers simpler, more concise syntax than JSON ARM templates; Bicep files transpile down to ARM templates for deployment.

  22. What does it mean that ARM/Bicep deployments are declarative and idempotent?

    Declarative: you state the desired end state, not the steps to get there. Idempotent: deploying the same template repeatedly produces the same result without creating duplicates or unintended changes.

  23. How does Infrastructure as Code differ from manually deploying resources via the Azure portal?

    IaC uses version-controlled definition files for automated, consistent, repeatable deployments at scale, reducing human error and configuration drift, whereas portal deployment is manual, slower and harder to reproduce exactly.

  24. Which Azure governance tool would you use to automatically ensure all resources are deployed only to approved regions?

    Azure Policy — you assign a policy (e.g. "Allowed locations") that denies the creation of resources in any region outside the approved list.

What this deck covers

The Azure Management, Governance, Pricing and Trust (AZ-900) deck follows the Microsoft Azure Certifications (e.g. AZ-104, AZ-900) Azure Management, Governance, Pricing and Trust (AZ-900) syllabus — 4 chapters and 12 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 12.8 cards per chapter.

Answers are written to be recallable, not just readable — averaging about 167 characters, which is long enough to carry the reasoning and short enough to say out loud.

A deck like this earns its keep on the second and third pass. Read the syllabus first so you know the shape of the subject, then use the cards to find the specific facts that have not stuck.

Azure Management, Governance, Pricing and Trust (AZ-900) flashcards FAQ

How many Azure Management, Governance, Pricing and Trust (AZ-900) flashcards are in this Microsoft Azure Certifications (e.g. AZ-104, AZ-900) deck?

51 cards. This page previews 24 of them, sampled evenly across the deck so you can judge the difficulty before installing anything.

Are these Microsoft Azure Certifications (e.g. AZ-104, AZ-900) flashcards free?

Yes. The preview here is free to read with no signup, and the full 51-card deck is free inside the Examius app.

What do the Azure Management, Governance, Pricing and Trust (AZ-900) cards cover?

They follow the Microsoft Azure Certifications (e.g. AZ-104, AZ-900) Azure Management, Governance, Pricing and Trust (AZ-900) syllabus — 4 chapters and 12 topics — so the questions track what is actually examinable.

How should I use these flashcards?

Read the syllabus first so you know the shape of the subject, then drill the deck. Examius schedules each card with spaced repetition, so cards you keep missing come back sooner and ones you know drift further apart.