Cloud concept · Updated

Management and governance - Management and governance is the combination of operating cloud resources and establishing the policies, responsibilities, and controls that keep their use aligned with business, security, and compliance requirements.

In short

Management handles activities such as provisioning, monitoring, configuration, and remediation, while governance defines who may act, which standards apply, and how compliance is demonstrated. Together, they help organizations give engineers useful autonomy without losing accountability, cost visibility, or control over risk.

Cloud Concepts Hub →

6 key aspects of Management and governance

Effective management and governance combines clear accountability, scoped compliance obligations, automated controls, operational autonomy, and continuously reviewed evidence.

01
Policies and accountability

Define who owns resources, who approves exceptions, and which security, operational, and financial standards apply. Assign control owners so findings lead to action rather than remaining unaddressed.

02
Shared responsibility and compliance scope

Separate provider responsibilities from customer responsibilities for each service and workload. Check the scope of provider reports and agreements instead of assuming that a certified provider makes every application compliant.

03
Preventive, detective, and corrective controls

Use permission restrictions to prevent prohibited actions, configuration checks to detect deviations, and approved workflows to correct them. Verify whether each control only reports a problem or also changes resources.

04
Controlled autonomy

Give teams self-service access within tested policy boundaries and separated environments. Use least-privilege permissions and documented, time-limited exceptions instead of making every deployment a manual approval exercise.

05
Traceability and audit evidence

Retain protected activity logs, configuration history, policy decisions, and relevant compliance documentation. Evidence should show which controls operated, which resources they covered, and how exceptions were handled.

06
Continuous oversight

Review configurations, access, costs, and control effectiveness as workloads and requirements change. Track remediation to completion and test changes to governance policies before applying them broadly.

Cloud services for Management and governance

AWS Organizations establishes account groupings and permission limits, while AWS Control Tower helps standardize the multi-account environment and apply controls. IAM defines the permissions identities receive within those limits. AWS Config records resource configurations and evaluates selected rules, while CloudTrail captures supported activity that helps explain who changed what. AWS Artifact supplies provider compliance documentation and certain agreements for assessing inherited controls and contractual obligations. Together, these services support policy enforcement and evidence collection, but they do not replace workload-specific safeguards, control ownership, evidence review, or remediation processes.

AWS OrganizationsAWS Organizations

Organizes multiple AWS accounts into organizational units and supports centralized governance through policies such as service control policies. SCPs limit the permissions available to principals in member accounts; they do not grant permissions and do not restrict principals in the organization's management account.

AWS Control TowerAWS Control Tower

Helps establish and govern a multi-account landing zone with standardized account provisioning and controls. Its controls provide governance coverage, but customers must still select appropriate controls, manage exceptions, and address their workload-specific requirements.

AWS ArtifactAWS Artifact

Provides access to AWS compliance reports and certain agreements, including business associate agreements. These documents support assessment of AWS responsibilities and service scope; they do not certify a customer's workload.

AWS ConfigAWS Config

Records supported resource configurations and evaluates them against configured rules. Configuration history and compliance evaluations support investigations and evidence collection; remediation requires a separately configured action or workflow.

AWS CloudTrailAWS CloudTrail

Records supported account activity and API events to support accountability, investigations, and audits. Configure the required event coverage and retention explicitly, because the default event history is not a complete, long-term record of all resource activity.

Management and governance exam questions

Real practice exam questions on Management and governance, with the correct answer and its explanation. Answer them with every option in the exam simulator.

AIB-C01 (beta)

An electric utility is planning a model in Amazon SageMaker AI to recommend the order in which crews restore power after storms. Dispatchers will approve the recommendations. Governance policy requires the utility to reconstruct disputed recommendations, including the input data, model version, and operating rules used at the time. The proposed project budget covers model development and dispatcher training, but the design would overwrite input datasets and retain only the latest model. Before approving the implementation plan, what should the business sponsor require?

Show answerCORRECT ANSWER

Fund traceability requirements now: retain approved model versions in SageMaker Model Registry, preserve relevant input snapshots and operating-rule versions, and link recommendations to this evidence under defined access and retention policies.

Governance by design establishes evidence requirements before architecture and funding decisions make them difficult to implement. Versioned models, inputs, and operating rules linked to recommendations enable reconstruction. Access controls and retention policies make preservation accountable rather than indefinite or unrestricted.

DEA-C01

A retailer's merchandising, inventory, and fulfillment teams use a shared analytics platform. A central data engineering team maintains every analytical dataset. Changes frequently break downstream reports, and freshness incidents remain unresolved while the central team waits for business teams to explain the data. The retailer wants to remove this operational bottleneck without moving data to separate platforms. Sensitive-data controls must remain consistent across the company, and routine dataset releases must not require central approval. Which operating model best meets these requirements?

