Cisco 350-801 Exam Prep
Implementing Cisco Collaboration Core Technologies (CLCOR) (Page 35 )

• NIDS: Monitors network traffic for suspicious activity and network-based attacks targeting the application or its supporting services.
• HIPS: Protects an individual host by monitoring processes, files, and system activity. It can help secure the web server, but it is not focused specifically on the application’s network attack surface.
• SIEM: Aggregates and correlates logs; it does not directly prevent attacks.
• Honeypot: A decoy system, not the primary protection for a production web application.
• Certificate revocation list: Deals with certificate trust, not application exploitation.

• Compensating control: The server is end-of-life, so it may no longer receive security patches or support. Placing it on a restricted VLAN provides an alternative layer of protection by reducing who can access it and limiting its exposure.
• Technical control: VLAN segmentation and access control lists (ACLs) are technology-based mechanisms that enforce network access restrictions automatically.

• Managerial: Policies, procedures, and governance—not network configuration.
• Physical: Locks, guards, or barriers.
• Corrective: Restores systems after an incident.
• Detective: Identifies suspicious activity rather than restricting access.
• Deterrent: Discourages behavior but does not enforce access rules.

• Whether a user has a console password
• Password age and last password change
• Whether MFA is enabled
• Access key status
• Access key creation date and last-use information
• Access key age, which helps audit rotation

• IAM Access Analyzer identifies unintended access to resources; it does not report credential age or rotation.
• AWS Artifact provides AWS compliance documents and agreements, not details about your IAM users.
• AWS Audit Manager helps collect evidence for audits, but it is not the direct tool for viewing IAM credential rotation details.

• Modelo de embeddings de texto: trabalha principalmente com texto, não sendo adequado para imagens.
• Modelo generativo multimodal: pode interpretar ou gerar conteúdo de vários tipos, mas não é a opção específica para busca por similaridade.
• Modelo de geração de imagens: cria imagens a partir de entradas, não realiza busca multimodal.

• Replaces the verbal message — this describes non-verbal communication being used instead of words.
• Substitutes for verbal communication — similar; it means communicating without speech.
• Confuses the verbal message — this occurs when non-verbal signals contradict or obscure the spoken message.

• A — VARIANT "null" values are not the same as SQL NULL: Correct.

• B — Frequent, single-row DMLs: Incorrect.

• C — Validate data before loading into the target table: Correct.

• D — Use staging tables to manage MERGE statements: Correct.

• C — Custom buttons display at the top and bottom of a page: Correct. In Salesforce Classic, buttons can appear in the page’s button areas, including the top and bottom of record pages.
• D — Custom buttons are available for Person Accounts: Correct. Person Accounts use the Account object, so Account custom buttons can be available on Person Account layouts.
• E — Custom buttons can reference an external app: Correct. A URL custom button can launch or navigate to an external application or website.

• A: JavaScript custom buttons are a Salesforce Classic feature and are not supported in Lightning Experience. They do not enhance Lightning Experience.
• B: The User object does not generally support custom buttons in the same way standard business objects do.

• Password spraying: Tries a few common passwords against many accounts; no indication of repeated login attempts.
• Remote-access Trojan (RAT): Could install malware, but it does not explain how the attacker obtained the administrator’s credentials.
• Dictionary attack: Tries words or common passwords against an account; again, the scenario specifically highlights Telnet’s lack of encryption.

• Microsoft Teams: Connects to Teams-related data, but it isn’t the primary connector for the Power Apps data tables.
• Personal Analytics: Provides personal productivity insights, not application data.
• SQL Server database: Only applies if the app explicitly uses SQL Server as its data source.
• Dataflows: Used for preparing and centralizing data, not as the normal direct connection to a Power Apps app.

• A — Too infrequent: Formal strategies are often reviewed only every three to five years. This can make the organisation slow to respond to rapid changes in technology, competitors, regulation or customer needs.

• C — Relies on predicting the future: The approach assumes senior managers can make reasonably reliable forecasts and assumptions. In uncertain environments, these assumptions may quickly become invalid.

• E — Can restrict radical innovation: Formal planning tends to favour existing information, established objectives and incremental improvements. This may discourage experimental or highly innovative strategies that emerge from lower levels of the organisation.

• B concerns the difficulty of achieving competitive advantage through core competences when competing with focused specialists. It is not specifically a drawback of the formal top-down planning process.
• D is an activity organisations should undertake—continuous monitoring—not a drawback of the approach itself.

• Regional leads — Customer Community Plus

• Capacity planners — External Identity

• Customer Community does not provide the enhanced reporting/dashboard access required by regional leads.
• An Identity license is generally for internal Salesforce identity use and does not fit the external capacity-planning users as well as External Identity.

