Practice Exams:

Systems & Infrastructure

HashiCorp Terraform Associate 004: Terraform State Without Surprises

Terraform state is the mapping between configuration and the real infrastructure Terraform manages. It stores resource identities and attributes so Terraform can compare desired configuration with existing objects and determine what to change. That makes state operationally critical: if it is unavailable, corrupted, exposed, or edited carelessly, otherwise correct configuration can become difficult or dangerous to apply. Home/HashiCorp/HashiCorp Terraform Associate 004: Terraform State Without SurprisesHashiCorpPublished October 7, 2026On this pageUnderstand what state is doingPrefer remote state for team workflowsTreat locking as concurrency controlProtect state as sensitive operational dataUse state commands…

Read More

HashiCorp Terraform Associate 004: Terraform Provider Version Strategy

Terraform providers translate configuration into API operations against cloud platforms and other services. Because providers evolve independently from Terraform itself, version strategy is part of infrastructure change management. A configuration that worked yesterday can produce a different plan after an uncontrolled provider upgrade even when no .tf file changed. The current Terraform Associate 004 objectives include installing and versioning providers, provider requirements, and the dependency lock file. HashiCorp’s current documentation recommends declaring provider version constraints and committing the lock file so teams and automation use consistent provider selections. Those mechanisms…

Read More

HashiCorp Terraform Associate 004: Terraform Module Design Patterns

Terraform modules help teams turn recurring infrastructure decisions into reviewed, reusable configuration. A useful module is not simply a folder with resources: it establishes a stable interface, states assumptions, and limits the risk that a small change in one environment accidentally alters another. This matters when an organization uses Terraform across accounts, regions and teams. The current HashiCorp Terraform Associate (004) exam examines configuration, modules, state and safe workflows; practical design judgment makes those concepts stick. Home/HashiCorp/HashiCorp Terraform Associate 004: Terraform Module Design PatternsHashiCorpPublished October 7, 2026On this pageStart with…

Read More

HashiCorp Terraform Associate 004: Importing Infrastructure into Terraform

Terraform adoption often begins in an environment that already contains infrastructure. Import is the bridge between resources that exist in a provider and resources that Terraform should manage. The operation sounds simple—associate an existing object with a Terraform resource address—but the engineering work is really about bringing code, state, provider behavior, and the live object into a consistent model. Home/HashiCorp/HashiCorp Terraform Associate 004: Importing Infrastructure into TerraformHashiCorpPublished October 7, 2026On this pageInventory the resource before importing itWrite the destination resource address firstChoose CLI import or import blocks deliberatelyUse the first…

Read More

CompTIA XK0-006: systemd Troubleshooting for Linux Admins

When a Linux service fails under systemd, restarting it repeatedly is not troubleshooting. The useful questions are more specific: what state does systemd believe the unit is in, what process or dependency caused the transition, what configuration did the manager actually load, and what evidence exists in the journal for this boot? A disciplined workflow answers those questions before changing the machine. Home/CompTIA/CompTIA XK0-006: systemd Troubleshooting for Linux AdminsCompTIAPublished October 7, 2026On this pageStart with the unit state systemd actually seesRead the journal in the same failure windowInspect the unit…

Read More

CompTIA XK0-006: Linux Storage and LVM in Practice

Linux storage administration is easier when the layers are kept distinct. A physical disk or virtual block device is not the same thing as a partition, an LVM physical volume, a volume group, a logical volume, a filesystem, or a mount point. Each layer solves a different problem. Logical Volume Manager adds a flexible allocation layer between raw devices and filesystems, which makes it possible to group capacity, create logical devices, and resize storage more easily than with fixed partitions alone. Home/CompTIA/CompTIA XK0-006: Linux Storage and LVM in PracticeCompTIAPublished October…

Read More

CompTIA XK0-006: Linux Permissions Beyond chmod

Linux permissions are often taught as a nine-character string and an octal number, but real administration quickly moves beyond `chmod 755`. Effective access depends on ownership, primary and supplementary groups, directory execute semantics, the process umask, special permission bits, access control lists, and—on systems that use it—mandatory access control such as SELinux. Troubleshooting therefore requires asking not only “what are the mode bits?” but “which identity is the process actually using, which path components must it traverse, and which additional policy layers apply?” Home/CompTIA/CompTIA XK0-006: Linux Permissions Beyond chmodCompTIAPublished October…

Read More

CompTIA XK0-006: Linux Networking from ip to ss

Linux networking becomes much easier to troubleshoot when the administrator stops treating the network stack as one black box. The `ip` family of commands exposes interfaces, addresses, routes, and neighbors; `ss` exposes sockets and the processes using them. Together they answer the first questions that matter when a service cannot communicate: does the host have the expected interface and address, is there a route to the destination, can the kernel resolve the next hop, and is the application actually listening where the client expects it? Home/CompTIA/CompTIA XK0-006: Linux Networking from…

