Best Quality F5 F5CAB1 Exam Questions ExamTorrent Realistic Practice Exams [2026]
Critical Information To BIG-IP Administration Install, Initial Configuration, and Upgrade Pass the First Time
F5 F5CAB1 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 12
The monitoring team reports that the SNMP server is unable to poll data from a BIG-IP device.
What information will help the BIG-IP Administrator determine whether the issue originates from the BIG-IP system?
- A. The "VLAN / Tunnel" setting must allow All Vlans.
- B. The "Port Lockdown" setting is preventing the SNMP server from polling data from the BIG-IP.
- C. The "Traffic Group" setting must use a floating Traffic Group.
- D. The configuration on the exhibit is correct and other options should be explored.
Answer: B
Explanation:
The exhibit shows aSelf IPwith:
* VLAN:Data
* Port Lockdown:Allow None
Impact of "Allow None" on SNMP
When a Self IP is configured with:
Port Lockdown: Allow None
the BIG-IP blocksallservices and ports except a few hardcoded HA communication ports.
This means:
* UDP/161 (SNMP)is blocked
* UDP/162 (SNMP traps)is blocked
* The SNMP server cannot poll or receive data from the BIG-IP through this Self IP SNMP relies on access through the Self IP if out-of-band (mgmt interface) is not used.
Thus, the issue is directly caused byPort Lockdown = Allow None, which prevents SNMP communication.
Why the other options are incorrect:
B). Traffic Group must use a floating Traffic Group
* SNMP polling doesnotrequire floating Self IPs.
* Floating groups apply to HA failover IPs, not SNMP functionality.
C). VLAN/Tunnel must allow All VLANs
* Self IPs are always bound to a VLAN; SNMP doesnotrequire All VLANs.
* As long as the Self IP belongs to a reachable VLAN, SNMP can work.
D). Configuration is correct
* It is not correct:Allow Noneblocks SNMP and is the problem.
NEW QUESTION # 13
A new logging solution is being implemented on the network. Policy requires keeping management traffic sent from the BIG-IPout of the management interface. After configuring the BIG-IP to forward messages to the new Syslog server, the BIG-IP Administrator notices that packets are being sentfrom a numbered data- plane Self IP.
What should the BIG-IP Administrator change to send the traffic out of thecorrect interface?
- A. Set the Management IP as the source address when configuring a Remote Syslog destination.
- B. Modify the port lockdown settings on the Self IP address to allow UDP port 514 traffic.
- C. Create a new Self IP in the same subnet as the management IP address using a route domain.
- D. Create a Management Route for the specific address/subnet of the syslog service via TMSH.
Answer: D
Explanation:
By default,management-plane trafficuses themanagement routing table, whiledata-plane trafficuses the TMM routing table.
Remote Syslog traffic ismanagement-planetrafficunlessa management route exists.
If noManagement Routematches the Syslog server's destination IP, the BIG-IP will instead:
* UseTMM routes, and
* Source the packets from aSelf IP
This is exactly what the administrator is observing.
To force Syslog traffic out the management port:
You must create aManagement Route, which is configured using:
tmsh create /sys management-route <name> gateway <ip> network <syslog subnet> This sends syslog traffic:
* Out of themanagement interface
* Using theManagement IPas the source
Thus,Option Bis correct.
Why the other options are incorrect:
A). Set the Management IP as the source address
* Source address selection is overridden by routing.
* Without a management route, traffic still goes out the data plane.
C). Create a new Self IP using a route domain
* Unnecessary and not related to management-plane routing.
* Syslog traffic should not rely on data-plane Self IPs.
D). Modify port lockdown on Self IP to allow UDP/514
* This would allow Syslog trafficintothe BIG-IP over a Self IP, not forceoutboundtraffic via management.
NEW QUESTION # 14
What will setting a Self IP to"Allow None"for Port Lockdown do?
- A. Block HA communications, causing the systems to report their peer as offline and go active-active.
- B. Block HA communications, causing the systems to report their peer as online ready.
- C. Default allow port 1026 access between peer devices and traffic processing across the network failover.
Answer: A
Explanation:
ThePort Lockdownfeature controls which services a Self-IP will respond to.
Setting a Self-IP toAllow Nonemeans:
* The Self-IP will not acceptanytraffic except the very limited, hard-coded HA ports such asTCP 4353 used for device trust and configuration sync.
* All other HA ports, including those needed for network failover and other HA mechanisms,are blocked.
When essential HA services cannot communicate, each device assumes its peer is down.
This results in:
* HA failover misbehavior
* Both devices thinking the other is offline
* Potentialactive-active condition, which is not intended and can cause traffic disruption Thus,Allow Nonecan break HA functionality unless the Self-IP is not used for HA links.
NEW QUESTION # 15
For security reasons, a BIG-IP Administrator needs to specify allowable IP ranges for access to the Configuration Utility (WebUI).
The exhibit shows the User Administration section of the Configuration Utility.
The administrator could not find any setting that explicitly restricts access to the Configuration Utility.
Which one of the following is a reason for that?
- A. The administrator needs to switch to the "Advanced" view mode in order to display the relevant setting
- B. The administrator must restrict access by IP address for SSH, which will implicitly restrict access to the Configuration Utility
- C. To avoid locking out the administrator, recent versions of BIG-IP no longer allow restricting administrator access to the Configuration Utility by source IP address
- D. Restricting access to the Configuration Utility can only be done from the Command Line Interface
Answer: D
Explanation:
The screenshot shown is from theUser Administrationsection of the BIG-IP GUI.
This section controls:
* Root and Admin passwords
* SSH Access
* SSH IP Allow settings
However,it does not contain any controls for restricting access to the WebUI (TMUI).
BIG-IP does not provide TMUI access restrictions from this part of the GUI.
Access to the web-based Configuration Utility is controlled by thehttpd allow list, configured through TMSH:
tmsh modify /sys httpd allow { <IP/subnet> }
This setting is not displayed in the User Administration panel, and in many BIG-IP versions, the httpd allow list isonly configurable from the CLI, not the GUI.
Therefore, the administrator cannot find the setting in the screen shown because:
* TMUI access restriction isnotlocated in this GUI section
* It must be configured usingtmshunder/sys httpd allow
This is whyOption Ais correct.
NEW QUESTION # 16
What are the two options for securing a BIG-IP's management interface?
(Choose two.)
- A. Limiting network access through the management interface to a trusted/secured network VLAN.
- B. Restrict administrative HTTPS and SSH access to specific IP addresses or IP ranges.
- C. Use the BIG-IP's Self-IP addresses for administrative access rather than the management interface.
- D. Block all management-interface administrative HTTPS and SSH service ports to prevent access.
Answer: A,B
Explanation:
Securing the BIG-IP management interface is a fundamental administrative responsibility. F5 best practices emphasize restricting who can reach the management port and ensuring that only authorized systems are allowed access.
A). Limiting management access to trusted network segments
F5 recommends placing the management interface on adedicated, isolated, and secured management network or VLAN, rather than exposing it to production or untrusted networks.
This reduces the attack surface by ensuring only trusted segments have visibility to administrative interfaces.
D). Restricting management access by IP or subnet
F5 BIG-IP uses the/sys httpd allowlist (for HTTPS) and configuration options insshd(for SSH) to control which IP addresses or subnets can access the device.
By specifying only known administrative IPs or ranges, unauthorized users cannot reach the login services.
Why the other options are incorrect
B). Blocking all management HTTPS/SSH ports
* This would prevent any administrative access and is not a viable security practice.
C). Using Self-IP addresses for administrative access
* F5 explicitly warns against using Self-IPs for management access unless strictly necessary.
* Self-IPs are exposed to the data plane and should not be used as the primary administrative interface.
NEW QUESTION # 17
An F5 BIG-IP Administrator is asked to report which modules areprovisionedon the BIG-IP.
In which two ways can this be done?
(Choose two.)
- A. Via TMSH withshow /sys provision
- B. Via the GUI atStatistics # Module Statistics # System
- C. Via the GUI atSystem # Resource Provisioning # Module Allocation
- D. Via TMSH withlist /sys provision
Answer: C,D
Explanation:
Provisioning determines:
* Which BIG-IP modules are enabled (LTM, ASM, APM, AFM, DNS, etc.)
* Their provisioning levels (None, Minimal, Nominal, Dedicated)
Two accurate ways to view provisioning settings are:
A). GUI - System # Resource Provisioning # Module Allocation
This is the primary GUI screen showing:
* All modules
* Their provisioning level
* System resource distribution impact
Administrators commonly use this page to confirm or change module provisioning.
D). TMSH - list /sys provision
This tmsh command displays each module and its provisioning level:
sys provision ltm { level nominal }
sys provision asm { level none }
This is the authoritative CLI method for checking module provisioning configurations.
Why the other options are incorrect:
B). show /sys provision
* Showsruntimeinformation butnot the actual configuration levels.
* list is the correct command for configuration details.
C). Statistics # Module Statistics
* Shows performance statistics, NOT provisioning status.
Therefore, the correct responses areAandD.
NEW QUESTION # 18
The monitoring team reports that the SNMP server is unable to poll data from a BIG-IP device.
What information will help the BIG-IP Administrator determine whether the issue originates from the BIG-IP system?
- A. The "VLAN / Tunnel" setting must allow All Vlans.
- B. The "Port Lockdown" setting is preventing the SNMP server from polling data from the BIG-IP.
- C. The "Traffic Group" setting must use a floating Traffic Group.
- D. The configuration on the exhibit is correct and other options should be explored.
Answer: B
Explanation:
The exhibit shows aSelf IPwith:
* VLAN:Data
* Port Lockdown:Allow None
Impact of "Allow None" on SNMP
When a Self IP is configured with:
Port Lockdown: Allow None
the BIG-IP blocksallservices and ports except a few hardcoded HA communication ports.
This means:
* UDP/161 (SNMP)is blocked
* UDP/162 (SNMP traps)is blocked
* The SNMP server cannot poll or receive data from the BIG-IP through this Self IP SNMP relies on access through the Self IP if out-of-band (mgmt interface) is not used.
Thus, the issue is directly caused byPort Lockdown = Allow None, which prevents SNMP communication.
Why the other options are incorrect:
B). Traffic Group must use a floating Traffic Group
* SNMP polling doesnotrequire floating Self IPs.
* Floating groups apply to HA failover IPs, not SNMP functionality.
C). VLAN/Tunnel must allow All VLANs
* Self IPs are always bound to a VLAN; SNMP doesnotrequire All VLANs.
* As long as the Self IP belongs to a reachable VLAN, SNMP can work.
D). Configuration is correct
* It is not correct:Allow Noneblocks SNMP and is the problem.
NEW QUESTION # 19
A BIG-IP Administrator discovers malicious brute-force attempts to access the BIG-IP device on the management interfacevia SSH.
The administrator needs to restrict SSH access to the management interface.
Where should this be accomplished?
- A. Network > Interfaces
- B. System > Configuration
- C. Network > Self IPs
- D. System > Platform
Answer: B
Explanation:
The BIG-IPmanagement interface (MGMT port)is controlled throughSystem settings, not through the Network menu.
SSH access on the management interface is configured here:
System # Configuration # Device # General # SSH Access / SSH IP Allow
This section allows the administrator to:
* Enable or disable SSH service
* Restrict SSH access to specific IP addresses or subnets
* Apply security policies to the management interface
Why the other options are incorrect:
A). Network > Interfaces
* Used for data-plane physical interface settings, not management plane SSH restrictions.
B). Network > Self IPs
* Controls in-band management or data-plane access, not the dedicated management port.
D). System > Platform
* Used for hostname, time zone, LCD contrast, hardware settings - not SSH security on the management port.
Therefore, restricting SSH access to themanagement interfacemust be done under:
#System # Configuration # Device # General
Which corresponds toOption C.
NEW QUESTION # 20
For an upgrade of a standalone BIG-IP, a maintenance window is available in which brief interruptions are allowed.
Actions with no impact can be done outside the maintenance window.
When should a license reactivation be performed?
- A. After the maintenance window.
- B. Before the maintenance window.
- C. During the maintenance window.
Answer: B
Explanation:
License reactivation updates the BIG-IP device's license file to ensure:
* TheService Check Dateis current
* The device is eligible to install the intended TMOS version
* Any module entitlement updates are received
Reactivationdoes not interrupt trafficand does not require a reboot, making it safe to performbeforethe maintenance window.
F5 best practices state:
* Performall non-impact tasks priorto the scheduled maintenance window
* Leave the window available for activities that require rebooting, such as the software installation itself Since license reactivation isnon-disruptive, it should be donebeforethe upgrade window starts.
NEW QUESTION # 21
When logged into thebash shellof a BIG-IP system, which of the following commands will display the management-ip address?
(Choose two.)
- A. ifconfig mgmt
- B. show mgmt ip
- C. list / sys management-ip
- D. tmsh list /sys management-ip
Answer: A,D
Explanation:
When logged into thebash shellof a BIG-IP system, there are two valid ways to view themanagement-ip address:
A). tmsh list /sys management-ip
* Even from the bash shell, the administrator can enter a tmsh command by typing:
* tmsh list /sys management-ip
* This displays:
* Management IP address
* Netmask
* Any configured management routes
* This is theofficial tmsh methodfor viewing the management-ip configuration.
C). ifconfig mgmt
* In the underlying Linux OS, the management interface maps to themgmtinterface.
* Running:
* ifconfig mgmt
displays:
* Assigned management IP
* Netmask
* Link-level status
* This is a valid Linux-level method used frequently for troubleshooting.
Why the other options are incorrect:
B). show mgmt ip
* Not a valid bash or tmsh command on BIG-IP.
D). list / sys management-ip
* Missing thetmshprefix.
* In bash, this will generate a syntax error.
* The correct form requires:
tmsh list /sys management-ip
NEW QUESTION # 22
How can the BIG-IP Administrator tell when anunlicensed modulehas been provisioned?
- A. When provisioning an unlicensed module, a warning will appear.
- B. AProvisioning Warningwill be displayed in the GUI in the upper left corner.
- C. A BIG-IP does not allow unlicensed modules to be provisioned.
Answer: B
Explanation:
The BIG-IP system has built-in licensing enforcement.
If an administrator provisions a module that the device isnot licensedto run, the system will still allow the provisioning action to occurinitially, but the system detects the mismatch and displays an alert.
What actually happens:
* The GUI places awarning bannerin theupper-left cornerlabeled something similar to:"Provisioning Warning"
* This appears immediately after provisioning a module that is not included in the active license.
* The system remains in an "inconsistent state" until the module is disabled again or the license is updated.
This is the visual cue BIG-IP uses to indicate that a module was provisioned without valid licensing.
Why the other options are incorrect:
A). "A BIG-IP does not allow unlicensed modules to be provisioned."
* Not true. BIG-IPdoesallow provisioning, but warns afterward.
B). "A warning will appear when provisioning an unlicensed module."
* The warning doesnotappear during the provisioning step itself.
* It appearsafter provisioning, in the main GUI, as a system banner.
NEW QUESTION # 23
A BIG-IP Administrator needs to install a HotFix on a standalone BIG-IP device, which hasHD1.1as the Active Boot Location.
The administrator has already re-activated the license and created a UCS archive.
In which sequence should the administrator perform the remaining steps?
- A. Install base Image in HD1.2, Install HotFix in HD1.2, Activate HD1.2
- B. Install HotFix in HD1.2, Install base Image in HD1.2, Activate HD1.2
- C. Install HotFix in HD1.1, Reboot the BIG-IP device, Install UCS Archive
- D. Activate HD1.2, Install base Image in HD1.2, Install HotFix in HD1.2
Answer: A
Explanation:
When installing a HotFix on a BIG-IP device, F5 best practices require:
* Installing the base TMOS image on a new, unused boot volume (HD1.2)
* This ensures the upgrade happens on a clean volume.
* The existing active boot location remains untouched for rollback.
* Installing the HotFix onto the SAME new boot volume (HD1.2)
* HotFixes must be applied on top of a base version.
* They cannot be installed on an empty volume.
* They must match the base image version.
* Activating the new boot volume (HD1.2)
* The system reboots into the updated software stack.
* Activation happensafterbase + HotFix installation is complete.
This sequence is exactly shown inOption C:
Install base Image in HD1.2
Install HotFix in HD1.2
Activate HD1.2
Why the other options are incorrect:
A). Install HotFix before base image
* Impossible.
* HotFix requires an installed base version first.
B). Installing HotFix on HD1.1 (active boot volume)
* Not recommended.
* Upgrading in-place removes rollback safety.
* HotFix cannot be applied cleanly without applying base image first.
D). Activate HD1.2 before installing anything
* You cannot activate an empty boot volume.
* Activation only occurs after the base + HotFix software is installed.
NEW QUESTION # 24
What command will allow the BIG-IP Administrator to view theconfigured management IPof a BIG-IP system?
(Choose one.)
- A. tmsh show sys management-ip
- B. tmsh list sys management-route
- C. tmsh list net self
- D. tmsh list sys management-ip
Answer: D
Explanation:
Comprehensive and Detailed Explanation (Paraphrased)
The BIG-IP stores the configured management IP address as asystem configuration objectunder the/sys hierarchy.
To display configured (persistent) values, BIG-IP uses thetmsh list command, not show.
Why tmsh list sys management-ip is correct
* The management IP configuration is defined under:
* /sys management-ip
* Running:
* tmsh list sys management-ip
displays:
* The configured management IP address
* Netmask
* Associated attributes
This command shows theactual configured management IP, which is what the question asks for.
Why the other options are incorrect
A). tmsh show sys management-ip
* The show command is used for runtime statistics and status.
* management-ip is a configuration object, not a statistics object.
C). tmsh list sys management-route
* Displays management routing information, not the management IP address itself.
D). tmsh list net self
* Displays Self IPs used on the data plane.
* Does not show the management interface IP.
NEW QUESTION # 25
The BIG-IP Administrator wants to manage the newly built F5 system through anin-band Self-IP.
The administrator has configured a VLAN and Self-IP and can ping the IP from their workstation, but cannot access the system viaSSHorHTTPS.
Whatport lockdownsettings should the BIG-IP Administrator use to allow management access on the Self-IP?
(Choose two.)
- A. The Self-IP port lockdown behavior could be adjusted toAllow Management
- B. The Self-IP port lockdown behavior could be adjusted toAllow Mgmt
- C. The Self-IP port lockdown behavior could be adjusted toAllow All
- D. The Self-IP port lockdown behavior could be adjusted toAllow Default
Answer: A,B
Explanation:
Self-IPs include a security feature calledPort Lockdown, which restricts which services respond on that Self- IP.
By default, Self-IPs block management access (SSH and HTTPS/TMUI), meaning an administrator cannot manage the device through in-band Self-IPs unless explicitly allowed.
Allow Mgmt / Allow Management
These settings enable only the management services required for administrative access, specifically:
* SSH (22)
* HTTPS/TMUI (443)
These options allow secure administration without opening unnecessary ports.
Why these are correct:
* They provide only the essential access for management.
* They follow F5 security best practices when using in-band admin access.
* They donotexpose all services, reducing the attack surface.
Why the other options are incorrect:
A). Allow Default
* This allows only a minimal set of system-required ports (e.g., failover, config sync), not SSH or HTTPS.
* Administrator access would still fail.
B). Allow All
* Opens all ports on the Self-IP, which isnot secure.
* Exposes services that should remain restricted.
Therefore,Allow Mgmt / Allow Managementare the correct choices.
NEW QUESTION # 26
Refer to the exhibit.
An organization has purchased a BIG-IP license that includes all available modules but has chosen to provision only the modules they require.
The exhibit displays the current resource allocation from theSystem # Resource Provisioningpage.
Based on the information provided, which F5 modules have been provisioned?
- A. TMM, DNS, APS
- B. DNS, APM
- C. LTM, APM
- D. LTM, DNS, APM
Answer: D
Explanation:
The exhibit shows theCurrent Resource Allocationfor:
* CPU
* Disk
* Memory
In particular, theMemory Allocationbar displays the modules that are currently provisioned.
Memory is the most reliable indicator because BIG-IP allocates memoryonlyto modules that are actively provisioned.
From the exhibit:
* MGMT(Management) - always present
* TMM(Traffic Management Microkernel) - indicatesLTM is provisioned
* GTM- this label indicates that theDNS moduleis provisioned (GTM = Global Traffic Manager, now called DNS)
* APM- explicitly shown, indicatingAccess Policy Manageris provisioned
Therefore, the provisioned modules are:
* LTM(implied by TMM allocation)
* DNS/GTM
* APM
This matchesOption C: LTM, DNS, APM.
NEW QUESTION # 27
Which port is an exception to the Port Lockdown function of Self-IPs if a device-group synchronization cluster is configured?
- A. TCP 4353
- B. TCP 443
- C. UDP 53
Answer: A
Explanation:
Self-IPs implement a security feature known asPort Lockdown, which limits which services are reachable on a Self-IP.
However, certain services required for BIG-IP device-to-device communication bypass Port Lockdown to ensure cluster and HA functionality.
TCP 4353
* TCP port4353is used byDevice Service Clustering (DSC)for:
* Device trust establishment
* Configuration synchronization
* Failover communication
* Because BIG-IP devices must always be able to communicate for HA functions to remain operational, port 4353 isexempt from Port Lockdown rules.
Why the other options are incorrect
A). TCP 443
* Not required for device trust or synchronization.
* HTTPS access is fully controlled by Port Lockdown.
C). UDP 53
* DNS traffic is not required for synchronization and has no exemption under Port Lockdown.
NEW QUESTION # 28
The Configuration Utility of a BIG-IP device is currently accessible via its management IP10.53.1.245from all VLANs.
The BIG-IP Administrator needs to restrict access so only hosts from the10.0.0.0/24subnet can access the Configuration Utility.
Which TMSH command accomplishes this?
- A. (tmos)# create /net acl MGMT.HTTP rule add { (permit tcp 10.0.0.0/24 10.53.1.245 http) (deny ip any any http) }
- B. (tmos)# create /net acl MGMT.HTTP rule add { (permit tcp 10.0.0.0 0.0.0.255 host 10.53.1.245 http) }
- C. (tmos)# modify /ltm httpd allow replace-all-with {10.0.0.0/24}
- D. (tmos)# modify /sys httpd allow replace-all-with {10.0.0.0/24}
Answer: D
Explanation:
BIG-IP controls access to the web-based Configuration Utility (TMUI) through the/sys httpd allowlist. This parameter specifies which client IPs or subnets may initiate HTTP/HTTPS connections to the management interface.
To restrict TMUI access toonlythe 10.0.0.0/24 subnet:
* The correct method is tomodify the HTTPD allow listso that it contains only this subnet.
* This requires replacing the entire current list with the new subnet using:
modify /sys httpd allow replace-all-with {10.0.0.0/24}
This ensures thatonlyclients within 10.0.0.0/24 can reach the Configuration Utility.
Why the other options are incorrect:
* Options A and Ccreate network ACL objects under /net acl, which apply to data-plane traffic, not management-plane TMUI access. TMUI access is not controlled by LTM ACLs but by the HTTPD allow directive.
* Option Bis incorrect syntax and references /ltm httpd, which is not the proper object; the correct hierarchy is /sys httpd.
Thus, only modifying the/sys httpd allowlist achieves the required restriction.
NEW QUESTION # 29
A BIG-IP Administrator needs to purchase new licenses for a BIG-IP appliance.
The administrator needs to know:
* Whether a module is licensed
* The memory requirement for that module
Where should the administrator view this information in theSystem menu?
- A. Resource Provisioning
- B. Configuration OVSDB
- C. Configuration Device
- D. Software Management
Answer: A
Explanation:
To understand:
* Which modules arelicensed
* Which modules areprovisioned
* Theresource requirements(CPU / RAM) of each module
The administrator uses:
System Resource Provisioning
This page displays:
* All modules present in the license
* Whether they are enabled or disabled
* Required memory to activate each module
* CPU and disk allocation information
* Provisioning level options (None / Minimal / Nominal / Dedicated)
This is the exact location where BIG-IP administrators evaluate module capacity before enabling or purchasing licensing upgrades.
Why the other options are incorrect:
A). Configuration OVSDB
* Used for network virtualization integrations, not licenses or modules.
B). Software Management
* Used for software image installation, not licensing.
C). Configuration Device
* Displays hostname, failover settings, device properties - not module resource requirements.
Thus, module licensing and memory requirement data are found underResource Provisioning.
NEW QUESTION # 30
Which one of the following is aport and protocol combination allowedby theAllow Defaultsetting for Port Lockdown?
- A. UDP 8443
- B. TCP 80
- C. TCP 443
Answer: C
Explanation:
Port Lockdown controls which ports and protocols aSelf IPwill respond to.
TheAllow Defaultsetting permits only a predefined set of BIG-IP internal and required service ports.
The Allow Default listincludes:
* TCP 443# HTTPS (Management/TMUI access via Self-IP)
* TCP 4353 # CMI (device sync)
* TCP/UDP ports related to HA communication
* Other essential internal F5 ports
Why TCP 443 is correct:
* It is one of the officially allowed ports underAllow Default.
* It enables HTTPS/TMUI access through a Self IP.
Why the other options are incorrect:
A). TCP 80 (HTTP)
* Not allowed under Allow Default
* HTTP via Self-IP is blocked unless placed under Allow Custom
B). UDP 8443
* Not an F5 default service
* Not part of the Allow Default ports
NEW QUESTION # 31
......
F5CAB1 EXAM DUMPS WITH GUARANTEED SUCCESS: https://passleader.examtorrent.com/F5CAB1-prep4sure-dumps.html