1. Start with the Customer table.
2. Use Merge Queries and select the Address table.
3. Match Customer[Address ID] to Address[Address ID].
4. Use a Left Outer join so every customer is retained.
5. Expand only City, State/Region, and Country.

• Append adds rows vertically; it is for stacking similarly structured tables.
• Group By summarizes rows and does not retrieve address columns.
• Transpose swaps rows and columns and is unrelated to table relationships.

• Portfolio definition cycle — establishes and maintains the portfolio strategy, objectives, and management framework.
• Portfolio delivery cycle — coordinates and monitors the delivery of change initiatives, ensuring the portfolio remains aligned with strategic objectives and delivers value.

• Practice — a structured area of portfolio management activity, such as risk management or resource management.
• Technique — a method used to perform an activity; it is not the term for portfolio delivery itself.
• Principle — a guiding rule for effective portfolio management.

• CSIRT: A Computer Security Incident Response Team that handles and coordinates incident response.
• CVSS: A scoring system used to rate the severity of vulnerabilities.
• SOAR: Security Orchestration, Automation, and Response technology used to automate security workflows.

• 16 VMs: one failure loses 25 GB and 10 cores—only 6.25% of memory.
• 8 VMs: one failure loses 12.5% of memory.
• 4 VMs: one failure loses 25%.
• 1 VM: one failure loses the entire application environment.

• Install unauthorized or unapproved applications
• Access system areas normally restricted
• Add features unavailable in the default software
• Modify the device’s operating system

• SQL injection (SQLi): Attacks databases by inserting malicious SQL commands.
• Cross-site scripting (XSS): Injects malicious scripts into web pages viewed by users.
• Sideloading: Installs an application from outside the official app store, but it does not necessarily remove the phone’s operating-system restrictions.

• Accept: Acknowledging the risk without taking additional action.
• Mitigate: Reducing the likelihood or impact through controls, such as patching or employee training.
• Avoid: Eliminating the activity or condition that creates the risk.
• Transfer: Shifting the consequences—usually financial—to another party, such as an insurer.

• Accept: Acknowledging the risk without taking additional action.
• Transfer: Shifting the risk’s impact to a third party, such as through insurance or outsourcing.
• Mitigate: Reducing the likelihood or impact of the risk through security controls.
• Avoid: Eliminating the activity or process that creates the risk.

1. Determine which host was infected first—the originating host.
2. Decide whether each other host is clean or infected based on communication and event logs.

• Compare timestamps and find the earliest suspicious event.
• Look for the host that initiated the malicious connection, file transfer, exploit, or command—not merely a host that later received traffic.
• Follow the timeline through the firewall:

• A host is likely infected if it both receives suspicious activity and then initiates related malicious traffic.
• A host may be clean if the firewall blocked the connection and there is no evidence of execution or follow-on communication.

sql 
CREATE PROCEDURE dbo.usp_CreateOrder 
AS 
BEGIN 
    SET NOCOUNT ON; 
    SET XACT_ABORT ON; 


    BEGIN TRY 
        BEGIN TRANSACTION; 


        INSERT INTO dbo.Orders (/ columns /) 
        VALUES (/ values /); 


        SET @OrderID = SCOPE_IDENTITY(); 


        COMMIT TRANSACTION; 
    END TRY 
    BEGIN CATCH 
        IF @@TRANCOUNT > 0 
            ROLLBACK TRANSACTION; 


        THROW; 
    END CATCH; 
END;

• BEGIN TRY contains the transactional work.
• SCOPE_IDENTITY() retrieves the identity generated by the INSERT; it belongs after the insert, not as the error-handling logic.
• COMMIT runs only if all statements succeed.
• BEGIN CATCH handles failures.
• IF @@TRANCOUNT > 0 prevents attempting a rollback when no transaction is active.
• ROLLBACK undoes partial changes.
• THROW re-raises the original error with consistent details for the application.
• SET XACT_ABORT ON ensures many run-time errors automatically terminate and roll back the transaction.

• Customer: Dual
• Date: Dual
• Sales: DirectQuery
• SalesAggregate: Import

• Sales – DirectQuery: Near-real-time data should not rely on an imported cache. DirectQuery sends queries to the source when visuals are loaded, allowing recent sales data to appear.
• SalesAggregate – Import: A weekly refresh is sufficient, and imported data generally gives faster visual performance because it is stored in Power BI’s in-memory cache.
• Customer and Date – Dual: These are dimension tables used with both the DirectQuery Sales table and the imported SalesAggregate table. Dual allows Power BI to use cached data when possible, while still behaving appropriately in queries involving DirectQuery data. This can improve performance and reduce unnecessary limited relationships.

• Encryption to preserve confidentiality
• Integrity protection to detect alteration
• Authentication of the server through certificates

