Question 130
At Granite SaaS, the site reliability team maintains multi-tenant Linux application instances under requirements for per-service isolation and reliable automated scaling. Following a proposed correction, the team checks: A remote synchronization job deletes legitimate target files because rsync --delete is run without checking source and destination paths. Which observed result BEST demonstrates that the correction works?
Explanation
Correct Answer
The dry-run deletion list matches the approved inventory and a test sync leaves unrelated target files intact. This measurable outcome verifies correction of: A remote synchronization job deletes legitimate target files because rsync --delete is run without checking source and destination paths. The associated technical action is: Run a controlled rsync dry-run and confirm the intended source directory semantics before allowing target deletions. The Granite SaaS review checks actual behavior rather than an untested change claim.
Incorrect Answers
An invalid trial reverts automatically and the corrected configuration retains remote SSH connectivity after confirmation. This evidence pertains to an unrelated remediation: Use netplan try with its timed rollback and validate the YAML routes before committing permanent network changes. The alternative issue is: A remote administrator applies an invalid Netplan route and loses access to the host during a direct netplan apply operation. The current Granite SaaS problem is: A remote synchronization job deletes legitimate target files because rsync --delete is run without checking source and destination paths. The decisive expected evidence is instead: The dry-run deletion list matches the approved inventory and a test sync leaves unrelated target files intact.
The capture shows whether the intended test packets arrive and the restored flow completes without a blanket firewall allow. This evidence pertains to an unrelated remediation: Capture a narrowly filtered tcpdump trace at the expected interface and correct the evidenced upstream routing or security control. The alternative issue is: A firewall investigation changes rules before verifying whether inbound packets even reach the server's network interface. The current Granite SaaS problem is: A remote synchronization job deletes legitimate target files because rsync --delete is run without checking source and destination paths. The decisive expected evidence is instead: The dry-run deletion list matches the approved inventory and a test sync leaves unrelated target files intact.
Two consecutive test runs produce distinct ordered log entries without erasing the first run's data. This evidence pertains to an unrelated remediation: Use append redirection for the log destination and retain explicit stderr handling where required. The alternative issue is: A script overwrites a daily log each time it runs because its redirection uses a single greater-than operator rather than append. The current Granite SaaS problem is: A remote synchronization job deletes legitimate target files because rsync --delete is run without checking source and destination paths. The decisive expected evidence is instead: The dry-run deletion list matches the approved inventory and a test sync leaves unrelated target files intact.