Free AZ-305 Exam Braindumps
Designing Microsoft Azure Infrastructure Solutions Questions 146–150 (page: 31)

Explanation:

Databricks is a cloud-based platform built for big data, AI, and machine learning, geared towards data professionals.
When you use auto-scaling, Databricks automatically determines when to upsize or to downsize. Using auto- scaling allows you to control usage costs. The cluster brings up additional nodes only when they are needed for resource-intensive tasks.
Databricks helps companies process large-scale data, and Databricks data masking ensures high-quality, compliant data.
Azure Databricks supports Microsoft Dataverse through various methods, including direct connection with Cdata JDBC Driver, exporting data to Delta Lake format using Azure Synapse Link, and leveraging Airbyte for data synchronization.
Incorrect.
Not C:
Microsoft Fabric:
Focus: Data integration, transformation, reporting, and business intelligence, especially within the Azure ecosystem.
Target audience: Business users, analysts.

Reference:

Explanation:

Azure Storage Mover is a fully managed, hybrid migration service designed to move on-premises file shares to Azure Blob Storage and Azure Files. It simplifies the process of migrating large volumes of data by automating the transfer and supporting various source types.
You can use Storage Mover for different migration scenarios such as lift-and-shift, and for migrations that you have to repeat regularly. Azure Storage Mover also helps maintain oversight and manage the migration of all your globally distributed file shares from a single storage mover resource.
Supported sources and targets
The current Azure Storage Mover release supports full-fidelity migrations for specific source-target pair combinations. Always utilize the latest agent version to benefit from these supported sources and destinations:
* SMB 2.x mount
Azure file share (SMB)
SMB 1.x sources and NFS Azure file shares are currently not supported.
*-> NFS 3 & 4 mount
Azure blob storage container
Containers with the “Hierarchical Namespace Service (HNS)” feature enabled, are supported and the ADLS Gen2 REST API set is used for migration.
Incorrect:
Not A: Is a more primitive tool.
Note: AzCopy is a command-line utility that enables efficient data transfer to, from, and between Azure Storage accounts. It’s designed to handle large amounts of data, making it a suitable tool for tasks like migrating on- premises data to the cloud or transferring data between different storage accounts.
AzCopy supports hierarchical namespaces. This means it can work with Azure Blob Storage accounts that have the hierarchical namespace enabled, which is also known as Azure Data Lake Storage Gen2.
Not C:
RoboCopy is a Windows-based command-line utility for copying files and directories, primarily used for copying within a file system, while AzCopy is a command-line tool designed for transferring data to and from Azure Storage services.
Not D:
Azure File Sync is a service that synchronizes files between on-premises Windows servers and Azure File shares, providing a hybrid cloud storage solution. It enables you to keep your files in Azure Files while maintaining the familiarity and performance of a local file server.

Reference:

https://docs.azure.cn/en-us/storage/common/storage-ref-azcopy-sync https://learn.microsoft.com/en-us/azure/storage-mover/service-overview

Explanation:

Box 1: Azure Database for PostgreSQL Flexible Server
For horizontal scaling of transactional writes in Azure PostgreSQL using row-based sharding, you should utilize Azure Database for PostgreSQL Flexible Server with Elastic Clusters. This feature leverages the Citus extension for PostgreSQL, enabling you to shard your data across multiple nodes and manage them as a single, distributed database.

Flexible Server:
It offers a flexible and powerful managed PostgreSQL service.

Elastic Clusters:
This feature, powered by Citus, allows horizontal scaling of your PostgreSQL database.

Row-based Sharding:
With row-based sharding, you define a distribution key, and the Citus extension automatically distributes rows based on this key across the nodes in the cluster.

Citus Extension:
Citus is an open-source extension for PostgreSQL that enables distributed database capabilities, including sharding.

Box 2: Distributed tables
Azure Database for PostgreSQL Flexible Server uses distributed tables for scaling through the use of an Elastic cluster, powered by the Citus extension. This allows for scaling out by adding more nodes to the cluster and distributing data across them, rather than just increasing the compute power of a single node.

Distributed Tables:
With an elastic cluster, you can define distributed tables where data is spread across multiple nodes.

Scalability:
By adding more nodes to the cluster, you can scale the database horizontally, increasing both capacity and performance.

Transparent Scaling:
The scaling process is managed transparently by the Citus extension, meaning the application doesn’t need to be aware of the distributed nature of the database.

Vertical vs. Horizontal Scaling:
While vertical scaling (increasing compute and memory on a single node) is still possible, the elastic cluster allows for true horizontal scaling, distributing the workload across multiple nodes.

Incorrect:
* Logical replication
* Near-zero downtime scaling

Reference:

https://techcommunity.microsoft.com/blog/adforpostgresql/postgres-horizontal-scaling-with-elastic-clusters-on- azure-database-for-postgres/4303508

Explanation:

Azure Cache for Redis provides an in-memory data store based on the Redis software. Redis improves the performance and scalability of an application that uses backend data stores heavily. It’s able to process large volumes of application requests by keeping frequently accessed data in the server memory, which can be written to and read from quickly. Redis brings a critical low-latency and high-throughput data storage solution to modern applications.

Reference:

https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-overview

Explanation:

SQL Server to Azure SQL Managed Instance
Azure SQL Managed Instance is a recommended target option for SQL Server workloads that require a fully managed service without having to manage virtual machines or their operating systems. SQL Managed Instance enables you to move your on-premises applications to Azure with minimal application or database changes. It offers complete isolation of your instances with native virtual network support.
Incorrect:
[Not B]
If one of the following conditions applies to your business, consider moving to a SQL Server virtual machine (VM) instead:
*-> You require direct access to the operating system or file system, such as to install third-party or custom agents on the same virtual machine with SQL Server.

Reference:

https://learn.microsoft.com/en-us/data-migration/sql-server/managed-instance/overview