1Z0-1072-25 Question 262
Single answerYou have deployed an Oracle Cloud Infrastructure File Storage Service (FSS) file system in a private subnet of your Virtual Cloud Network (VCN). Instances in Subnet A can mount and use the file system without issue. However, when you launch new compute instances in Subnet B, they cannot mount the same file system despite having the correct network route to the mount target. Which additional step is required to enable the Subnet B compute instances to access the FSS file system?
- A
Create a second mount target in Subnet B and associate it with the same file system.
- B
Update the file system export to include a rule allowing Subnet B� CIDR as a source.
- C
Assign a public IP to the compute instances in Subnet B and open SSH (port 22) to the mount target� IP.
- D
Attach a NAT Gateway for Subnet B to forward NFS traffic to the mount target.
Show answer and explanation
Correct answer: B
Explanation
To allow additional subnets to access the same File Storage Service file system, you must configure an export rule that includes the new subnet� CIDR as a valid source. This ensures that NFS traffic from the compute instances in that subnet is permitted. Refer to the Oracle Cloud Infrastructure File Storage documentation for detailed steps on creating and updating export rules to grant NFS access to various subnet CIDRs.
- A. Incorrect.
Option 1: Creating a new mount target in Subnet B is possible but not strictly required. A single mount target can serve multiple subnets, provided the export rules and security configurations allow traffic from those subnets.
- B. Correct.
Option 2 (Correct): You must define an export rule for each subnet or CIDR range that needs access. By updating the export configuration to explicitly allow Subnet B� CIDR, those instances can mount the file system. This is a standard OCI File Storage best practice.
- C. Incorrect.
Option 3: Simply assigning a public IP to the instances and opening SSH (port 22) does not address the need for NFS access. NFS uses specific ports (commonly 2049), and enabling SSH has no relevance to the required export rule change.
- D. Incorrect.
Option 4: NAT Gateways are not used for NFS traffic within a private VCN setting. NAT Gateways facilitate outgoing connections to the internet, which is not how internal NFS mounting works.