Oracle
1Z0-1067 · Question #31
You set up a bastion host in your VCN to only allow your IP address (140.19.2.140) to establish SSH connections to your Compute instances that are deployed private subnet. The Compute instances have…
The correct answer is C. All compute instances associated with NSG-050504 are also able to connect to the bastion host. As per security rules that allow ssh on port 22 and source will be NSG-050504, so any compute instance that attached to this NSG will able to access the bastion host as it includes in the same NSG
Implement OCI Tagging and Governance
Question
You set up a bastion host in your VCN to only allow your IP address (140.19.2.140) to establish SSH connections to your Compute instances that are deployed private subnet. The Compute instances have an attached Network Security Group with a Source Type: Network security Group (NSG) , Source NSG: - 050504. To secure the bastion host, you added the following ingress rules to its Network Security Group: However, after checking the bastion host logs, you discovered that there are IP addresses other than your own that can access your bastion host. What is the root cause of this issue?
Options
- AA netmask of /32 allows all IP address in the 140.19.2.0 network, other than your IP 110.19.2.140
- BThe port 22 provides unrestricted access to 140.19.2.140 and to other IP address
- CAll compute instances associated with NSG-050504 are also able to connect to the bastion host.
- DThe Security List allows access to all IP address which overrides the Network Security Group ingress
How the community answered
(48 responses)- A6% (3)
- B10% (5)
- C81% (39)
- D2% (1)
Explanation
As per security rules that allow ssh on port 22 and source will be NSG-050504, so any compute instance that attached to this NSG will able to access the bastion host as it includes in the same NSG
Topics
#bastion host#Network Security Group#NSG ingress rules#CIDR netmask
Community Discussion
No community discussion yet for this question.