A programming team is deploying a new PHP module to be run on a Solaris 10 server with trusted extensions. The server is configured with three zones, a management zone, a customer zone, and a…

Question

Options

• AThe PHP module is written to transfer data from the customer zone to the management zone,
• BThe iptables configuration is not configured correctly to permit zone to zone communications
• CThe PHP module was installed in the management zone, but is trying to call a routine in the
• DThe ipfilters configuration is configured to disallow loopback traffic between the physical NICs

• A
  24% (7)
• B
  7% (2)
• C
  62% (18)
• D
  7% (2)

Explanation

Solaris 10 Trusted Extensions enforces strict zone isolation. In this architecture, only programs installed in the management zone are permitted to communicate data between zones. The PHP module handles online customer payments, which requires communication between the customer zone (where user-facing interactions occur) and the backend zone (where payment processing or databases reside). If the PHP module was installed in the management zone but is attempting to call routines or services located in the customer or backend zone without proper zone-crossing logic, the Trusted Extensions mandatory access controls would block that communication, causing the module to malfunction. Answer A is incorrect because zone-to-zone data transfer by the management zone is the intended design. Answer B is incorrect because Solaris 10 uses ipfilter, not iptables (Linux). Answer D is a plausible but less direct cause than the zone placement issue.

No community discussion yet for this question.