FCSS_SDW_AR-7.4 Exam Dumps : FCSS - SD-WAN 7.4 Architect

When using the diagnose sys session list command, SD-WAN-specific session steering is indicated by the presence of the sdwan_service_id field in the session data. This identifier ties the session directly to a specific SD-WAN rule or service. As noted in the Fortinet documentation: “Sessions that are handled according to SD-WAN rules will include a service ID tag (sdwan_service_id) in their session listing. This allows administrators to correlate live sessions with SD-WAN policy matches for troubleshooting and visibility.” This is a crucial diagnostic tool, as it distinguishes between traffic managed by traditional routing and that explicitly controlled by SD-WAN steering logic, aiding in operational insight and troubleshooting.

When using FortiManager to configure SD-WAN members for multiple branches, it's crucial that you do not combine direct installation targets and metadata variables for the same SD-WAN member. From the FortiManager logs and the SD-WAN 7.4 documentation:

"If you define a metadata variable for an SD-WAN member interface, you must not also specify an explicit installation target for that member. This is because the metadata variable will be resolved to a specific interface during template application, making the static assignment redundant or conflicting. FortiManager will display a 'Copy Failed' or similar error if both are defined, requiring the administrator to remove the installation target and rely solely on the metadata-driven assignment."

This approach supports scalable deployments with device-specific mapping handled dynamically by FortiManager.

When importing a CSV for Zero Touch Provisioning (ZTP), FortiManager requires:

"Each device in the CSV must have a unique name, and a blueprint (template) must be associated with every device entry. The blueprint determines the configuration and role of the device in the SD-WAN topology. Missing either a name or blueprint results in an import failure, as these are required fields for automated device onboarding."

This ensures every device can be uniquely identified and provisioned according to policy.