A lead cloud engineer is deploying a new Google Cloud Storage bucket to archive monthly financial transaction audit records in the europe-west3 region. The security and operational requirements specify that:
1. Objects uploaded to the bucket must default to the Nearline storage class.
2. Access control must be enforced strictly via IAM policies by disabling per-object Access Control Lists (ACLs).
3. Any public access to objects within the bucket must be prevented at the bucket level.
Which command should the engineer execute to deploy this bucket according to Google Cloud recommended best practices?
- gcloud storage buckets create gs://fin-audit-archive-euwest3 --location=europe-west3 --default-storage-class=nearline --uniform-bucket-level-access --public-access-preventionCevap
- Bgcloud storage buckets create gs://fin-audit-archive-euwest3 --region=europe-west3 --storage-class=nearline --no-assign-acls --block-public-access
- Cgcloud storage buckets create gs://fin-audit-archive-euwest3 --location=europe-west3 --default-storage-class=coldline --uniform-bucket-level-access --public-access-prevention
- Dgsutil mb -c nearline -l europe-west3 -b on -a public-read-off gs://fin-audit-archive-euwest3
Cevap
The command 'gcloud storage buckets create gs://fin-audit-archive-euwest3 --location=europe-west3 --default-storage-class=nearline --uniform-bucket-level-access --public-access-prevention' fulfills all requirements using modern Google Cloud CLI syntax.
The correct option utilizes the standard 'gcloud storage buckets create' command with proper flag parameters: '--location=europe-west3' sets the bucket location, '--default-storage-class=nearline' sets the default storage class for new objects, '--uniform-bucket-level-access' enforces IAM-only permissions by disabling per-object ACLs, and '--public-access-prevention' prevents public data exposure at the bucket level.
Adım Adım Çözüm
Anahtar Kavram
Cloud Storage Bucket Deployment via gcloud storage CLI