Practise the standard verbs for terminating TLS at the nginx edge.
0 / 5 completed
1 / 5
Fill in: 'We ___ TLS at the nginx edge so backend services communicate over plain HTTP inside the trusted internal network only.'
We 'terminate TLS' — the standard, established nginx collocation for ending the encrypted connection at the reverse proxy. The other options aren't the recognised term here.
2 / 5
Fill in: 'Forgetting to set X-Forwarded-Proto after termination can ___ the backend app generating insecure http links in every response.'
We say a missing header will 'leave' the app generating insecure links — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ only modern TLS versions and strong cipher suites so an outdated client can't downgrade the connection to something weak.'
We 'allow' a version or cipher — the standard, established collocation for permitting only approved protocol options. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ certificate renewal with certbot so an expiring TLS certificate never catches us off guard on a Friday evening.'
We 'automate' renewal — the standard, simple collocation for scripting a recurring maintenance task. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the certificate chain with an SSL testing tool after every renewal so a misconfigured intermediate doesn't break older clients.'
We 'verify a chain' — the standard, simple collocation for confirming a certificate setup is correct. The other options are less idiomatic here.