---
esco_uri: http://data.europa.eu/esco/skill/d3286405-49f8-4e8a-8046-a4376b4e7963
esco_label: "manage cloud data and storage"
relation: optional
onet_soc: 15-1242.00
source: model-knowledge
confidence: high
qa_count: 0
generator: gemma3:27b (prompt-designed and spot-checked by Claude)
generated: 2026-07-10
---

# manage cloud data and storage — Database Administrator

For a Database Administrator, 'manage cloud data and storage' isn’t just about *having* cloud storage; it's about extending traditional DBA skills to a distributed, often serverless environment. Daily tasks shift from physical hardware provisioning to configuring services like AWS RDS/Aurora, Azure SQL Database, or Google Cloud Spanner. You'll be defining backup & recovery strategies leveraging cloud-native tools (e.g., AWS Backup, Azure Recovery Services Vault), setting up data lifecycle policies for cost optimization and compliance (retention periods!), and ensuring consistent performance through proper storage tier selection (hot/cold/archive). Think less 'disk space is full' and more 'optimize S3 Glacier Deep Archive costs while meeting regulatory requirements'.

Specifically, you’ll be heavily involved in data protection – implementing encryption at rest *and* in transit using KMS or similar services. This includes key management, rotation policies, and auditing access. Capacity planning becomes predictive; instead of over-provisioning, you're monitoring usage metrics (CloudWatch, Azure Monitor) and auto-scaling storage based on demand.  You’ll also be responsible for data residency considerations – ensuring data is stored in the correct geographic region to meet compliance needs like GDPR.

The biggest pitfalls are underestimating cloud costs (easy to spin up resources, harder to shut them down!), neglecting security configurations (misconfigured S3 buckets are a common issue), and assuming on-premise DBA knowledge directly translates.  Cloud databases often have different performance characteristics and require understanding of vendor-specific tuning parameters. Monitoring isn’t just about CPU/memory; it's also about API request rates, storage IOPS, and data transfer costs.

Good looks like automated infrastructure as code (Terraform, CloudFormation) for consistent deployments, robust monitoring & alerting, proactive cost management, and a deep understanding of the cloud provider’s database services. It means being able to quickly respond to incidents *and* prevent them through automation and best practices.  Essentially, you're shifting from 'keeping the servers running' to 'ensuring data is available, secure, compliant, and cost-effective in the cloud'.

## Weitere Anreicherung

Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).
