Knowledge Check - Governance, Identity, and Cost
Test your understanding of the key concepts from Module 2. Select the best answer for each question, then submit to see your results. You need to score at least 60% to pass.
FinCorp's development team needs the Administrator role so that it can experiment freely with new services. The risk office insists that no development engineer may ever reach the regulated payment workloads, and wants the audit evidence for those workloads kept apart. Which design should the architect recommend?
Administrators have access to all contracted resources and are exempt from group management, so a separate VDC cannot keep an Administrator out; only a contract boundary does, and it also separates the activity log and the invoice. Denying the group a grant works only for User accounts, which contradicts the requirement for the Administrator role. Cross Connect and Network Security Groups address network traffic, not administrative reach.
FinCorp federates DCD logins through its corporate OIDC identity provider. An engineer with Edit rights on a production VDC and two API tokens leaves the company. The identity team has disabled the engineer's corporate identity. What else must the leaver runbook do?
IAM Federation is authentication only: users are pre-created in IONOS CLOUD, groups are not mapped from the identity provider, and after unlinking a user can still log in with native IONOS CLOUD credentials. The runbook must therefore act on the IONOS CLOUD user and its tokens, which keep working until deleted or expired. Resources the engineer created remain owned by them even after privileges change, so they need review too.
FinCorp must keep a tamper-evident record of user and resource activity for several years, for both of its contracts, and must be able to prove that no entry was altered. Which design meets the requirement?
The activity log is read-only but purges entries after 35 days and is retrieved per contract, so long-term evidence needs an export that runs inside that window and aggregates the contracts. Object Lock can be enabled only at bucket creation, and Compliance mode cannot be shortened by the owner or by IONOS CLOUD, which is what makes the archive tamper-evident; retention beyond 365 days requires the API. Governance mode allows privileged overrides, and the Logging Service is a search plane, not an immutable archive.
FinCorp's production estate runs at least 48 dedicated cores every hour of the year and peaks at 100 cores during month-end processing. The finance team wants to minimise compute cost without risking paying for capacity it does not use. Which commitment should the architect recommend?
A plan bills its full quantity whether used or not and cannot be modified or cancelled after purchase, so committing above the floor buys idle capacity, and an average cannot be adjusted later. Usage above the plan is billed at the standard pay-as-you-go rate, not a premium, so the peak belongs there. Stacked plans let the commitment grow in layers. Moving to vCPU Servers changes the contention model of a regulated tier, which is a design decision, not a commitment strategy.
A FinCorp team runs a small transactional database on a 40 GB Performance Block Storage volume and reports poor I/O performance. To save money, a colleague proposes moving the data to Essential, the cheapest class. What should the architect recommend?
Balanced and Performance volumes deliver IOPS in proportion to their size, and volumes of at least 100 GB are recommended to get the full benefit of the SSDs, so the volume is too small rather than the class too expensive. Essential suits backups and cold data, and its static 1,100 IOPS are below what a 40 GB Performance volume already delivers. IOPS are free of charge, so the premise of the second-volume option is false. Object Storage is an archive and dataset store, not a block device for a transactional database.