Arrange these steps for requesting and issuing a server certificate in the correct order. Certificate Authority (CA) is expanded here for clarity.

### Why this is right The server must first have a key pair before it can put the public key into a request or sign that request. After the CA receives and checks the signed request, it can issue a certificate that binds the subject information to the public key. ### The order 1. **The server generates its private key.** The key pair must exist before the server can create a request or demonstrate possession of the key. 2. **The server creates a Certificate Signing Request (CSR) containing its public key and subject information.** The request identifies the key and the subject for which a certificate is requested. 3. **The server signs the request with its private key to show possession of the corresponding key.** This proves control without placing the private key in the request. 4. **The CA checks the request and signs the issued server certificate with the CA’s private key.** The CA’s signature creates the certificate that a verifier can later check. ### Terms - **Certificate Authority (CA)**: An entity that reviews requests and signs certificates. - **Certificate Signing Request (CSR)**: A request containing the public key and subject information to be certified. - **Public key**: The shareable part of the server’s key pair. - **Private key**: The secret part of the key pair, retained by its owner. - **Certificate**: A signed record binding a subject to a public key. ### Remember Generate the key before requesting certification, and have the CA sign only after it receives and checks the request.