Pre-Deployment Check

D-PDD-DY-01 · 42 questions

• A customer hands over raw front-end numbers at kickoff: 2 PB of VMs and file systems to protect, growing 30 percent a year, and expects one Data Domain system to hold it all. An engineer is about to choose a platform tier. Why must those raw front-end estimates be translated before a platform can be selected?
• The customer's backup administrator states that nightly backups of 40 TB of front-end data must complete inside a six-hour window. The new Data Domain appliance looks comfortable on capacity alone. What does that backup window tell the engineer during the pre-deployment review?
• A requirements interview finds that backups will come from NetBackup, from Veeam, and from a legacy NetApp filer that runs no backup agent. The engineer must record which Data Domain connection methods each source needs. Which mapping belongs in the design?
• Two departments will share one new Data Domain system, but the security review requires that neither can see or address the other's data, namespaces, or administration. When should the engineer capture this requirement, and what design decision does it drive?
• A compliance officer in a regulated industry insists that no backup copy may be deleted or altered by anyone, including the backup administrator, until seven-year retention has fully expired. Where does this requirement belong in the deployment plan, and what feature answers it?
• During the security requirement review, the customer's security team demands that the encryption keys protecting backup data at rest be held in their own external key manager rather than on the appliance. What is the correct pre-deployment action for the engineer?
• The DR plan requires a replicated copy of a new Data Domain system at a site 800 km away, and the survey measured 200 ms round-trip latency on a constrained WAN link. What determines whether this replication design is feasible?
• After last year's ransomware incident, the customer demands a backup copy that an attacker holding production administrative credentials can never reach from the production network. Which pre-deployment response is correct?
• The design calls for one Data Domain head unit plus two expansion shelves, and facilities asks how much rack elevation to reserve before the order ships. How should the engineer determine the correct amount?
• During the site survey, facilities shows the engineer the target rack, which has two PDUs fed from a single circuit. What power verification belongs in the pre-deployment checklist before the system ships?
• A fully loaded expansion shelf is far too heavy for one person to carry, and the path from the loading dock crosses a freight elevator and a narrow corridor door. When and how should this be handled?
• The proposed rack position sits near a roof line where the data center runs warm, and summer readings have crept above the mid-20s Celsius. What should the engineer do about this during the site survey?
• Before arrival, the network team asks what the Data Domain deployment will need in writing. The system must support administrative access, backup traffic, and replication to the DR site. What should the pre-deployment network plan contain?
• The customer's policy issues every device an address through DHCP with no DNS records, but the deployment plan wants to administer the new Data Domain system and issue its certificates by hostname. Which pre-deployment requirement resolves this conflict?
• The security team runs a default-deny firewall and asks the engineer to produce, as one deliverable, everything that must be opened for the new Data Domain system. What belongs in that deliverable, and why is it a first-week item?
• A small remote office wants Data Domain deduplicating backup behavior for a few terabytes, but the site has a single VMware host, a small closet, no rack space, and no spare power. Which form-factor decision do the captured pre-deployment requirements support?
• The customer wants five years of monthly backup copies retained on cheaper storage and asks what the appliance design must include right now to make that work. What is the correct pre-deployment answer?
• Before shipping, an engineer notes the DD OS version the new platform will run and the customer's backup application and media server versions. What is the correct compatibility action, and where does the answer come from?
• The data center permits no outbound traffic without a security exception, and at the design review Dell support asks how proactive call-home support will work on the new Data Domain system. What is the correct pre-deployment action?
• The customer's change board approves exactly one maintenance window, Sunday from 02:00 to 06:00, for introducing the new backup target to production. What should the engineer do with that information during pre-deployment planning?
• At kickoff, the design review settles hostnames, the IP scheme, administrator contacts, and who signs each project phase. From the requirements task's point of view, what closes that task?
• Crates arrive on a Friday afternoon. Working through the installation checklist, the engineer opens the packing list. What is the engineer reconciling it against, and why is that the checklist's first hardware step?
• The hardware is racked, and the engineer reaches the service-tag portion of the installation checklist. What is the correct first step with service tags?
• Every service tag is now recorded on the installation worksheet. Before touching a screwdriver, the engineer proceeds with the pre-installation checklist. What is each service tag used for at this stage?
• At the dock, a carton holding new Data Domain gear shows a crushed corner, and the tipped-package indicator on its side has tripped. The carrier driver waits for a signature. What does the installation checklist's receiving step tell the engineer to do?
• Pre-staging a PowerProtect Data Domain head unit, the engineer opens the rail kit and notices the shipped rails don't match the customer's rack type. The customer's team wants to 'just mount it, it will fit.' What does the installation checklist tell the engineer to do?
• During receiving, the project manager asks why the engineer is photographing every service tag and serial number into the deployment binder instead of just typing in the head unit's serial. What is the best answer?
• Receiving verification shows the Data Domain head shipped with a DD OS version older than the minimum required by the customer's backup application support matrix. The install is scheduled for today. What does the installation checklist's software-version step call for?
• Before the first customer backup is allowed to write to a freshly built Data Domain system, the engineer reads the DD OS release notes for the exact planned build. Which pre-installation practice does this support?
• At unboxing, the power cords included with the appliance end in a connector type the customer's PDUs don't have, and someone reaches for a third-party adapter. What should the installation checklist's power section have caught, and what is the right response?
• A site-survey photo shows the target rack, and the engineer is about to rack the head unit on the morning of the install. How should the installation checklist's rack and mechanical section—mounting hole pattern, rack depth, rear service space—be handled?
• On install morning the head unit is staged and the schedule says start today, yet the paperwork shows the expansion shelf's pallet is still sitting in customs. What does the installation checklist's shipment-verification step call for?
• The accessory kit holds two lengths of storage interconnect cable, and the planned layout puts the expansion shelf several rack units below the head unit. What does the checklist's cabling section call for before the install day?
• The customer's rack uses square mounting holes, and the rail kit's hardware list shows screws that mate with cage nuts—yet the box contains screws and no cage nuts. What does the checklist's mounting-hardware step call for?
• At the staging area before racking, the checklist calls for unpack-and-inspection steps and handling-equipment guidance. The team's lift is rated below the loaded chassis weight and someone suggests 'being careful instead.' What does correct staging practice require?
• The installation checklist has blanks for hostname, the management addressing choice between static and DHCP, and the DNS and gateway entries. The on-site engineer plans to 'pick sensible values at bring-up.' What does the checklist intend by having these filled from the design document beforehand?
• The checklist's loading plan puts the expansion shelves at the lowest rack positions, but the customer's technician wants the head unit at the bottom 'because the lights look better down there.' What wins?
• The design requires encryption at rest and cloud tiering, and the installation checklist includes a step confirming the order actually includes those features. When should that entitlement check happen, and why?
• Cutover day arrives, the only person the installer knows at the customer site is on vacation, and nobody else holds badge access to the server room. The installation checklist's contact block had been left blank. What is that checklist item actually for?
• The physical installation is complete and the system is reachable. The project manager asks what closes out the installation-checklist paperwork for this engagement. What completes the task?
• Leaving the server room, the engineer runs the checklist's final sweep: service tags recorded, photographs taken, serials listed. A colleague suggests doing that later from the shipping paperwork at the hotel. Why does the checklist make it an on-site sweep?
• Packing-list reconciliation against the checklist at 4 p.m. the day before install finds one expansion shelf unaccounted for—ordered but on no delivery record. The team wants to rack what they have and hope the shelf turns up. What does proper checklist discipline require?