Dell Cloud Infrastructure Design case studies
Dell Cloud Infrastructure Design · Put your knowledge to work in context.
This independent study page provides practice for Dell Cloud Infrastructure Design. Its editorial learning areas include Cloud infrastructure design, alternatives and lifecycle trade-offs; Cloud concepts, architecture and service models; Storage access, protection and capacity reasoning; Identity, access and cryptographic protection; Network boundaries and protected communication; Security operations, monitoring and response; Continuity, backup and technical recovery. The questions develop subject knowledge and application through worked reasoning, distinctions between competing answers, and practical scenarios. Study the relevant guide before attempting a mixed set, then explain the evidence or calculation that supports each answer. The Dell Cloud Infrastructure Design case studies are 4 cases and about 837 words.
1A design comparison hides a shared failure dependency
A fictional organization compares a validated converged stack with a proposed hyperconverged arrangement for a business service. Both proposals meet the supplied average compute demand, but the recovery requirement includes loss of the only shared identity service.
174 words, under 1 min2SaaS access after a role change
A fictional organization uses a managed collaboration service for internal planning documents. The provider maintains the application and underlying servers, while the organization configures users, groups and sharing settings.
221 words, about 1 min3An incident review with an action that can be checked
A fictional delivery team restores service after a release encounters an undocumented database dependency. The initial meeting ends with the statement that the engineer should be more careful, but no owner, test or review date is recorded.
219 words, about 1 min4A recovery target does not prescribe one universal architecture
A fictional order service has a recovery-point objective of fifteen minutes and a recovery-time objective of four hours. A tested option creates consistent recovery points every ten minutes and restores the service in three hours after the declared recovery procedure begins.
223 words, about 1 min