Download Designing Microsoft Azure Infrastructure Solutions.AZ-305.VCEplus.2021-12-17.59q.vcex

Scenario: App1 has the following data requirements:Each instance will write data to a data store in the same availability zone as the instance. Data written by any App1 instance must be visible to all App1 instances. Azure Cosmos DB: Each partition across all the regions is replicated. Each region contains all the data partitions of an Azure Cosmos container and can serve reads as well as serve writes when multiregion writes is enabled.Incorrect Answers:B, D: GZRS protects against failures. Geo-redundant storage (with GRS or GZRS) replicates your data to another physical location in the secondary region to protect against regional outages. However, that data is available to be read only if the customer or Microsoft initiates a failover from the primary to secondary region. C: Active geo-replication is designed as a business continuity solution that lets you perform quick disaster recovery of individual databases in case of a regional disaster or a large scale outage. Once georeplication is set up, you can initiate a geo-failover to a geo-secondary in a different Azure region. The geo-failover is initiated programmatically by the application or manually by the user. Reference:https://docs.microsoft.com/en-us/azure/cosmos-db/high-availability

Box 1: Azure FilesScenario: App2 has the following file storage requirements:   Save files to an Azure Storage account. Replicate files to an on-premises location. Ensure that on-premises clients can read the files over the LAN by using the SMB protocol. Box 2: Azure File SyncUse Azure File Sync to centralize your organization's file shares in Azure Files, while keeping the flexibility, performance, and compatibility of an on-premises file server. Azure File Sync transforms Windows Server into a quick cache of your Azure file share. You can use any protocol that's available on Windows Server to access your data locally, including SMB, NFS, and FTPS. You can have as many caches as you need across the world. Reference: https://docs.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide  

Directory synchronization between Azure Active Directory (Azure AD) and corp.fabrikam.com must not be affected by a link failure between Azure and the on-premises network. (This requires domain controllers in Azure). Users on the on-premises network must be able to authenticate to corp.fabrikam.com if an Internet link fails. (This requires domain controllers on-premises).

  

Private Endpoint securely connect to storage accounts from on-premises networks that connect to the VNet using VPN or ExpressRoutes with private-peering. Private Endpoint also secure your storage account by configuring the storage firewall to block all connections on the public endpoint for the storage service. Incorrect Answers:A: Microsoft peering provides access to Azure public services via public endpoints with public IP addresses, which should not be allowed.B: Azure public peering has been deprecated.C: By default, Service Endpoints are enabled on subnets configured in Azure virtual networks. Endpoints can't be used for traffic from your premises to Azure services.Reference: https://docs.microsoft.com/en-us/azure/expressroute/expressroute-circuit-peerings

Scenario: The Network Contributor built-in RBAC role must be used to grant permissions to the network administrators for all the virtual networks in all the Azure subscriptions. RBAC roles must be applied at the highest level possible.

Box 1: Standard general-purpose v2     Standard general-purpose v2 supports Blob Storage. Azure Storage provides data protection for Blob Storage and Azure Data Lake Storage Gen2. Scenario:Litware identifies the following security and compliance requirements:Once App1 is migrated to Azure, you must ensure that new data can be written to the app, and the modification of new and existing data is prevented for a period of three years. On-premises users and services must be able to access the Azure Storage account that will host the data in App1. Access to the public endpoint of the Azure Storage account that will host the App1 data must be prevented. All Azure SQL databases in the production environment must have Transparent Data Encryption (TDE) enabled. App1 must NOT share physical hardware with other workloads. Box 2: NFSv3Scenario: Plan: Migrate App1 to Azure virtual machines.Blob storage now supports the Network File System (NFS) 3.0 protocol. This support provides Linux file system compatibility at object storage scale and prices and enables Linux clients to mount a container in Blob storage from an Azure Virtual Machine (VM) or a computer on-premises. Reference: https://docs.microsoft.com/en-us/azure/storage/blobs/data-protection-overview

Scenario: Once App1 is migrated to Azure, you must ensure that new data can be written to the app, and the modification of new and existing data is prevented for a period of three years.As an administrator, you can lock a subscription, resource group, or resource to prevent other users in your organization from accidentally deleting or modifying critical resources. The lock overrides any permissions the user might have. Reference: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources

Reference: https://docs.microsoft.com/en-us/azure/active-directory/governance/manage-user-access-with-access-reviews