AZ-304 is more focused on designing solutions using Azure, and AZ-305 is more focused on Azure Identity and Access Management. So I guess for me AZ-304 should be more appropriate.
Outline
- Design Identity, Governance, and Monitoring Solutions (25-30%) Design a solution for logging and monitoring
designing a log routing solution (Microsoft Documentation: Gateway Routing pattern) also, recommend an appropriate level of logging (Microsoft Documentation: LogLevel Enum) furthermore, recommend monitoring tools for a solution (Microsoft Documentation: Azure Monitor overview) Design authentication and authorization solutions
recommend a solution for securing resources with role-based access control (Microsoft Documentation: Azure role-based access control (Azure RBAC)) also, recommending an identity management solution (Microsoft Documentation: Microsoft Identity Manager 2016 news and updates) furthermore, recommend a solution for securing identities (Microsoft Documentation: Azure Identity Management and access control security best practices) Design governance
recommend an organizational and hierarchical structure for Azure resources (Microsoft Documentation: Organize your Azure resources effectively) also, recommend a solution for enforcing and auditing compliance (Microsoft Documentation: Azure Policy) Design identities and access to applications recommend solutions to allow applications to access Azure resources (Microsoft Documentation: Azure Resource Manager) also, recommends a solution that securely stores passwords and secrets (Microsoft Documentation: Azure Key Vault) furthermore, recommending a solution for integrating applications into Azure Active Directory(Azure AD) (Microsoft Documentation: Integrating Azure Active Directory with applications getting started guide) moreover, recommend a user consent solution for applications (Microsoft Documentation: Configure how end-users consent to applications) 2. Design Data Storage Solutions (25-30%) Design a data storage solution for relational data
recommend database service tier sizing (Microsoft Documentation: Azure SQL Database and Azure SQL Managed Instance service tiers) also, recommending a solution for database scalability (Microsoft Documentation: Dynamically scale database resources with minimal downtime) furthermore, recommend a solution for encrypting data at rest, data in transmission, and data in use (Microsoft Documentation: Azure encryption overview) Design data integration
recommending a solution for data integration (Microsoft Documentation: Integrate data into Microsoft Dataverse) also, recommend a solution for data analysis (Microsoft Documentation: Advanced analytics architecture) Recommend a data storage solution
recommending a solution for storing relational data (Microsoft Documentation: Understand data store models) also, recommend a solution for storing semi-structured data (Microsoft Documentation: Choose a big data storage technology in Azure) furthermore, recommends a solution for storing non-relational data (Microsoft Documentation: Non-relational data and NoSQL) Design a data storage solution for non-relational data
recommend access control solutions to data storage (Microsoft Documentation: Security recommendations for Blob storage) also, recommend a data storage solution to balance features, performance, and cost furthermore, design a data solution for protection and durability (Microsoft Documentation: Azure customer data protection) 3. Design Business Continuity Solutions (10-15%) Design a solution for backup and disaster recovery
recommend a recovery solution for Azure, hybrid, and on-premises workloads that meets recovery objectives (Recovery Time Objective [RTO], Recovery Level Objective [RLO], Recovery Point Objective [RPO]) (Microsoft Documentation: Protect and recover in cloud management) also, understand the recovery solutions for containers (Microsoft Documentation: Protection Containers – Refresh) furthermore, recommend a backup and recovery solution for computing (Microsoft Documentation: Azure Backup service) moreover, recommends a backup and recovery solution for databases (Microsoft Documentation: Back Up and Restore of SQL Server Databases) also, recommend a backup and recovery solution for unstructured data (Microsoft Documentation: Azure Storage archive, backup, and disaster recovery partners) Design for high availability
identify the availability requirements of Azure resources (Microsoft Documentation: Regions and availability zones) also, recommend a high availability solution for compute (Microsoft Documentation: Build solutions for high availability using availability zones) furthermore, recommending a high availability solution for non-relational data storage (Microsoft Documentation: Design for high availability) moreover, recommend a high availability solution for relational data storage (Microsoft Documentation: High availability for Azure SQL Database and SQL Managed Instance) 4. Design Infrastructure Solutions (25-30%) Design a compute solution
recommend a virtual machine-based compute solution (Microsoft Documentation: Windows virtual machines in Azure) also, recommending an appropriately sized compute solution based on workload requirements (Microsoft Documentation: Best practices to cost and size workloads migrated to Azure) furthermore, recommend a container-based compute solution (Microsoft Documentation: Choose an Azure compute service for your application) moreover, recommending a serverless-based compute solution (Microsoft Documentation: Serverless computing) Design an application architecture
recommend a caching solution for applications (Microsoft Documentation: Caching) also, recommend a messaging architecture (Microsoft Documentation: Asynchronous messaging options in Azure) furthermore, recommending an event-driven architecture (Microsoft Documentation: Event-driven architecture style) moreover, recommending an automated deployment solution for your applications (Microsoft Documentation: Deployment considerations for DevOps) also, recommend an application configuration management solution (Microsoft Documentation: Configuration Manager) furthermore, recommend a solution for API integration (Microsoft Documentation: API Management) Design migrations evaluate a migration solution that leverages the Cloud Adoption Framework for Azure (Microsoft Documentation: Get started with the Cloud Adoption Framework) also, assess and interpret on-premises servers, data, and applications for migration (Microsoft Documentation: Assess servers using an imported CSV file) furthermore, recommend a solution for migrating applications and virtual machines (Microsoft Documentation: Migrate on-premises machines to Azure) moreover, recommending a solution for migrating databases (Microsoft Documentation: Azure Database Migration Service) also, recommend a solution for migrating unstructured data (Microsoft Documentation: Azure Storage migration overview) Design network solutions
recommending a network architecture solution based on workload requirements (Microsoft Documentation: Review your network options) recommend a connectivity solution that connects Azure resources to the internet (Microsoft Documentation: Azure networking services overview) recommending a connectivity solution that connects Azure resources to on-premises networks (Microsoft Documentation: Connect an on-premises network to a Microsoft Azure virtual network) optimize network performance for applications (Microsoft Documentation: Performance Tuning Network Adapters) recommend a solution to optimize network security (Microsoft Documentation: Azure best practices for network security) recommend a load balancing and routing solution (Microsoft Documentation: Understand Azure load balancing)