Examkin

Question

Difficulty: HardConfigure Azure Data Box and Import/Export Services

An organization needs to import 75 TB75\text{ TB} of unstructured data from an on-premises network-isolated Linux server cluster to Azure Block Blob storage. The local cluster has no outbound internet connectivity, and the organization wants to minimize administrative overhead and hardware management during the transfer. Which of the following actions must the administrator perform to successfully complete this import process? (Select TWO.)

  1. Order a single Azure Data Box device and copy the data using the NFS protocol.Answer
  2. From the local web UI of the Data Box, configure the client IP addresses of the Linux servers under the NFS client access settings.Answer
  3. C
    Order three Azure Data Box Disk devices and mount them directly to the Linux servers using the NFS protocol.
  4. D
    Prepare physical drives using the WAImportExport tool on a Linux server and format them with the ext4 file system.
  5. E
    Install the Azure File Sync agent on the Linux servers and configure a sync group targeting the Azure Storage account over a private endpoint.

Answer

To successfully import the data, the administrator must order a single Azure Data Box device and copy the data using the NFS protocol, and configure the client IP addresses of the Linux servers under the NFS client access settings in the local web UI of the Data Box.
A single Azure Data Box device provides up to 80 TB80\text{ TB} of usable capacity, which accommodates the 75 TB75\text{ TB} dataset. Because the source system is a Linux cluster and the environment is network-isolated, utilizing the Data Box's native NFS share support is the most efficient method to copy data without extra infrastructure. To enable this, the administrator must configure the NFS client access settings in the Data Box's local web UI by adding the IP addresses of the Linux servers.

Step-by-Step Solution

1
Determine the optimal transfer service based on constraints.
Since the dataset is 75 TB75\text{ TB} and there is no outbound network connectivity, online tools are ruled out. Data Box Disk is limited to 35 TB35\text{ TB} usable capacity, making Azure Data Box (with 80 TB80\text{ TB} usable capacity) the correct choice. Using Data Box also eliminates the need to purchase and format custom drives as required by the Import/Export service.
Properly aligning capacity limits and hardware constraints avoids multi-device ordering overhead and protocol mismatches.
2
Connect the Data Box to the local network and configure access.
Connect the device and configure its network parameters. Access the local web UI of the Data Box to unlock it with the key provided in the Azure Portal.
The device must be unlocked locally using Azure credentials before it can expose shares for copying.
3
Configure NFS client access on the Data Box.
Navigate to the NFS share settings in the local web UI and add the IP addresses of the source Linux servers. Mount the shares on the Linux servers and copy the data directly.
By default, NFS access is blocked until client IPs are explicitly permitted in the local configuration of the Data Box.

Key Concept

Selecting and configuring the appropriate Azure offline data transfer service (Azure Data Box vs. Data Box Disk or Import/Export) based on capacity, OS compatibility, and protocol requirements.
Estimated Time:2m 30s
Rate this question

Topics

Configure Azure Data Box and Import/Export Services

More questions from this topic