CompTIA Updated XK0-006 Exam Questions and Answers by malakai

This scenario represents a name resolution failure, which is a common troubleshooting case addressed in CompTIA Linux+ V8. The critical clues are the error messages returned by both curl and dig.

The curl error “Could not resolve host” indicates that the system is unable to translate the hostname into an IP address. This is confirmed by the dig output, which returns NXDOMAIN, meaning the DNS resolver cannot resolve the requested domain name. Importantly, the dig output shows that the query is reaching a DNS server (10.255.255.254), but the resolution fails, strongly pointing to a DNS client configuration issue.

Option C, reviewing and fixing the DNS client configuration file (such as /etc/resolv.conf or systemd-resolved settings), is the correct action. Linux+ V8 documentation highlights DNS misconfiguration as a primary cause of application connectivity issues. Incorrect nameserver entries, unreachable DNS servers, or misconfigured resolvers commonly produce NXDOMAIN responses.

The other options are incorrect. Firewall issues would result in connection timeouts, not DNS resolution failures. Requesting a new API endpoint is unnecessary without first confirming local DNS functionality. Internet connectivity issues would typically prevent any DNS communication, but here a DNS server is clearly being contacted.

Linux+ V8 stresses a layered troubleshooting approach: verify DNS resolution before investigating network ports or application logic. Therefore, the correct answer is C. Review and fix the DNS client configuration file.

File attribute management is an important system administration skill included in Linux+ V8. In this scenario, the administrator needs to ensure that a file cannot be modified or truncated, while still allowing data to be appended.

The correct solution is chattr +a file, which sets the append-only attribute on the file. When this attribute is enabled, the file’s existing contents cannot be altered or deleted, but new data can be appended to the end of the file. This is commonly used for protecting log files from tampering while still allowing normal logging operations.

The other options are incorrect. setenforce controls SELinux enforcement mode and does not affect file write behavior. setfacl modifies access control lists but does not enforce append-only semantics. chmod +t applies the sticky bit, which is primarily used on directories to prevent users from deleting files they do not own.

Linux+ V8 documentation explicitly references chattr and immutable or append-only attributes as mechanisms for protecting critical files from accidental or malicious modification.

Ansible architecture and core components are part of the Automation, Orchestration, and Scripting domain in CompTIA Linux+ V8. Among these components, the inventory plays a foundational role in defining the infrastructure Ansible manages.

An Ansible inventory is a file (or set of files) that contains a list of managed hosts and optionally organizes them into logical groups. These hosts can be defined by IP address, fully qualified domain name (FQDN), or hostname. Inventories may be written in INI, YAML, or dynamically generated formats. Grouping hosts allows administrators to apply configurations, roles, and tasks to multiple systems simultaneously.

Option B, Inventory, is correct because it explicitly defines which systems Ansible will target. Without an inventory, Ansible does not know where to execute tasks. Linux+ V8 documentation emphasizes inventories as the starting point for all Ansible operations.

The other options are incorrect. Facts are system variables automatically collected by Ansible about managed hosts, such as OS version or IP address. Playbooks define what actions to perform but rely on the inventory to know where to perform them. Collections are distribution units that package roles, modules, and plugins, not host definitions.

Therefore, the correct answer is B. Inventory.