F5 F5CAB1 問題集 練習問題・模擬試験｜日本語版＆英語版対応

Explanation: Comprehensive and Detailed Explanation (Paraphrased from F5 BIG-IP Administration Install, Initial Configuration, and Upgrade concepts) When performing a TMOS upgrade, F5 recommends validating the target software version to ensure that the release does not contain defects that may impact system behavior. The upgrade preparation process includes checking for known issues, validating compatibility, and reviewing advisory information for the intended version. Two primary F5 tools serve this purpose: B. F5 iHealth iHealth is a cloud-based diagnostic and analysis platform used to evaluate the operational state of a BIG-IP system. Administrators upload a QKView file to iHealth to receive an automated assessment of the system. As part of upgrade planning, iHealth provides: Version-specific issue analysis, comparing the system’s configuration and hardware against F5’s internal catalog of published issues. Upgrade advisories, identifying potential risks such as deprecated features, module compatibility concerns, or changes in behavior between TMOS versions. Checks against known defects, allowing administrators to determine whether the target TMOS version contains issues relevant to their deployment. This aligns with F5’s recommended upgrade workflow, where iHealth is used before upgrading to confirm system readiness and detect software-level concerns. D. F5 Bug Tracker The Bug Tracker is F5’s dedicated interface for reviewing software defects across TMOS releases. It enables administrators to: Search for known bugs by TMOS version, module, severity, or defect ID. Review the status of defects (open, resolved, fixed in later releases). Identify whether high-impact or security-related issues are associated with the target upgrade version. F5 documentation emphasizes reviewing known defects prior to installation of new software images, making the Bug Tracker a critical resource for upgrade validation. Why the other options are not correct A. F5 End User Diagnostics (EUD) EUD is used exclusively for hardware diagnostics (ports, memory, fans). It does not provide software- related issue verification and is not used for upgrade planning. C. F5 University This is a training platform, not an operational tool. It does not provide defect listings or upgrade-specific warnings. E. F5 Downloads Although it provides access to software images and release notes, it is not a tool for identifying known bugs. Release notes summarize general fixes and features, but systematic bug verification requires iHealth or the Bug Tracker

Explanation: Comprehensive and Detailed Explanation (Paraphrased from F5 BIG-IP Administration / Installation / Initial Configuration concepts) Within the BIG-IP Traffic Management Shell (tmsh), system configuration objects―including the management IP―are organized under the /sys hierarchy. The management IP address is a configurable property stored in the system configuration and can be viewed using the tmsh list command, which displays configuration objects and their currently assigned values. Why “list /sys management-ip” is correct The list command in tmsh is used to display configured system values, not runtime statistics. The object that holds the management IP settings on BIG-IP systems is located at: /sys management-ip Running the command: list /sys management-ip will reveal the settings for the management IP interface, including the address, netmask, and any associated attributes. This is the standard method used during system setup and verification to confirm the management IP configuration. This behavior aligns with BIG-IP administration procedures, where configuration information is retrieved using list, while operational data is retrieved using show. Why the other options are incorrect A. run /util bash ifconfig mgmt This command enters the Bash shell, then runs ifconfig to display the management interface. While this can show the management interface address, it is not a tmsh-native command, and the question specifically asks for a tmsh command. Administrators use tmsh directly for configuration display rather than leaving the shell. C. show /sys management-ip The show command displays statistics or operational data, not configuration values. The management-ip object does not maintain statistics; therefore show does not return the configuration details required. Only the list command reveals stored configuration data such as IP address and netmask.

Explanation: The HTTPD allow list controls which IP addresses or subnets may access the Configuration Utility (TMUI) on the BIG-IP system. The Administrator already has two subnets allowed and needs to add a single host IP to the existing list. The object /sys httpd allow supports actions such as add, delete, and replace-all-with. Because the goal is to add one more entry without removing the existing permitted subnets, the correct command is: modify /sys httpd allow add { 172.28.32.22 } This appends the new host to the existing list while preserving the previously configured networks. Why the other options are incorrect: Option A (replace-all-with) would overwrite the entire allow list, removing existing permitted subnets―unacceptable. Option B (delete) would remove the existing networks and not add the required host. Therefore, the correct administrative action is to add the jump host’s IP.