New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon SAP-C02 Exam - Topic 8 Question 34 Discussion

Actual exam question for Amazon's SAP-C02 exam
Question #: 34
Topic #: 8
[All SAP-C02 Questions]

A company has multiple lines of business (LOBs) that toll up to the parent company. The company has asked its solutions architect to develop a solution with the following requirements

* Produce a single AWS invoice for all of the AWS accounts used by its LOBs.

* The costs for each LOB account should be broken out on the invoice

* Provide the ability to restrict services and features in the LOB accounts, as defined by the company's governance policy

* Each LOB account should be delegated full administrator permissions regardless of the governance policy

Which combination of steps should the solutions architect take to meet these requirements'? (Select TWO.)

Show Suggested Answer Hide Answer
Suggested Answer: B, E

Create AWS Organization:

In the AWS Management Console, navigate to AWS Organizations and create a new organization in the parent account.

Invite LOB Accounts:

Invite each Line of Business (LOB) account to join the organization. This allows centralized management and governance of all accounts.

Enable Consolidated Billing:

Enable consolidated billing in the billing console of the parent account. Link all LOB accounts to ensure a single consolidated invoice that breaks down costs per account.

Apply Service Control Policies (SCPs):

Implement Service Control Policies (SCPs) to define the services and features permitted for each LOB account as per the governance policy, while still delegating full administrative permissions to the LOB accounts.

By consolidating billing and using AWS Organizations, the company can achieve centralized billing and governance while maintaining independent administrative control for each LOB account


Contribute your Thoughts:

0/2000 characters
Yen
3 months ago
C is good for service limits, but not sure it's essential here.
upvoted 0 times
...
Francoise
3 months ago
A seems unnecessary if B covers it all.
upvoted 0 times
...
Lashonda
3 months ago
Wait, can LOB accounts really have full admin permissions? Sounds risky.
upvoted 0 times
...
Melda
4 months ago
I think D is a must too, gotta enforce those policies!
upvoted 0 times
...
Jeannine
4 months ago
Definitely B and E! Perfect for consolidated billing.
upvoted 0 times
...
Merrilee
4 months ago
I feel like we need to ensure governance, so option D with the SCP sounds right, but I'm not completely sure about the first step.
upvoted 0 times
...
Kindra
4 months ago
I practiced a similar question about billing and permissions, and I think enabling consolidated billing with option E is definitely a step we need to take.
upvoted 0 times
...
Alysa
4 months ago
I'm a bit unsure about the service quotas. I thought they were more about limits rather than restricting features. Maybe option D is better for that?
upvoted 0 times
...
Helaine
5 months ago
I remember studying AWS Organizations and how it helps with consolidated billing, so I think option B might be a good choice.
upvoted 0 times
...
Carlee
5 months ago
This is a good example of a complex scenario that requires a thoughtful, multi-faceted solution. I'll need to carefully weigh the pros and cons of each option to determine the best approach.
upvoted 0 times
...
Micheal
5 months ago
I feel pretty confident about this one. I think the combination of using AWS Organizations and implementing service quotas or SCPs is the way to go. I'll make sure to thoroughly explain my reasoning in the exam.
upvoted 0 times
...
Shannon
5 months ago
Hmm, I'm a bit confused by the requirement to delegate full admin permissions to the LOB accounts. That seems to conflict with the need to restrict services and features. I'll have to think through that part carefully.
upvoted 0 times
...
Mirta
5 months ago
Okay, let's see here. The key seems to be using AWS Organizations to manage the accounts and billing. I'm leaning towards option B, but I'll need to double-check the details.
upvoted 0 times
...
Niesha
5 months ago
This looks like a tricky one. I think I'll need to carefully review the requirements and consider the different options presented.
upvoted 0 times
...
Georgiann
5 months ago
Patator seems like it might be overkill for this task. I think I'll go with CeWL since it's specifically designed for website crawling and wordlist generation.
upvoted 0 times
...
Annamaria
5 months ago
I'm a bit confused by this question. The details about the Accounting Flex field structure aren't totally clear to me. I'll need to think it through step-by-step.
upvoted 0 times
...
Jordan
2 years ago
Hmm, I'm not sure about B. Shouldn't we be able to restrict services and features per LOB account? Maybe a combination of B and C would work better.
upvoted 0 times
Alberto
2 years ago
D) Create an SCP that allows only approved services and features then apply the policy to the LOB accounts
upvoted 0 times
...
Gerald
2 years ago
B) Use AWS Organizations to create a single organization in the parent account Then, invite each LOB's AWS account to join the organization.
upvoted 0 times
...
Helene
2 years ago
C) Implement service quotas to define the services and features that are permitted and apply the quotas to each LOB, as appropriate
upvoted 0 times
...
Marsha
2 years ago
A) Use AWS Organizations to create an organization in the parent account for each LOB Then invite each LOB account to the appropriate organization
upvoted 0 times
...
...
Jordan
2 years ago
That's a good point, we can use service quotas in combination with AWS Organizations to meet all the requirements.
upvoted 0 times
...
Evangelina
2 years ago
But shouldn't we also implement service quotas to restrict certain services for each LOB?
upvoted 0 times
...
Maynard
2 years ago
I agree, that way we can easily manage the accounts and control the permissions.
upvoted 0 times
...
Margery
2 years ago
D looks tempting, but I'm not sure that giving each LOB full admin permissions aligns with the governance policy requirements. B is probably the safer choice.
upvoted 0 times
Josphine
2 years ago
That's a good point. B seems like the better option to ensure we meet all the requirements.
upvoted 0 times
...
Shelia
2 years ago
True, but D might not align with the governance policy requirements if it gives full admin permissions to each LOB account.
upvoted 0 times
...
Meaghan
2 years ago
But D could also work if we create a policy that only allows approved services and features in the LOB accounts.
upvoted 0 times
...
Joni
2 years ago
I think B is the safer choice as it allows us to invite each LOB's AWS account to join a single organization in the parent account.
upvoted 0 times
...
...
Lashandra
2 years ago
I agree, B is the way to go. Consolidated billing is key here, and having a single organization makes that easier to manage.
upvoted 0 times
...
Temeka
2 years ago
Option B seems like the most straightforward way to handle the requirements. Creating a single organization and adding the LOB accounts seems simpler than creating multiple organizations.
upvoted 0 times
Dierdre
2 years ago
Yes, creating a single organization and inviting the LOB accounts would simplify the process.
upvoted 0 times
...
Dalene
2 years ago
I agree, Option B does seem like the most straightforward approach.
upvoted 0 times
...
...
Jordan
2 years ago
I think we should use AWS Organizations to create an organization for each LOB.
upvoted 0 times
...

Save Cancel