Exam Tips: Designing Microsoft Azure Infrastructure Solutions (AZ-305)

https://www.linkedin.com/learning/exam-tips-designing-microsoft-azure-infrastructure-solutions-az-305

by Nicole Stevens

Introduction

  1. Why the AZ-305 exam?
  2. What you need to know
    • you should take az 104 first

I. Design Identity, Governance, and Solutions
  1. Design a solution for logging and monitoring
  2. Design authentication and authorization solutions
    • the three identity based solutions in azure:
      • Active Directory Domain Services (AD DS)
        • You can extend an on premises domain by replicating a domain controller to a VM running on Azure, or have Azure VMs domain join to on premises domain controllers using a VPN or express route
      • Azure Active Directory Domain Services (Azure AD DS)
      • Azure Active Directory (Azure AD)
    • you need to know how to configure conditional access for the exam
  3. Design identities and access for applications
    • managed identity use case
    • two types of managed identity: system assigned and user assigned
    • know how to perform app registration in azure ad
      • request uri is blank for an api but is required for an application
  4. Design governance
    • organize subscription by billing department
    • overview of an azure policy json
2. Design Data Storage Solutions
  1. Recommend a data storage solution
    • when to use relation dbs
    • store semi structured data in key value stores
    • shows a flowchart that assists in picking  a data store
  2. Design a data storage solution for relational data
    • azure sql is the recommended solution for relation data
      • three versions: Azure SQL VM, Azure SQL MI, Azure SQL DB
  3. Design a data storage solution for nonrelational data
    • Azure Blob Storage and Data Lake Gen2
    • shows hot enable data lake storage when creating an azure blob
  4. Design data integration
    • azure data factory
      • ETL solution
    • azure databricks
      • for ML workflows and analytics
3. Design Business Continuity Solutions
  1. Design a solution for backup and disaster recovery
    • Recovery time objective (RTO)
      • Acceptable time to recover any system to its state prior to the disaster
    • Recovery point objective (RPO)
      • Acceptable maximum period of data loss once restored to recovery point
    • Recovery level objective (RLO)
      • Acceptable level of system service before considered operational
    • what is BCDR for AKS?
    • know recovery options for sql server
  2. CD Design for high availability
    • Always On availability group (AG)
      • - Failover at the database level
    • Always On failover cluster instance (FCI)
      • - Failover at the instance level
      • - DBs available once recovery complete; generally longer recovery time
    • Windows Server failover cluster (service for AG and FCI)
      • - Quorum, single or multiple subnet configuration (DNN/VNN)
      • - DNN - multiple subnets, no LB, reduced failover latency, specific SQL/Server versions
    • Standard availability model
      • - Separation of compute and storage
      • - Service tiers - Basic (DTU), Standard (DTU), General Purpose (vCore)
      • - Availability zone support - General Purpose tier only (not Azure SQL MI)
    • Premium availability model
      • - Cluster of database engines, quorum; similar to Always On availability groups
      • - Service tiers - Premium (DTU), Business Critical (vCore)
      • - Availability zone support for both tiers (not Azure SQL MI)
4. Design Infrastructure Solutions
  1. Design a compute solution: VM-based compute and serverless
    • azure batch discussion
    • azure functions vs azure logic app
  2. Design a compute solution: WebApps and containers
    • discussion of app service plan
    • know how a webapp can scale out
    • discussion of service fabric and aks
  3. Design an application architecture
    • event hub vs event grid
    • discussion of api management service
  4. Design migrations
    • discussion of the Cloud Adoption Framework
    • discussion of database migration
    • discussion of migrating data to the cloud
  5. Design network solutions
    • you can peer vnets from different subscriptions 
    • what is a virtual network link?
    • what is a conditional forwarder?
  6. Design network solutions: Routing and load balancing
    • discusses the different load balancing options in Azure
Conclusion
  1. Next steps and study resources



Comments

Popular posts from this blog

Angular Routing and Navigation Playbook

Working with Files in C# 10

Mastering Git