Show answerCORRECT ANSWER

Give each business team responsibility for its analytical data products, including quality targets, freshness commitments, and compatible schema changes. Provide self-service platform templates with automated enterprise controls, and have domain representatives and security staff jointly maintain governance standards.

This applies domain ownership, data as a product, self-service infrastructure, and federated computational governance. Business teams become accountable for product reliability and changes, while shared automation enforces mandatory controls without central approval of every release. Separate physical platforms are not required.

AIP-C01

A company is standardizing governance for foundation models that shortlist applicants for technical apprenticeships across its business units. Teams fine-tune their models on resumes labeled with historical hire-or-reject decisions. The models closely reproduce those decisions.

An investigation finds that past hiring favored employee referrals because referred applicants received preferential interview access, not because they demonstrated stronger technical skills. Referral rates differ substantially across demographic groups. Legal counsel permits demographic attributes to be used in a restricted audit environment, but not as prediction inputs. Independently validated technical work samples are available for a representative sample of both previously hired and rejected applicants.

The governance committee requires shortlisting to reflect demonstrated, job-relevant qualifications rather than reproduce historical access barriers. Which organization-wide requirement should the committee establish before approving these training datasets?

Show answerCORRECT ANSWER

Require a centrally approved qualification rubric grounded in the validated work samples. Independently reassess representative hired and rejected applicants, audit label validity and coverage across demographic groups, and correct or exclude unsupported historical labels before approving datasets.

This requirement addresses the source of the disparity: historical hiring outcomes are not reliable measures of qualification. Independent, job-relevant assessment of both hired and rejected applicants provides a defensible basis for labels. A shared rubric, demographic auditing, and required remediation establish consistent organizational oversight.

Practice Management and governance in a full exam

Questions on Management and governance in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Management and governance

2 min read

Management and governance connects day-to-day cloud operations with organizational rules and accountability. Governance establishes decision rights, acceptable risk, mandatory controls, and evidence requirements. Management implements those decisions through provisioning, access administration, monitoring, change control, and remediation. For example, governance might require encryption for sensitive information, while management ensures that storage is configured correctly and investigates deviations.

In the cloud, resources can be created quickly through consoles, APIs, and deployment pipelines. Manual approval of every change rarely scales, so organizations commonly express standards as reusable infrastructure templates, permission boundaries, and automated checks. Preventive controls block prohibited actions, detective controls identify violations, and corrective controls restore an approved state. These controls complement one another: detecting an exposed resource is not the same as preventing exposure, and a detection rule does not necessarily perform remediation.

A practical governance model separates production, development, security, and logging responsibilities across accounts or equivalent administrative boundaries. Teams receive permissions appropriate to their roles, resources have identifiable owners, and policies define approved locations, required tags, backup expectations, and exception procedures. For example, a company handling regulated customer records might restrict deployments to approved Regions, centralize audit logs, and require documented approval before changing retention settings. Region restrictions alone do not establish data residency; engineers must also consider replication, backups, service behavior, and data transfers.

Compliance requires understanding the cloud shared responsibility model. AWS is responsible for security of its cloud infrastructure, while customers remain responsible for areas such as their data, access permissions, and workload configuration; the exact division depends on the service used. Provider certifications and reports can support an organization's assessment of inherited controls, but they do not automatically make a customer application compliant. A workload using a service covered by a provider's assessment must still meet its own applicable requirements.

Engineers should distinguish compliance evidence from operational evidence. AWS Artifact provides access to AWS compliance reports and certain agreements, while configuration records and activity logs help demonstrate how a customer's environment is controlled. SOC reports, ISO certifications, and PCI DSS documentation have different scopes and purposes. HIPAA-related workloads require applicable safeguards and an appropriate business associate agreement; using a HIPAA-eligible service alone is insufficient. Legal, security, and compliance teams should determine which obligations apply and which evidence is required.

The main trade-off is consistency versus flexibility. Broad restrictions can reduce risk but can also interrupt legitimate deployments or emergency recovery. Start with tested controls, documented ownership, time-limited exceptions, and a controlled emergency-access process. Centralized governance need not mean centralized execution: teams can operate independently within agreed boundaries. Finally, passing an automated check is not proof of complete compliance, and retaining logs is useful only when their coverage, protection, retention, and review meet the organization's requirements.

Learn Management and governance in lessons

9 short lessons on Management and governance in 5 certification courses.

and 3 more lessons

Open the lessons