In AWS Organizations, which account is responsible for paying the charges of all the accounts in the organization?
Easy · Choose one
Explanation
Answer: A. Every organization has exactly one management account, also referred to as the payer account, and it pays the charges of all the member accounts. Centralizing payment is what makes consolidated billing possible: because AWS sees the organization's usage as a whole, volume tiering and commitment discounts can be applied across the pooled usage rather than account by account.
B. Order of joining has no bearing on payment responsibility. The management account is the account that created the organization.
C. A delegated administrator can perform certain billing tasks, but financial responsibility for the organization's charges remains with the management account.
D. Separate payment is exactly what consolidated billing removes. Member accounts continue to see their own costs but do not receive separate invoices.
32
What is a benefit of using consolidated billing in AWS Organizations?
Easy · Choose one
Explanation
Answer: D. Consolidated billing aggregates usage across every account in the organization. Because tiered pricing for services such as Amazon S3 and data transfer becomes cheaper as monthly volume rises, pooling usage moves the organization into lower-priced tiers faster than the same usage split across standalone accounts. The same pooling lets Reserved Instance and Savings Plans discounts be applied wherever matching usage exists.
A. AWS offers consolidated billing at no additional charge. There is no per-account fee for joining an organization.
B. The organization receives one bill from the management account. Separate invoices with independent volume tiers describe standalone accounts, which is the arrangement consolidated billing improves upon.
C. Consolidated billing does not share identities. Accounts remain isolated security boundaries, and cross-account access requires IAM roles or AWS IAM Identity Center.
33
Which mechanism allows a company to categorize AWS resources so that costs can be broken down by department, project, or environment in billing reports?
Easy · Choose one
Explanation
Answer: C. Cost allocation tags are key-value pairs attached to resources that AWS then carries through into Cost Explorer and the Cost and Usage Report as dimensions. Once activated, a tag such as CostCenter or Environment lets an organization attribute spend to the teams that generated it. A consistent tagging strategy is the foundation of showback and chargeback, because untagged resources cannot be allocated to anyone.
A. Service control policies define the maximum permissions available to accounts in an organization. They govern what can be done, not how cost is attributed.
B. Resource groups organize resources for operational tasks such as automation and patching. They do not feed billing reports as cost dimensions.
D. Placement groups influence how Amazon EC2 instances are physically positioned for networking performance or resilience. They have no billing role.
34
Where can a customer find the published per-unit prices for AWS services before creating an account?
Easy · Choose one
Explanation
Answer: B. AWS publishes list pricing publicly on a pricing page for each service, and the same rates back AWS Pricing Calculator and the AWS Price List API. Transparent public pricing is deliberate: it lets prospective customers model costs, compare options, and build a business case with no account, no sales conversation, and no commitment.
A. AWS Support handles account, billing, and technical cases for existing customers. It is not the route to obtain list pricing.
C. Partners can offer their own commercial terms, but AWS list pricing is public and does not depend on engaging a partner.
D. The Billing and Cost Management console shows what an account has been charged. Published rates are available beforehand, on the public website.
35
Which statement about the two types of AWS cost allocation tags is correct?
Intermediate · Choose one
Explanation
Answer: D. AWS distinguishes tags that it generates from tags that the customer defines, and the prefix makes the origin unambiguous in billing data. AWS-generated tags carry the aws: prefix, with createdBy as a common example, and are defined, created, and applied by AWS or by an AWS Marketplace independent software vendor. User-defined tags carry the user: prefix and reflect the customer's own taxonomy. Both types must be activated separately before they appear in Cost Explorer or in a cost allocation report.
A. The prefixes are the other way around. The aws: namespace is reserved for tags AWS creates.
B. User-defined tags are created and managed entirely by the customer, which is what makes them useful for departmental cost allocation.
C. The prefix identifies who created the tag, not what kind of resource it applies to. Tags apply across resource types.
36
A company activates a new user-defined cost allocation tag but does not see it in Cost Explorer immediately. What should it expect?
Intermediate · Choose one
Explanation
Answer: A. AWS documents that all tags can take up to 24 hours to appear in the Billing and Cost Management console after activation. Knowing this prevents a common mistake, which is re-tagging resources or reconfiguring reports in response to a delay that is simply normal processing time. It also reinforces why tagging should be established as resources are created rather than retrofitted when a report is due.
B. Cost allocation tags surface in Cost Explorer and cost allocation reports during the current billing period, not only after invoicing.
C. Billing data processing is not instantaneous. A delay of a few hours is expected behavior rather than a sign of misconfiguration.
D. A Cost and Usage Report is one place tags appear, but activation is not conditional on having configured one.
37
Which account can activate cost allocation tags for an organization in the AWS Billing and Cost Management console?
Intermediate · Choose one
Explanation
Answer: D. AWS states that only the management account in an organization, along with standalone accounts that are not organization members, has access to the cost allocation tags manager in the Billing console. Centralizing activation is what keeps the organization's cost taxonomy consistent, since a tag key activated once becomes a reporting dimension across every account in the organization.
A. Member accounts can apply tags to their own resources, but they cannot activate a tag key as a cost allocation dimension. That control sits with the management account.
B. AWS Support plans govern support entitlements such as case severity and Trusted Advisor coverage. They do not determine who can activate cost allocation tags.
C. Enabling a Cost and Usage Report is unrelated to the permission to activate tags.
38
A company is preparing a business case for migrating its on-premises data center to AWS and needs an estimate of the cost savings based on its existing server inventory and utilization. Which AWS service is designed for this?
Intermediate · Choose one
Explanation
Answer: C. Migration Evaluator builds a data-driven business case for migration. It collects inventory and utilization data from the existing on-premises environment and produces a directional cost projection for running those workloads on AWS, including the effect of licensing choices. It is the right tool at the point where an organization has not yet migrated and needs to justify the move financially.
A. AWS Budgets tracks and alerts on spend in an AWS account that already exists. It cannot model an on-premises estate.
B. AWS Compute Optimizer rightsizes resources already running in AWS using CloudWatch metrics. It does not analyze on-premises servers for a migration business case.
D. Cost Explorer analyzes AWS costs that have already been incurred, so it has nothing to report before the migration happens.
39
Which TWO statements about AWS Organizations are correct? (Choose TWO.)
Intermediate · Select 2 answers
Explanation
Answer: D and E. AWS Organizations serves governance and finance at the same time. On the governance side, service control policies set the ceiling on what principals in member accounts are permitted to do, acting as a guardrail rather than a grant of permissions. On the finance side, consolidated billing costs nothing extra: AWS provides one bill, pooled usage for volume tiering, and shared commitment discounts as part of the service.
A. Accounts remain distinct security and resource boundaries after joining an organization. Organizations groups accounts; it does not merge them.
B. The management account receives the bill for the organization. Member accounts can view their own costs but are not invoiced separately.
C. Reserved Instance and Savings Plans discounts are shared across the organization by default when discount sharing is enabled, applying to the owning account first and then to other accounts.
40
Which TWO benefits does a well-implemented resource tagging strategy provide? (Choose TWO.)
Intermediate · Select 2 answers
Explanation
Answer: C and D. Tags are metadata that serve two distinct purposes at once. Financially, activated cost allocation tags become dimensions in Cost Explorer and the Cost and Usage Report, which is what turns an undifferentiated bill into departmental accountability. Operationally, the same tags let teams select resources for automation, apply attribute-based access control in IAM, and drive patching and backup policies. Both benefits depend on tagging being applied consistently as resources are created.
A. Tags do not enforce spending limits. AWS Budgets, optionally scoped by tag and combined with Budgets actions, is what enforces a threshold.
B. Tags are descriptive metadata and have no effect on price. Discounts come from commitment mechanisms such as Savings Plans and Reserved Instances.
E. Encryption is provided by services such as AWS KMS and by service-level encryption settings. A tag has no effect on the confidentiality of data.