350-401 Dumps Questions With Valid Answers

It checks the MAC address table every 600 seconds to see if the specified address has been learned.

Use Cisco AMP deployment with the Exploit Prevention engine enabled.

Explanation:
Ransomware are malicious software that locks up critical resources of the users. Ransomware uses well-established public/private key cryptography which leaves the only way of recovering the files being the payment of the ransom, or restoring files from backups.

Cisco Advanced Malware Protection (AMP) for Endpoints Malicious Activity Protection (MAP) engine defends your endpoints by monitoring the system and identifying processes that exhibit malicious activities when they execute and stops them from running. Because the MAP engine detects threats by observing the behavior of the process at run time, it can generically determine if a system is under attack by a new variant of ransomware or malware that may have eluded other security products and detection technology, such as legacy signature-based malware detection. The first release of the MAP engine targets identification, blocking, and quarantine of ransomware attacks on the endpoint.

Reference: https://www.cisco.com/c/dam/en/us/products/collateral/security/ampforendpoints/white-paper-c11-740980.pdf

ip http port 8888

Option B

Explanation:
Option B is the correct configuration to implement HSRP between two WAN routers with the given requirement. The configuration steps are as follows12:
Define the HSRP group number and the virtual IP address for the group using the standby <group> ip <address> command. In this case, the group number is 300 and the virtual IP address is 10.10.10.1: standby 300 ip 10.10.10.1.

Configure HSRP preemption and preemption delay using the standby <group> preempt [delay [minimum] <seconds>] command. Preemption allows a router with higher priority to take over the active role from a router with lower priority. Preemption delay is the time that a router waits before taking over the active role in the HSRP group. In this case, the preemption delay is 100 seconds, which means that R1 will wait for 100 seconds before preempting R2 after R1 regains operational status: standby 300 preempt delay minimum 100.

Configure the HSRP priority for the router using the standby <group> priority <value> command. The priority determines which router is the active router and which router is the standby router. The higher the priority, the more likely the router is to become the active router. In this case, R1 has a priority of 200 and R2 has a priority of 100, which means that R1 is the preferred active router and R2 is the standby router: standby 300 priority 200 on R1 and standby 300 priority 100 on R2.

Option A is incorrect because it does not configure HSRP preemption and preemption delay, which are required by the question. Without preemption, R2 will remain the active router even if R1 has a higher priority and regains operational status. Without preemption delay, R1 will attempt to preempt R2 immediately, which may cause routing instability12.

Option C is incorrect because it configures HSRP preemption delay with the reload keyword, which means that the delay period applies only to the first interface-up event after the router has reloaded. This does not meet the requirement of the question, which states that the delay period should apply to any interface-up event after R1 fails and then regains operational status12.

Option D is incorrect because it configures HSRP preemption delay with the sync keyword, which means that the delay period applies only to the first interface-up event after the router has reloaded, and only if such an event occurs within 360 seconds from reload. This does not meet the requirement of the question, which states that the delay period should apply to any interface-up event after R1 fails and then regains operational status, and without any time limit12. References: 1: Configuring HSRP, 2: HSRP Configuration Guide

PBKDF2, BCrypt, and SCrypt

Explanation: One of the best practices to secure REST APIs is using password hash.
Passwords must always be hashed to protect the system (or minimize the damage) even if it is compromised in some hacking attempts. There are many such hashing algorithms which can prove really effective for password security e.g. PBKDF2, bcrypt and scrypt algorithms.
Other ways to secure REST APIs are: Always use HTTPS, Never expose information on URLs (Usernames, passwords, session tokens, and API keys should not appear in the URL), Adding Timestamp in Request, Using OAuth, Input Parameter Validation.

Reference: https://restfulapi.net/security-essentials/