From this link: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/4-x/rest-api-config/Cisco-APIC-REST-API-Configuration-Guide-401/Cisco-APIC-REST-API-Configuration-Guide-401_chapter_01101.html
Configure the tenant, VRF, and bridge domain. (Answer A)
The example is pretty much identical to the question.
Now, on step 3 of link:
Configure the node and interface.
This example configures VRF v1 on node 103 (the border leaf switch), with the node profile, nodep1, and router ID 11.11.11.103. It also configures interface eth1/3 as a routed interface (Layer 3 port), with IP address 12.12.12.1/24 and Layer 3 domain dom1.
Clearly, what the step said is configure node and INTERFACE. Basically Answer B is talking about this one.
Correct answer is A.
<fvRsCtx tnFvCtxName="v1"/>: This creates a relationship between the Bridge Domain "bd1" and the context "v1." It associates the Bridge Domain with the VRF context, allowing Layer 3 routing between different Bridge Domains.
<fvSubnet ip="44.44.44.1/24" scope="public"/>: This defines a subnet with the IP address "44.44.44.1/24" within the Bridge Domain "bd1." The "scope" attribute specifies the scope of the subnet, and in this case, it is set to "public."
<fvRsBDToOut tnL3extOutName="l3out1"/>: This creates a relationship between the Bridge Domain "bd1" and the external Layer 3 Out (L3Out) named "l3out1." L3Outs provide connectivity between the ACI fabric and external networks, such as the Internet or other data centers.
A is correct, look at the example in https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/4-x/rest-api-config/Cisco-APIC-REST-API-Configuration-Guide-401/Cisco-APIC-REST-API-Configuration-Guide-401_chapter_01101.html
A
The configuration is from the example in the Cisco document for "Configure the tenant, VRF, and bridge domain."
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/4-x/rest-api-config/Cisco-APIC-REST-API-Configuration-Guide-401/Cisco-APIC-REST-API-Configuration-Guide-401_chapter_01101.html
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/4-x/rest-api-config/Cisco-APIC-REST-API-Configuration-Guide-401/Cisco-APIC-REST-API-Configuration-Guide-401_chapter_01101.html
onfigure the tenant, VRF, and bridge domain.
This example configures tenant t1 with VRF v1 and bridge domain bd1. The tenant, VRF, and BD are not yet deployed.
Example:
<fvTenant name="t1">
<fvCtx name="v1"/>
<fvBD name="bd1">
<fvRsCtx tnFvCtxName="v1"/>
<fvSubnet ip="44.44.44.1/24" scope="public"/>
<fvRsBDToOut tnL3extOutName="l3out1"/>
</fvBD>/>
</fvTenant>
I doubt its A as can’t see and RD or RT, more likely to be B as would be adding ip to an exiting interface where the vrf is already configured. So I’d go with B
I think its A.
This is a script for a tenant, vrf and a bridge-domain.
Reference.
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/2-x/rest_cfg/2_1_x/b_Cisco_APIC_REST_API_Configuration_Guide/b_Cisco_APIC_REST_API_Configuration_Guide_chapter_01110.html
I guess is A
see: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/4-x/rest-api-config/Cisco-APIC-REST-API-Configuration-Guide-401/Cisco-APIC-REST-API-Configuration-Guide-401_chapter_01010.html
But it can be "B", as it is within the interface context
upvoted 2 times
...
...
This section is not available anymore. Please use the main Exam Page.350-501 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Seele
10 months, 1 week agoLandawap
10 months, 1 week agoLandawap
10 months, 1 week agoWorgen44
11 months, 3 weeks agoDUsoo
1 year, 2 months agothejag
1 year, 4 months agohk9042
2 years, 4 months agoelroy909
2 years, 5 months agorm868
2 years, 6 months agojefranca
2 years, 7 months agojefranca
2 years, 7 months ago