An IT systems architect for a municipal transit agency is mapping operational workload requirements to essential cloud computing features. Match each transit infrastructure operational scenario on the left with its corresponding cloud computing characteristic on the right.
- Transit API server instances automatically expand compute capacity during unexpected severe weather delays and immediately scale down when passenger queries subside.Rapid Elasticity
- Route analysts can independently spin up temporary database instances using an automated administrative dashboard without submitting support tickets to the cloud vendor.On-Demand Self-Service
- Multiple city departments dynamically share physical host servers while multi-tenant software boundary controls keep department data logically isolated.Resource Pooling
- The agency's monthly cloud invoice accurately details and charges for the precise amount of processing time, network bandwidth, and storage consumed by GPS tracking units.Measured Service
Cevap
The operational scenarios correctly pair with the following cloud characteristics: automatically expanding and contracting server capacity pairs with Rapid Elasticity; provisioning instances independently via an automated portal pairs with On-Demand Self-Service; dynamically sharing physical host infrastructure across multi-tenant departments pairs with Resource Pooling; and billing based on tracked resource consumption pairs with Measured Service.
Each scenario maps directly to a standard NIST essential cloud characteristic: dynamic workload-driven auto-scaling maps to Rapid Elasticity; autonomous user provisioning via self-service interfaces maps to On-Demand Self-Service; shared physical compute infrastructure serving multiple isolated users maps to Resource Pooling; and granular resource metering for billing maps to Measured Service.
Adım Adım Çözüm
Anahtar Kavram
Essential NIST Cloud Computing Characteristics (Rapid Elasticity, On-Demand Self-Service, Resource Pooling, Measured Service)