D-NWR-DY-01 Dell NetWorker Deploy v2 Exam Questions and Answers

lic- the traditional ASCII license file (e.g.dpa.lic) used for Capacity or Update Entitlements in NetWorker 19.2–19.8.

xml- the newer Unserved XML Capacity Entitlement file supported in NetWorker 19.9 and later (configured via

In a NetWorker environment integrated with LDAP/AD, users must authenticate against the NetWorker Authentication Service to execute commands with appropriate privileges. Thensrlogincommand isused to authenticate the user with the Authentication Server, establishing the required session context. This resolves privilege-related failures when running NetWorker commands.

When you deploy the vProxy OVA in vCenter, the “Admin” and “Root” password fields are optional - if you leave them blank, the appliance automatically uses its built‑in defaults (admin: a3dp@m8n, root: changeme) and the deployment completes normally.

In the Simulator, do the following:

1.Open the Authentication Server view

In the left‑hand menu clickAuthentication Server➔Directories.

2.Add a new Active Directory directory

Click+ Add Directory(or+).

ForDirectory TypechooseActive Directory.

3.Fill in the AD details

Name:LAB_AD

Server Hostname/IP:win2k16.lab.emc.com

Tenant:default

User DN:cn=administrator,cn=users

Password:Password123#

4.(Optional)If your environment requires it, enableStartTLSor specify aBase DN(e.g.cn=users)—but in most lab setups the defaults will work.

5.Test & Save

ClickTest Connectionto verify you can bind to the AD server.

Once successful, clickSave.

The Console Security Administrator role is the only NMC role that can add, delete, and modify NetWorker Authentication Service local‐database users and control user access to managed applications (e.g., NetWorker servers).

NetWorker Virtual Edition (NVE) supports simple deployment on Microsoft Azure and Amazon Web Services (AWS) by leveraging their native cloud formats such as Azure Marketplace images and AWS AMIs. These providers offer streamlined provisioning and integration with NetWorker using preconfigured templates or images, simplifying cloud-based backup operations.

Deduplication, encryption, and compression before transfer to the cloud

CloudBoost performs inline deduplication, compression and AES‑256 encryption on the client side (or in‑appliance) so that only minimal, secure data is sent to the cloud object store.

Low‑cost cloud object storage for all backup copies

All backup copies - both short‑term and long‑term - are written to inexpensive, deduplicated cloud object storage (e.g. AWS S3, Azure Blob, ECS), driving down retention costs.

No on‑premises infrastructure required

You can deploy CloudBoost as a virtual appliance directly in public clouds (AWS, Azure, VMware), so no dedicated on‑prem hardware is needed to replicate backups into cloud services.

For successful installation and operation of NetWorker on a Linux system, the presence oflibncursesw(wide-character support for terminal UI) andglibc(the GNU C library) is essential. These libraries are foundational for the functioning of NetWorker’s command-line and daemon processes.