A parks-and-rec access layer needs a new SVI VLAN and a static route declared in Terraform for IOS XE. Which construction matches the intended 5.3.b resources?
Select an answer to reveal the explanation.
Short Explanation
Name the VLAN and route as first-class resources—like labeled shelves in a warehouse—not a shell that types CLI. A null_resource SSH workaround is not the intended construction.
Full Explanation
DEVCOR 5.3.b construction expects typed Terraform resource blocks for the network parameters being configured. For a parks-and-rec access layer that needs a new SVI VLAN and a static route on IOS XE, declare those objects as Terraform resources—VLAN/interface and route—so plan can describe exact creates and state can track lifecycle. That is the intended resource-oriented construction, not an empty wrapper or a shell side effect.
A null_resource that SSHes ios_command strings as the primary design abandons typed resources, precise plans, and lifecycle management. A Puppet defined type that Terraform imports as its only resource type is not the official 5.3.b construction. An empty module with no resources because “plan alone configures the device” fails completely: plan without resources changes nothing on the switch.
Exam caveat: reusable modules may wrap resources for multiple civic sites, but the module must still contain real resources. Prefer provider resources over local-exec when the goal is idempotent network parameters.
Operational check: apply a root that only contains VLAN and route resources, run terraform state list, and verify typed addresses correspond to the objects present on the lab switch.