Free EX210 sample questions

Correct answer: aide --update; mv /var/lib/aide/aide.db.new.gz /var/lib/aide/aide.db.gz

To accept a legitimate change, the AIDE database must be updated. The `aide --update` command generates a new database file (`aide.db.new.gz`) that incorporates the current state of the filesystem. This new database must then replace the existing baseline database (`aide.db.gz`) to prevent the change from being flagged in future checks.

Correct answer: The logical datapath (switch) name and the microflow parameters

The `ovn-trace` command simulates packet processing within the OVN logical network. It requires the name of the logical datapath (usually the logical switch name) and the flow parameters (such as source MAC, destination MAC, IP addresses) to trace the pipeline execution. While port IDs can be helpful, the datapath context is essential.

Correct answer: hw:cpu_policy=dedicated

The `hw:cpu_policy=dedicated` extra spec tells the Nova scheduler and compute driver to pin the instance's vCPUs to specific physical CPU cores (pCPUs) on the host. This ensures exclusive access to those cores, eliminating contention and reducing latency for performance-sensitive workloads.

Correct answer: pcs node standby controller-0

The `pcs node standby controller-0` command tells the Pacemaker cluster manager to move all active resources off the specified node to other available nodes in the cluster. This is the correct, safe way to drain a node before maintenance. Stopping the cluster service directly might cause unexpected failover behavior or resource fencing.

Correct answer: ceph osd out 5; ceph osd crush remove osd.5; ceph auth del osd.5; ceph osd rm 5

This sequence completely cleans up the old OSD traces: 1) Marks it 'out' to trigger rebalancing (if not already done). 2) Removes it from the CRUSH map so data isn't routed there. 3) Deletes its authentication key. 4) Removes the OSD ID itself. This clean slate allows the new disk to be provisioned, potentially reusing ID 5 if specified during creation.

Correct answer: Domain-specific configuration using `keystone.conf` [identity] domain_config_dir

By enabling `domain_specific_drivers_enabled` and configuring `domain_config_dir`, you can create separate configuration files (e.g., `keystone.Engineering.conf`) for each domain. This allows you to define specific LDAP filters, user trees, and group mappings for each domain independently, ensuring that the Engineering domain only queries and authenticates users relevant to that department.