Read More

CompTIA XK0-006: Containers from a Linux Admin View

Containers are easier for a Linux administrator to understand when they are viewed as ordinary processes with carefully constructed isolation rather than as tiny virtual machines. A container image supplies a filesystem and metadata; the runtime starts one or more processes with namespaces, cgroups, capabilities, mounts, and networking that shape what those processes can see and do. That model connects container troubleshooting directly to familiar Linux skills: processes, users, filesystems, sockets, storage, logs, and resource limits. Home/CompTIA/CompTIA XK0-006: Containers from a Linux Admin ViewCompTIAPublished October 7, 2026On this pageSeparate images,…

Read More

CompTIA XK0-006: Bash Automation for Routine Admin Work

Bash is most valuable to a Linux administrator when it removes a repetitive operational step without hiding what the system is doing. A good script can turn a ten-command checklist into one repeatable action, collect the same evidence on every server, or enforce the same preconditions before a change. A bad script can multiply mistakes just as quickly. The difference is not whether the script is clever; it is whether inputs, failure behavior, privileges, logging, and rollback are explicit enough that another administrator can understand and trust it. Home/CompTIA/CompTIA XK0-006:…

Read More

VMware 2V0-17.25: vSAN Design for VCF

vSAN design in VMware Cloud Foundation begins with a simple correction to a common assumption: raw drive capacity is not the storage capacity the service can safely promise. Effective vSAN capacity depends on storage policy, failure tolerance, rebuild reserve, metadata, maintenance operations, compression and efficiency behavior, workload growth, and the physical failure domains of the hosts. In VCF, those storage decisions also affect lifecycle operations and workload-domain availability. Home/VMware/VMware 2V0-17.25: vSAN Design for VCFVMwarePublished October 7, 2026On this pageStart with the availability promiseDesign fault domains to match physical realitySize capacity…

Read More

VMware 2V0-17.25: VMware Cloud Foundation Architecture

VMware Cloud Foundation architecture is easiest to understand when it is treated as a private-cloud operating system rather than as a bundle of familiar VMware products. VCF 9 brings vSphere, vCenter, NSX, storage, operations, automation, identity, and lifecycle workflows into a coordinated platform. The individual components still matter, but the architectural value comes from how they are deployed, managed, and changed together. Home/VMware/VMware 2V0-17.25: VMware Cloud Foundation ArchitectureVMwarePublished October 7, 2026On this pageThe management domain anchors each VCF instanceWorkload domains create repeatable infrastructure unitsVCF Operations is the cross-instance control planeNSX…

Read More

VMware 2V0-17.25: VCF Workload Domain Design

VMware Cloud Foundation workload domains are not simply administrative folders for clusters. They are architectural boundaries that combine compute, vCenter management, networking, storage, lifecycle behavior, and operational responsibility. In VCF 9, a VCF instance contains a management domain and can contain additional virtual infrastructure workload domains, each with its own vCenter Server and an NSX relationship that supports the workloads placed there. The design decision is therefore less about naming domains and more about deciding where independence is valuable enough to justify another managed boundary. Home/VMware/VMware 2V0-17.25: VCF Workload Domain…

Read More

VMware 2V0-17.25: VCF Lifecycle Management

Lifecycle management is where a private-cloud design proves whether it can survive change. VMware Cloud Foundation integrates components that must remain compatible across vCenter, ESX, NSX, management services, operations tooling, automation, storage, and surrounding infrastructure. Updating one component independently can break that compatibility even when the update itself succeeds. VCF lifecycle workflows exist to coordinate those dependencies, run prechecks, stage software, and apply changes in an order the platform supports. Home/VMware/VMware 2V0-17.25: VCF Lifecycle ManagementVMwarePublished October 7, 2026On this pageStart with the supported upgrade pathTreat prechecks as engineering findings, not…

Read More

VMware 2V0-17.25: VCF Identity and Access Design

Identity and access design determines who can change the private cloud, which actions automation can perform, and how the organization recovers when its normal identity provider is unavailable. VMware Cloud Foundation brings multiple management surfaces together, so relying on separate local administrator accounts for every component creates inconsistent privilege, weak auditing, and difficult offboarding. Current VCF releases provide stronger fleet-level identity and single sign-on capabilities intended to reduce that fragmentation. Home/VMware/VMware 2V0-17.25: VCF Identity and Access DesignVMwarePublished October 7, 2026On this pageCentralize authentication while keeping authorization explicitUse the VCF identity…

Read More