Practice Exams:

Governance & Compliance

Amazon AWS AIF-C01: Responsible AI Is a Product Requirement

Responsible AI should not appear at the end of a project as a policy document that nobody used to shape the product. Fairness, explainability, privacy, security, safety, controllability, robustness, and governance affect requirements, architecture, data choices, evaluation, user experience, monitoring, and release decisions. If those concerns are postponed until deployment, the expensive parts of the system may already be difficult to change. Home/Amazon/Amazon AWS AIF-C01: Responsible AI Is a Product RequirementAmazonPublished October 3, 2026On this pageStart by defining who can be harmed and howFairness needs use-case-specific evidenceExplainability should match the…

Read More

Microsoft SC-401: Retention vs. Records Management

Retention and records management are often discussed together because both control the lifecycle of information, but they solve different governance problems. Retention answers questions such as how long content must be kept and when it can be deleted. Records management adds a stronger question: which information must be treated as evidence of business activity and placed under additional controls? Microsoft Purview administrators working toward Microsoft SC-401 need to distinguish keeping information for a required period from declaring it a formal record. Retention answers how long content remains available or recoverable…

Read More

Microsoft MD-102: Intune Compliance vs. Configuration Policies

Intune compliance policies and configuration policies are often discussed together because both evaluate or influence device settings. They solve different operational problems. Configuration policies tell a managed device how it should be configured. Compliance policies evaluate whether the device meets conditions the organization requires and return a compliance state that can drive reporting, remediation, or access decisions. Home/Microsoft/Microsoft MD-102: Intune Compliance vs. Configuration PoliciesMicrosoftPublished October 3, 2026On this pageConfiguration policies establish desired device stateCompliance policies evaluate whether requirements are metAccess control is where compliance becomes consequentialTargeting determines who receives the…

Read More

Microsoft AB-900: 365 Agents Add a New Governance Layer

Microsoft 365 agents introduce more than another user interface for Copilot. An agent can package instructions, knowledge sources, access paths, and in some cases actions into a reusable experience that other people can discover and use. That makes agent administration a lifecycle and governance problem: who can create an agent, what information can it reach, who can use or share it, what actions can it take, and who is responsible when its purpose or data becomes outdated? Home/Microsoft/Microsoft AB-900: 365 Agents Add a New Governance LayerMicrosoftPublished October 3, 2026On this…

Read More

ServiceNow CIS-DF: Data Owners and Stewards

CMDB governance can look like a collection of technical controls: health scores, reconciliation rules, lifecycle policies, certification tasks, class definitions, dashboards, and remediation queues. Those mechanisms matter, but none of them can answer a basic business question on their own: who is accountable for deciding what this data should mean and whether it is good enough for the processes that depend on it? Without named people and decision rights, governance tools become another set of queues that administrators chase without authority to resolve the underlying issue. Home/ServiceNow/ServiceNow CIS-DF: Data Owners…

Read More

Microsoft AZ-305: Landing Zones: Governance That Scales

An Azure landing zone is not a folder structure with a few policies attached. It is an operating foundation for subscriptions, identity, network connectivity, governance, security, management, and platform services. Its value appears when the organization grows: new workloads can enter an environment with known boundaries and inherited controls instead of negotiating basic cloud rules from scratch every time. Home/Microsoft/Microsoft AZ-305: Landing Zones: Governance That ScalesMicrosoftPublished October 3, 2026On this pageStart with the operating model before drawing the hierarchyManagement groups are inheritance boundariesSubscriptions are scale and responsibility boundariesPolicy should automate…

Read More

PMI PMP: Why Project Governance Should Clarify Decisions

Project governance is easy to overbuild because meetings, templates, steering committees, and status packs are visible. Decision quality is harder to see. A project can have an impressive governance calendar and still move slowly because nobody knows who can approve a change, when an exception must be escalated, which measures actually define success, or how a disagreement moves from the delivery team to the sponsor. Good governance is not the volume of oversight. It is the clarity of the decision system around the work. Home/Project Management/PMI PMP: Why Project Governance…

Read More

Microsoft SC-300: Identity Governance Begins After Account Creation

Creating an identity is only the first moment in an access lifecycle. The harder questions arrive afterward. Which applications should the person use? What changes when the person moves to a new role? How should temporary project access expire? Who approves access to sensitive data? What happens to guest access when a partner relationship ends? Identity governance exists because valid access on day one can become inappropriate through ordinary organizational change. Home/Microsoft/Microsoft SC-300: Identity Governance Begins After Account CreationMicrosoftPublished October 3, 2026On this pageJoiner, mover, and leaver events are different…

