DVA-C02 Deployment Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  1. Register or have a domain, 2. Request or import a certificate in ACM, 3. Create a custom domain name in API Gateway, 4. Create an API mapping to a stage, 5. Update DNS records to point to the API Gateway domain name

  Why this is correct

  This order is correct because you first need a domain and a certificate to secure it, then create the custom domain in API Gateway, map it to your API stage, and finally update DNS to complete the setup.

• ✗

  1. Create a custom domain name in API Gateway, 2. Register or have a domain, 3. Request or import a certificate in ACM, 4. Create an API mapping to a stage, 5. Update DNS records

  Why it's wrong here

  This order is incorrect because creating a custom domain name in API Gateway (step 1) has prerequisites that are not met. Specifically, the API Gateway console or API requires an existing domain name and a valid SSL/TLS certificate from AWS Certificate Manager (ACM) to be selected during the custom domain creation process. Without a registered domain (step 2) and an issued or imported certificate (step 3) in place beforehand, this initial step cannot be successfully completed, leading to an immediate failure.

• ✗

  1. Update DNS records, 2. Register or have a domain, 3. Request or import a certificate in ACM, 4. Create a custom domain name in API Gateway, 5. Create an API mapping to a stage

  Why it's wrong here

  This order is incorrect because updating DNS records (step 1) is a final configuration step that directs traffic to a fully provisioned endpoint. Before DNS records can be meaningfully updated, the API Gateway custom domain name must first be created and configured, and then mapped to an API stage. Attempting to update DNS records without a pre-existing, configured API Gateway custom domain endpoint means there is no valid target for the DNS record to point to, rendering the update ineffective and causing resolution failures.

• ✗

  1. Register or have a domain, 2. Create a custom domain name in API Gateway, 3. Request or import a certificate in ACM, 4. Create an API mapping to a stage, 5. Update DNS records

  Why it's wrong here

  This order is incorrect because the sequence of creating the custom domain name in API Gateway (step 2) before requesting or importing a certificate in ACM (step 3) is reversed. When configuring a custom domain in API Gateway, it is mandatory to associate an SSL/TLS certificate with it to enable secure HTTPS communication. This certificate must already exist in AWS Certificate Manager (ACM) in the same region as the API Gateway, making the certificate acquisition a necessary precursor to custom domain creation.

Go deeper

Related to this question