AZ-305 Korean 無料問題集「Microsoft Designing Microsoft Azure Infrastructure Solutions (AZ-305 Korean Version)」

解説: (JPNTest メンバーにのみ表示されます)

解説: (JPNTest メンバーにのみ表示されます)

Explanation:
Box 1: Log queries
The diagram and table below compare the Analytics, and Basic table plans.

Box 2: Ingestion
Reference:
https://learn.microsoft.com/en-us/azure/azure-monitor/logs/data-platform-logs

解説: (JPNTest メンバーにのみ表示されます)

Explanation:
Creating an Always On availability group on VM1 would not be necessary, as you already have an availability group (AG1) in place on your on-premises SQL Server instances.
By adding a secondary replica to AG1, you can provide a copy of DB1 that can be used for the migration. This will allow you to minimize downtime on DB1 by performing the migration on the secondary replica, while the primary replica remains available for use.
While using Azure Migration can simplify the migration process, it may not necessarily minimize downtime. You may still need to plan for an appropriate maintenance window to complete the migration with minimal disruption to your application.

Explanation:
Box 1: Yes
The storage account and SQL server are in the same region, ensuring compliance with the requirement that audit logs be stored in a storage account in the same region as the server.
Box 2: No
Since the regions are different, the audit logs cannot be stored in storage2 for SQLdb2.
Box 3: No
Since the regions are different, the audit logs cannot be stored in storage2 for SQLdb3.
Note: While configuring auditing for azure sql db, azure portal only will show storage accounts which are in same region. Both standard and premium storage accounts can be used but they need to be in same region as db.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/auditing-overview#auditing-limitations

Explanation:
Box 1: Storage1 and storage3 only
Azure Blob Storage lifecycle management offers a rich, rule-based policy for GPv2 and blob storage accounts. Storage 2 does not support access tiers.
Box 2: Storage1 and storage4 only
FileStorage storage accounts allow you to deploy Azure file shares on premium/solid-state disk- based (SSD-based) hardware.
Reference:
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-lifecycle-management-concepts
https://docs.microsoft.com/ja-jp/azure/storage/common/storage-account-overview

解説: (JPNTest メンバーにのみ表示されます)

Explanation:
For ETL operations use Azure Data Factory and Azure Synapse Pipelines are based on Azure Data Factory.
Source: https://learn.microsoft.com/en-us/azure/synapse-analytics/data-integration/concepts- data-factory-differences For restricted access use Azure Data Share:
Azure Data Share enables organizations to securely share data with multiple customers and partners. Data providers are always in control of the data that they've shared and Azure Data Share makes it simple to manage and monitor what data was shared, when and by whom.
In this case snapshot-based sharing should be used.
Source: https://learn.microsoft.com/en-us/azure/data-share/overview

Explanation:
Box 1: vCore
Virtual core (vCore)-based purchasing model (recommended). This purchasing model provides a choice between a provisioned compute tier and a serverless compute tier. With the provisioned compute tier, you choose the exact amount of compute resources that are always provisioned for your workload. With the serverless compute tier, you specify the autoscaling of the compute resources over a configurable compute range Box 2: An Azure SQL Database Elastic pool Azure SQL Database provides the following deployment options for a database:
Single database represents a fully managed, isolated database. Elastic pool is a collection of single databases with a shared set of resources, such as CPU or memory. Single databases can be moved into and out of an elastic pool.
Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/purchasing-models

解説: (JPNTest メンバーにのみ表示されます)