• SHA-256: A hashing algorithm; it does not encrypt data for transmission.
• SSL 3.0: Obsolete and insecure. It should not be used.
• AES-256: A strong encryption algorithm, but by itself it does not provide the complete secure communication protocol needed for data in transit.

• C — “when the query finishes”

• D — “when the query began”

• Issuer: Identifies the party issuing a SAML message, commonly the IdP in the SAML assertion. It is not the Salesforce setting used to distinguish Salesforce from other service providers.
• Identity Provider Login URL: Specifies where Salesforce sends users for authentication; it does not identify Salesforce.
• SAML Identity Location: Specifies where the user identity is found in the SAML assertion, such as the subject or an attribute.

• SQL injection
• Cross-site scripting (XSS)
• Malicious or malformed web requests
• Some application-layer abuse

• Layer 4 firewall: Filters based mainly on IP addresses, ports, and connections; it lacks detailed web-request inspection.
• NGFW: Provides broader network security, but a WAF is more specialized for protecting web applications.
• UTM: Combines multiple security functions, but it is not necessarily optimized for web-application protection.

• CCTV system — Detective control: Cameras monitor and record activity, helping identify or investigate security incidents after—or while—they occur.
• Signs about being filmed — Deterrent control: The signs discourage people from attempting unauthorized or criminal activity because they know surveillance is present.

• Preventive: Stops an incident from occurring, such as a lock or access-control system.
• Corrective: Restores systems after an incident.
• Directive: Instructs people to behave in a certain way, such as a security policy.
• Compensating: Provides an alternative control when the preferred control cannot be implemented.

• 10 TB with maximum I/O performance: Use EC2 instance store. It provides very high-throughput, low-latency local storage suitable for temporary video-processing data. The application must tolerate data loss because instance store is ephemeral.
• 300 TB of highly durable media: Use Amazon S3, which is designed for highly durable object storage and can scale to this size.
• 900 TB of inactive archival media: Use S3 Glacier, which provides lower-cost storage for data that is rarely accessed.

• A: Amazon EBS offers high performance but is not the best fit for the question’s “maximum possible I/O” requirement compared with local instance store.
• B: Amazon EFS is durable and shared, but is generally more expensive and less suitable for very large archival storage.
• C: Uses EC2 instance store for performance, but incorrectly uses EFS for the 300-TB durable tier and S3 rather than Glacier for archival data.

• Product Owner: May attend, but is not required unless also working as a Developer.
• Scrum Master: May attend to help facilitate or coach, but is not required.
• Developers: Must participate because the event is specifically for them.

• IaaS: You manage the virtual machine’s operating system, configuration, applications, and data. Azure manages the physical infrastructure and virtualization platform.
• PaaS: You deploy applications without managing the underlying operating system or servers.
• SaaS: You consume a complete application managed by the provider, such as Microsoft 365.

• Generates a syslog message
• Shuts down the PoE port
• Places the port into error-disabled (err-disabled) state
• Frees the power allocation

• A device starting to draw power does not necessarily generate a syslog message.
• Monitoring does not pause data traffic while checking power.
• Drawing less than the configured minimum does not automatically mean the device has failed and should be disconnected.

• A. Modify CommunitiesSelfRegController

• C. Configure Communities registration to use a custom Visualforce page

• B. Modify the self-registration trigger — There is no standard “self-registration trigger” intended for this configuration. The registration logic is handled by the Visualforce controller.
• D. Configure a custom Apex controller — The standard approach is to modify the provided CommunitiesSelfRegController, rather than simply selecting a separate controller configuration.

1. Define Power Platform DLP policies

1. Add custom prompt modifications

1. Conduct adversarial testing

sql 
GRANT ALTER ON SCHEMA::schemaA TO User1;

• TRUNCATE TABLE is a DDL operation, not a normal DELETE.
• Having DELETE permission on a table is not sufficient to truncate it.
• The minimum relevant permission is ALTER on the table.
• Granting ALTER on SCHEMA::schemaA allows the user to truncate tables within schemaA.
• It does not grant equivalent permissions on schemaB or schemaC, satisfying least privilege.

Flat organisation

• Few levels of management
• A wide span of control—managers supervise many employees
• Shorter communication channels
• More employee autonomy and quicker decisions
• Fewer formal promotion levels

Tall organisation

• Many levels of management
• A narrow span of control—managers supervise relatively few employees
• A clear hierarchy and reporting structure
• More formal supervision and communication channels
• More obvious promotion and career stages

• Create and manage approved IT services as products
• Control which users can deploy those products
• Apply governance, permissions, and constraints
• Use and manage infrastructure-as-code templates, such as AWS CloudFormation templates

• AWS Resource Explorer: Helps find and browse AWS resources; it does not govern IaC deployments.
• AWS Organizations: Manages accounts, consolidated billing, and organization-wide policies.
• AWS Systems Manager: Provides operational management, such as patching, automation, and parameter storage, but it is not primarily used to catalog and govern IaC-based service deployments.

