Explanation:
AWS Certificate Manager (ACM) certificates must be created in the same account where the resource (like an Application Load Balancer) that uses them resides. Therefore, the certificate should be requested in the development account. For DNS validation, ACM provides CNAME records that must be added to the DNS configuration. Since Route 53 is managed in the shared account, the SysOps administrator must create those CNAME records in the shared account's Route 53 hosted zone to complete the validation process. KMS (Options A and D) is not used for ACM DNS validation.
Ultimate access to all questions.
Question 4
A company uses a multi-account structure in the AWS Cloud. The company's environment includes a shared account for common resources. The environment also includes a development account for new application development. The company uses Amazon Route 53 for DNS management. The company manages all its Route 53 hosted zones from the shared account.
A SysOps administrator needs to obtain a new SSL/TLS certificate for an application that is deployed in the development account.
What must the SysOps administrator do to meet this requirement?
A
Create a new AWS Key Management Service (AWS KMS) key in the shared account. Configure the key policy to give read access to the development account's root principal.
B
Request a new certificate by using AWS Certificate Manager (ACM) from the shared account. Use Route 53 from the shared account to create validation record sets in the relevant hosted zone.
C
Request a new certificate by using AWS Certificate Manager (ACM) from the development account. Use Route 53 from the shared account to create validation record sets in the relevant hosted zone.
D
Create a new AWS Key Management Service (AWS KMS) key in the development account. Configure the key policy to give read access to the shared account's root principal. Use Route 53 from the shared account to create a validation record set that references the Amazon Resource Name (ARN) of the KMS key.
No comments yet.