Comprehensive and Detailed Explanation From Exact Extract:
The CloudFormation template feature should be used to specify the AWS resources to be provisioned. A template is a JSON or YAML file that defines the resources (e.g., EC2 instances, S3 buckets) and their configurations for deployment. The WGU Cloud Deployment and Operations Study Guide (Section 5.3, CloudFormation Templates) states, "The template is the core component of CloudFormation, containing the resource specifications and properties that are provisioned when a stack is created." Change sets, exports, and stack sets serve different purposes (e.g., previewing changes, sharing outputs, managing multiple stacks).

Comprehensive and Detailed Explanation From Exact Extract:
AWS CloudFormation uses YAML and JSON languages to define infrastructure as code (IaC) templates, specifying resources, parameters, and configurations. These formats are human-readable and support the creation of stacks for provisioning AWS resources. The WGU Cloud Deployment and Operations Study Guide (Section 5.3, CloudFormation) states, "CloudFormation templates can be written in YAML or JSON, both of which are supported for defining infrastructure resources like EC2 instances and S3 buckets." XML and C# are not supported languages for CloudFormation templates.

Comprehensive and Detailed Explanation From Exact Extract:
The inability to make an AMI public is caused by an encrypted boot volume. AWS does not allow AMIs with encrypted EBS snapshots to be shared publicly due to security constraints; sharing is limited to specific AWS accounts. The WGU Cloud Deployment and Operations Study Guide (Section 6.3, AMI Management) states,
"An AMI cannot be made public if its boot volume is encrypted; encryption restricts sharing to authorized accounts only, requiring decryption keys to be managed separately." Legacy BIOS, paravirtual virtualization, and the absence of a bookmark do not impact AMI sharing.

A Private Hosted Zone in Amazon Route 53 should be used to restrict DNS resolution to instances within a Virtual Private Cloud (VPC), ensuring that the zone is only accessible internally. This isolates DNS services from public internet access. The WGU Cloud Deployment and Operations Study Guide (Section 3.1, Route 53 Hosted Zones) states, "A Private Hosted Zone in Route 53 limits DNS resolution to resources within a specified VPC, preventing external access and enhancing security for internal services." Public Hosted Zones, DNS Zones, and Lightsail DNS Zones do not provide this VPC-specific restriction.

The Enterprise support plan provides a technical account manager (TAM) and full use of Trusted Advisor, offering proactive guidance and comprehensive access to all checks. This plan is designed for large-scale, mission-critical workloads. The WGU Cloud Deployment and Operations Study Guide (Section 6.4, AWS Support Plans) states, "The Enterprise support plan includes a dedicated Technical Account Manager and full Trusted Advisor access, providing 24/7 support and proactive optimization recommendations." Developer, Standard, and Business plans offer limited or no TAM support and partial Trusted Advisor access.