• Drops packets when traffic exceeds a certain bitrate: This describes traffic policing, not shaping.
• Fragments large packets and queues them: Shaping does not fragment packets as its primary congestion-control action.
• Drops packets randomly from lower-priority queues: Packet dropping may occur if a shaping queue becomes full, but it is not the defining behavior.

• Shaping: buffers and delays excess traffic.
• Policing: drops or marks traffic that exceeds the configured rate.

• Continuous deployment: Automates software releases; it does not specifically test input handling.
• Static code analysis: Examines source or compiled code without executing it. It can find coding flaws but does not directly stress the application with malformed inputs.
• Manual peer review: Developers inspect code or design manually. Useful, but not the best practice specifically for testing how a live product handles invalid input.

• Valor maior: mais aderência às instruções e aos detalhes descritos.
• Valor menor: mais liberdade criativa e resultados potencialmente mais variados.
• Valor excessivamente alto: pode causar artefatos ou imagens menos naturais.

• Aumentar o número de passos de geração: pode melhorar qualidade e refinamento, mas não é o principal controle de especificidade do prompt.
• MASK_IMAGE_BLACK: relaciona-se ao uso de máscara em geração ou edição de imagens, não à especificidade textual.
• Prompt strength: é mais associado à força do prompt em processos como image-to-image; nesta questão, o parâmetro diretamente ligado à aderência textual é o CFG scale.

• Monitoring: Detects activity but does not remove the underlying risk.
• Patching: Useful for systems that must remain operational, but these desktops are unused.
• Isolating: Can be a temporary containment measure, but permanently removing unnecessary systems is more appropriate.

• Managerial: policies, standards, risk management, governance
• Operational: procedures carried out by people, such as training, incident response, and backups
• Technical: firewalls, encryption, access-control systems
• Physical: locks, guards, cameras

yaml 
clusterIP: None

• CronJob: Runs Jobs on a schedule and normally does not need stable networking.
• Deployment: Manages interchangeable, stateless replicas and usually uses a regular Service.
• DaemonSet: Runs a Pod on selected nodes but does not inherently require stable Pod identities.

• 800 devices ? a scalable, centralized solution is needed.
• Four hardware/vendor classes ? the tool must handle different drivers and images.
• Two user groups ? it should allow different configurations for each group.
• “Distribute custom images” ? an imaging/deployment tool is required, not just a file-copy utility.

• A. Tuning system software: This is a corrective action, not an analysis method. Tuning should be based on measured performance data.
• B. User dissatisfaction reports: Useful as an indicator, but subjective and insufficient for diagnosing the cause.
• D. Off-peak utilization and response time: This may hide problems occurring during peak periods. Performance analysis should cover representative or peak workloads.

• Multiple nodes: Data is replicated several times in the primary region.
• Separate geography: A copy is asynchronously replicated to a secondary Azure region.
• Readable secondary: RA-GRS provides read-only access to the secondary replica, even when the primary region is available.

• GRS: Replicates to another region but the secondary copy isn’t normally readable.
• ZRS: Replicates across availability zones in the same region, not a separate geographic region.
• LRS: Keeps replicas within a single datacenter or region and provides no geographic redundancy.

Question 3: AWS Storage Gateway File Gateway

• A: S3 bucket per user — S3 is object storage, not a traditional shared file system; mounting it requires extra tools and is less efficient.
• B: File Gateway — Provides a local file share using standard file protocols while storing files in Amazon S3. This preserves convenient local access and extends storage capacity.
• C: WorkSpaces and WorkDocs — Designed for virtual desktops and document collaboration, not large shared file storage.
• D: EC2 with EBS — EBS is attached to one EC2 instance and is not designed for direct multi-user file sharing.

• Digitally signing the software: Verifies authenticity and integrity. It does not hide how the software works.
• Limiting third-party libraries: May reduce dependencies and attack surface, but does not directly prevent reverse engineering.
• Using compile flags: Some compiler options can remove debugging information or optimize code, which may provide limited protection, but this is not the primary technique identified for preventing reverse engineering.

text 
interface GigabitEthernet0/0.10 
 encapsulation dot1Q 3

• .10 is the router’s local subinterface number.
• dot1Q 3 identifies the 802.1Q VLAN tag carried on the trunk.

text 
interface GigabitEthernet0/0.3 
 encapsulation dot1Q 3

text 
interface GigabitEthernet0/0.2 
 encapsulation dot1Q 2

1. Convert text and images into numerical embeddings.
2. Store or compare those embeddings.
3. Retrieve the most semantically similar items.

• Embedding model: Best for similarity search and retrieval.
• Generation model: Best for producing new text or other content from multimodal input.