Read More

Microsoft SC-300: Workload Identities Need Governance Too

Applications, automation, services, and pipelines need identities just as people do, but workload identities behave differently from human accounts. They do not attend security training, cannot respond to an MFA prompt, may depend on secrets or certificates, and are frequently created by technical teams outside a formal joiner-mover-leaver process. Those differences make them easy to overlook and dangerous to leave unmanaged. Home/Microsoft/Microsoft SC-300: Workload Identities Need Governance TooMicrosoftPublished October 3, 2026On this pageDistinguish app registrations, service principals, and managed identitiesPrefer credentialless or managed approaches where the platform supports themAPI permissions…

Read More

Google Professional Cloud Architect: Landing Zones Before Growth

A landing zone is the foundation that determines how new cloud projects inherit identity, network, security, billing, logging, and policy decisions. Its purpose is not to make every workload identical. It is to make safe, supportable defaults available before hundreds of teams create their own incompatible versions. Home/Cloud & Architecture/Google Professional Cloud Architect: Landing Zones Before GrowthCloud & ArchitecturePublished October 3, 2026On this pageResource hierarchy is an operating modelUse organization policy for preventive guardrailsIdentity design should minimize standing privilegeNetwork foundations should enable teams without erasing boundariesCentralize the evidence needed to…

Read More

Microsoft AI-300: Model Registries Are Governance Tools, Not Just Storage

Home/Microsoft/Microsoft AI-300: Model Registries Are Governance Tools, Not Just StorageMicrosoftPublished October 3, 2026On this pageA registered model needs an identity that survives individual runsVersioning is valuable only when versions are meaningfully differentLineage turns a model artifact into evidenceMetadata should describe operating constraints, not decorate the catalogA registry can separate reusable assets from workspace-specific resourcesEnvironment and dependency context belong beside the modelQuality gates should happen before promotion, not after deploymentAccess control protects the supply chain, not just the artifactArchiving and retirement are part of the lifecycle  A model registry is often…

Read More

Microsoft AI-300: Responsible AI Is an Operational Discipline

Home/Microsoft/Microsoft AI-300: Responsible AI Is an Operational DisciplineMicrosoftPublished October 3, 2026On this pagePrinciples become useful only when they are translated into controlsResponsible AI starts before model registrationEvidence needs versioning just as much as the model doesDeployment should preserve the option to stop or reverse harmProduction monitoring must include model behavior, not only service healthHuman review should be designed around uncertainty and consequenceGovernance should make exceptions visible instead of pretending they do not existResponsible AI is a lifecycle, not a release milestone  Responsible AI stops being a set of principles the…

Read More

Microsoft DP-700: OneLake Shortcuts and Hidden Coupling

OneLake shortcuts solve an appealing problem: make data stored somewhere else appear inside a Fabric item without first building another copy pipeline. A shortcut can point to data elsewhere in OneLake or in supported external storage, allowing teams to create a unified analytical view while leaving ownership and physical storage at the source. Home/Microsoft/Microsoft DP-700: OneLake Shortcuts and Hidden CouplingMicrosoftPublished October 3, 2026 On this page OneLake shortcuts still introduce dependencies Intersect shortcut and destination permissions Delegated credentials and hidden privilege Govern shortcut dependencies across domains Caching affects costs and…

Read More

Microsoft PL-300: Power BI Governance Without Killing Self-Service

Self-service analytics fails when every useful action requires a ticket, but governance fails when anyone can publish any definition of revenue, expose any data, or create a workspace with no owner. Power BI governance therefore has to solve a tension: make trusted analytics easy to create and reuse without turning the platform into an uncontrolled collection of models and reports. Home/Microsoft/Microsoft PL-300: Power BI Governance Without Killing Self-ServiceMicrosoftPublished October 3, 2026On this pageSeparate exploration from authoritative reportingWorkspace design should reflect ownership and lifecycleShared semantic models reduce conflicting business definitionsEndorsement should…

Read More

Amazon AWS AIP-C01: Data Governance for RAG Pipelines

Home/Data governance for rag pipelines that touch sensitive informationRetrieval Augmented Generation can turn an ordinary document repository into an interactive knowledge system. It can also turn a poorly governed repository into a faster path to sensitive information. Once documents are parsed, chunked, embedded, indexed, retrieved, logged, and evaluated, the data exists in more forms and more places than the original source alone.On this pageClassify data before RAG ingestionTreat chunks and embeddings as sensitiveProtect prompts and generated outputsManage data freshness and deletionCitations do not establish authorizationControl agent tools and actionsCross-cloud RAG…

Read More