Practise the standard verbs for hardening S3 bucket access.
0 / 5 completed
1 / 5
Fill in: 'We ___ public access on every bucket by default so a misconfigured file never gets exposed to the internet.'
We 'block public access' — the standard, established AWS collocation for the account-level protective setting. The other options aren't the recognised term here.
2 / 5
Fill in: 'An overly broad bucket policy can ___ far more principals read access than the application actually needs.'
We say a loose policy will 'grant' excess access — the standard, established IAM collocation for the resulting permission. The other options aren't the recognised term here.
3 / 5
Fill in: 'We ___ least-privilege principles when writing a bucket policy instead of reaching for a wildcard action.'
We 'apply principles' — the standard collocation for putting a design approach into practice. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ bucket policies against a linter in CI so an accidental public-read statement never merges.'
We 'scan' policies — the standard, established security collocation for automated static checking. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ access logs for every sensitive bucket so an unexpected download gets noticed quickly.'
We 'enable logging' — the standard, simple collocation for turning on an audit feature. The other options are less idiomatic here.