UiPath UiPath-ADAv1 Exam Prep
UiPath Automation Developer Associate v1 (Page 17 )

• Key difference: DirectQuery leaves data in the on-prem SQL Server and queries it live. That means every visual request can trigger online processing on the source, which can be slower and adds load on the on-prem system. In contrast, Import loads data into the Power BI data model, so visuals render from the in-memory engine (faster).

• Why that helps with the requirements:

• Why not A or B: Both rely on live data via DirectQuery, which contradicts the goal to minimize online processing and visuals performance.

• Why not D: It uses Import, but refreshing hourly adds unnecessary processing and complexity when daily refresh already satisfies currency needs.

• The requirement is a fully managed file server that natively supports Microsoft workloads and file systems and uses the SMB protocol. FSx for Windows File Server is built specifically for Windows workloads, provides native SMB file shares, and supports Windows permissions/Active Directory integration.
• Why the others don’t fit:

• Dynamics 365 Remote Assist — used for remote collaboration and mixed-reality scenarios.
• Dynamics 365 Finance — supports financial and operational management.
• Dynamics 365 Business Central — designed primarily for small and medium-sized businesses’ finance and operations.
• Dynamics 365 for Phones — provides mobile access to Dynamics 365 apps, including Sales, through the mobile Unified Interface.

• 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.

• Disable default accounts: Default or unused accounts may have predictable names or credentials and can be abused by attackers. They should be disabled, removed, or secured with strong credentials where necessary.
• Remove unnecessary services: Every running service can contain vulnerabilities or provide an entry point. Removing services the server does not need reduces exposure.

• Add the server to the asset inventory: Important for asset management, but it does not directly harden the system.
• Document default passwords: Default passwords should be changed or disabled—not recorded for continued use.
• Send logs to the SIEM: Supports monitoring and detection, rather than directly reducing the attack surface.
• Join the corporate domain: A deployment/configuration decision, not inherently a hardening measure.

• Le rôle n’a pas de clés propres. Des identifiants temporaires (via STS) sont émis lorsque quelqu’un ou quelque chose « assume » le rôle.
• La trust policy déclare qui peut assumer le rôle (par ex. une instance EC2, un utilisateur IAM, ou un service comme Lambda).
• Une fois attaché à une ressource (par exemple comme un instance profile sur une EC2), l’application peut appeler les services AWS avec les permissions du rôle.

• Respect du principe du moindre privilège: on accorde uniquement ce qui est nécessaire.
• Pas de stockages de clés sur les instances; les credentials se renouvellent automatiquement.

• Rôles pour EC2, rôles pour Lambda, accès cross-compte, etc.

• Entradas grandes, de até aproximadamente 1 GB.
• Processamentos demorados, que podem levar até cerca de 1 hora.
• O cliente envia a solicitação e consulta o resultado depois, sem precisar manter uma conexão aberta durante todo o processamento.

• Real-time inference: indicada para respostas imediatas, com entradas menores e processamento rápido.
• Serverless inference: adequada para cargas variáveis e solicitações menores; não é ideal para processamento longo e arquivos grandes.
• Batch transform: processa grandes volumes em lote, mas não atende à necessidade de respostas próximas do tempo real.

• The policy is confidential, and the requester is no longer authorized merely because they used to work for the organization.
• The security professional should not disclose it by email or display it on a device without authorization.
• Using official channels allows the organization’s owner or information custodian to verify:

kusto 
Event | where EventType == "error"

• == is the KQL equality operator.
• -eq is a PowerShell operator, not KQL.
• is is not the correct equality operator in this context.

text 
Event | where EventType –eq "error"

• Event | search "error" — valid, broad search.
• search in (Event) "error" — valid, broad search.
• Event | where EventType == "error" — valid, targeted filter.

• ?????? CPU
• ?????????????????
• ??????????????????????????
• ???????????? throughput
• ??????????????????????????????

• A ??????? system software ????????????????????????????????? ??????????????????????????????????
• B ?????????????????????????? ????????????????????????? ?????????????????????????????
• D ????????????????????????? ?????????????? ?????????????????????????????????????????

• Honeypots: Decoy systems or services designed to attract attackers. Legitimate users should not access them, so activity on a honeypot is a strong indicator of unauthorized activity. Security teams can also observe attacker behavior.

• DNS sinkhole: Redirects requests for known malicious domains to a controlled internal server or blocks them. If an infected workstation attempts to contact command-and-control infrastructure, the sinkhole records the request and helps identify the compromised device.

• Tokenization: Protects sensitive data by replacing it with tokens.
• CI/CD: Automates software development and deployment.
• Threat modeling: Identifies potential risks before or during system design.
• Data obfuscation: Makes data harder to understand, but does not detect intruders.

• A: True. You can change the size of a Virtual Warehouse after creation (via UI or ALTER WAREHOUSE).

• B: True. A warehouse can be resized while it’s running; the resize will take effect without needing to stop queries.

• C: True. A warehouse can be configured to suspend after a period of inactivity (AUTO_SUSPEND).

• D: True. A warehouse can be configured to auto-resume when new queries are submitted (AUTO_RESUME).

• The target API uses HTTPS, so Mule must validate the server’s TLS certificate.
• The TLS configuration is set to None, meaning no custom truststore is configured.
• Mule therefore uses the JRE’s default truststore to determine whether the target certificate is trusted.
• If the issuing CA certificate is in that truststore, the TLS handshake can succeed.
• If it is absent—or the certificate is otherwise invalid—the request fails with a TLS/handshake error.

• Short answer: The correct term is Anti-forensics (option D), not “Felony.”

• Why: The actions described—hiding files in slack space, changing file headers, placing suspicious files in executables, and altering metadata—are classic anti-forensics techniques. They’re used to hinder or obscure forensic analysis, not to label the act as a legal category.

• About the options:

• Note: The provided answer key lists B (Felony), which is misleading for this exam objective. The exam typically tests knowledge of forensics concepts, where anti-forensics is the correct category.

• Answer: D. Select an IdP

• Why: To reduce the number of credentials across multiple SaaS apps, implement a single sign-on approach via an Identity Provider. The first step is choosing the IdP; once selected, you can enable SAML (A) or OAuth as supported by apps. Password vaulting (C) is not a true SSO solution, and B is not the foundational step.

1. Create a new AMI or copy the existing AMI while specifying EBS encryption and an appropriate AWS KMS key.
2. This creates an encrypted AMI backed by encrypted EBS snapshots.
3. Copy the encrypted AMI to the destination Region, using a KMS key available there.
4. Launch the application stack from the encrypted AMI.

• B: AWS KMS does not encrypt an existing unencrypted AMI in place. You must create an encrypted copy.
• C: AWS Certificate Manager manages TLS certificates, not EBS or AMI encryption.
• D: Enabling encryption by default affects newly created EBS volumes and snapshots; it does not encrypt an existing unencrypted AMI during copying.

• Used for communication on the local link or LAN segment
• Automatically generated on IPv6-enabled interfaces
• Not routed by routers to other networks
• Commonly used by devices to communicate with their local IPv6 router
• Begins with FE80 through FEBF

• FC00::/7 — unique local unicast
• FE80::/10 — link-local unicast
• FF00::/8 — multicast
• 2000::/3 — global unicast

• Answer: False. Agents and managers CAN create knowledge articles from Community questions.

• Why: In ServiceNow, a Community question can be converted into a Knowledge article using the Create Knowledge (or Convert to Knowledge) action. This allows what customers asked to become a reusable article for others.

• How it works (high level):

• Permissions: This ability depends on having the right roles/permissions (e.g., agents or knowledge managers). If you don’t see the option, check your role assignments or the knowledge-management configuration.

• Quick take: If a question in Community is valuable for others, a trained agent can turn it into a Knowledge article, making it available for self-service.

Why

cmd 
PowerShell.exe -ExecutionPolicy Bypass -File C:\Scripts\ConfigureVM.ps1

Why the other options are less suitable

• GPO logon script: Runs only when a user logs on and may not run during initial VM provisioning.
• GPO startup script: Can work, but requires the VM to be joined to the domain and the policy to be applied. It is also normally evaluated at each startup.
• Place scripts in a VHD: Merely placing scripts on a disk does not cause them to execute.

• C — Schema.describeSObjects(new String[]{myObject})[0].fields.getMap()

• D — Schema.getGlobalDescribe().get(myObject).getDescribe().fields.getMap()

• A: sObjectType is not used this way, and fieldSet() is not the appropriate method for retrieving all fields.
• B: mySObject.myObject is not valid dynamic Apex syntax.

• A limited lifetime
• Permissions defined by an IAM role or policy
• The ability to access AWS APIs without using long-term IAM user credentials

• Amazon API Gateway — Builds and manages APIs; it does not generally issue AWS credentials for applications.
• IAM users — Usually use long-term credentials, which are less suitable for applications.
• IAM instance profiles — Provide temporary role credentials to applications running on EC2 instances, but are specifically tied to EC2. The broader requirement described is best met by AWS STS.

• DNS????????????????

• ???????????

• ????????????????

• Strongest encryption algorithms: Choose the strongest available encryption and integrity options, typically AES with the largest key size and a secure integrity algorithm.
• Encrypt all traffic: Select tunnel mode rather than transport mode. Tunnel mode encrypts the entire original IP packet, which is appropriate for a site-to-site VPN between branch networks.
• Secret-password authentication: Configure a pre-shared key (PSK) on both VPN concentrators. The key must match at both ends.

• Writing with Apache Spark, typically as Delta tables.
• Reading with Apache Spark for processing and analysis.
• Reading with T-SQL through the lakehouse’s automatically generated SQL analytics endpoint.
• Reading with KQL through Fabric’s query capabilities that can access lakehouse data.

• Eventhouse: Optimized for real-time and KQL workloads, but it is not the natural destination for Spark-based writes or general lakehouse storage.
• Datamart: Intended mainly for relational analytics and Power BI; it is not designed for Spark-based data ingestion.
• Warehouse: Primarily T-SQL-based and structured. It does not provide the same native Spark write experience or flexibility for semi-structured data.

• Source: on-premises SQL Server Database1
• Destination: Fabric Warehouse Warehouse1
• Connectivity: on-premises data gateway

• Dataflow Gen1: Primarily for Power Query transformations and isn’t the best Fabric-native choice for this copy operation.
• KQL queryset: Queries data; it does not orchestrate copying from SQL Server.
• Notebook: Could perform custom code-based movement, but it is unnecessary and less direct than a pipeline.

bash 
docker run -it microsoft/azure-cli:0.10.17

• docker run starts an Azure CLI container; it does not automatically connect to the AKS cluster.
• The command does not run kubectl apply.
• The container would need the appropriate Kubernetes tools and AKS credentials.
• The device or container must obtain cluster credentials, typically using an AKS credential command, before running Kubernetes commands.

bash 
az aks get-credentials --resource-group <resource-group> --name <aks-cluster> 
kubectl apply -f myapp.yaml

• Approval publish: Request approval from a manager of the knowledge base before moving the article into the publish state.
• Instant Publish: Immediately publishes a draft article without requiring an approval.
• Instant Retire: Immediately retires a published article without requiring an approval.
• Retire Knowledge: Moves a knowledge article to the retired state.

• These are the base knowledge workflows that control how articles move between states (Draft, Published, Retired) and whether approvals are required.
• The other options describe different lifecycle actions, but these four cover the standard publish/retire workflows in ServiceNow.

• Correct answer: S3 Versioning

• Why the other options aren’t suitable for this protection:

• Quick tip: For enhanced protection, enable Versioning (and consider related features like Object Lock for write-once scenarios in specific compliance cases).

• L2TP uses UDP port 1701 for the L2TP control channel.
• The destination port is 1701; the source port is a dynamically chosen ephemeral port on the client (not 1701).
• Therefore the statement that both source and destination ports are 1710 is incorrect (and 1710 is not the standard L2TP port).

• The destination port should be 1701, not 1710.
• The source port should be an ephemeral port chosen by the client, not 1701.

• Planning — identify the need, objectives, resources and feasibility.
• Analysis — determine user requirements and examine the existing system.
• Design — specify how the new system will work.
• Implementation — build, test, install and introduce the system.
• Maintenance/evaluation — monitor and improve the system after implementation.

• 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.

• Modelo de embeddings multimodal: transforma texto e imagens em vetores no mesmo espaço semântico. Isso permite comparar uma consulta textual com imagens, ou uma imagem com textos relacionados.
• Modelo generativo multimodal: interpreta diferentes modalidades e gera conteúdo, mas não é a escolha específica para indexação e busca vetorial.
• Modelo de geração de imagens: cria imagens, portanto é inadequado.
• Modelo de embeddings de texto: não atende consultas com imagens.

• BCP: Maintains essential business operations during and after disruption. It is broader than IT recovery, but the question focuses on restoring the destroyed data center.
• Communication plan: Defines how the organization communicates with staff, the public, and other stakeholders.
• IRP: Handles security incidents such as malware, unauthorized access, or data breaches—not physical disaster recovery.

• Basic: Self-help only; no technical support or design assessment.
• Standard: Technical support, but not the full proactive architectural guidance required here.
• Professional Direct: Provides proactive guidance and architecture-related assistance.
• Premier: Also supports this, but is a more expensive, enterprise-level option.

1. Modify the database subnet NACL inbound rules to allow traffic from the new web subnet’s CIDR block on the MySQL port (3306).
2. Modify the database subnet NACL outbound rules to allow return traffic to the new web subnet’s CIDR block on the required ephemeral port range.

• Mesh: WAPs communicate wirelessly with one another, often to extend coverage without wired connections. It does not specifically describe centralized WLC management.
• Point-to-point: Connects two specific devices or locations.
• Ad hoc: Wireless devices communicate directly with one another without an access point.

• Progress iteratively with feedback focuses on making improvements in manageable steps and learning from feedback.
• Optimize and automate focuses on maximizing value from resources and automating suitable activities.
• Start where you are focuses on assessing the current situation and reusing what already exists.

• Which Security policy matches
• Which NAT rule/translation is selected
• Which PBF rule applies
• Which route is used

text 
test security-policy-match ... 
test nat-policy-match ... 
test pbf-policy-match ... 
test routing fib-lookup ...

• A single Construction Job can use multiple Machinery records.
• A single Machinery record may be used on multiple Construction Jobs.
• This is a many-to-many relationship, which Salesforce models using a junction object.
• The junction object can contain fields such as:

• Master-detail to Machinery
• Master-detail to Construction Job
• Date and cost fields

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.

• View/inspect configuration: Possible.
• Modify the installed application or its S-Controls: Typically restricted in a test-drive org.

• VPC: A logically isolated virtual network in a cloud environment; it describes networking, not shared application access.
• NFV: Replaces dedicated network appliances with virtualized network functions.
• SaaS: A cloud service model in which users consume an application without managing its infrastructure. It could describe how the application is delivered, but the question emphasizes serving multiple user groups, which points to multitenancy.

• 2000::/3 — Global unicast, used for publicly routable IPv6 addresses.
• FC00::/7 — Unique local, used for private internal addressing.
• FE80::/10 — Link-local, used only on the local network segment and not routed between subnets.

• Alice is co-resident on the same physical host and exploits shared hardware (the processor cache) to infer secrets. This is the classic definition of a side-channel attack—information leakage through implementation details (like timing or cache behavior) rather than by breaking a protocol or injecting code.

• Observing cache timing or access patterns to deduce cryptographic keys or plaintext data from the victim VM.

• Man-in-the-cloud attack: targets cloud trust/auth, not local hardware sharing.
• SQL injection: exploits input to run SQL commands, not a VM/caching vector.
• Service hijacking: takes control of a service, not about covert data leakage via shared hardware.

• Notice phrases like “shared hardware resources,” “co-resident,” or “cache”—these indicate a side-channel vector.

• Customers access the portal without needing a full Dynamics 365 license.
• They submit case information through portal forms.
• The submitted data is stored in Dataverse tables, such as the Case table.
• Security is controlled using web roles and table permissions, so customers can access only appropriate records.

• Dynamics 365 Connector — connects apps to Dynamics 365 data but is not the portal’s underlying data platform.
• Microsoft SharePoint — useful for documents and collaboration, not the standard case-management data source for portals.
• Microsoft Azure Storage — stores files or other data, but is not the native portal business-data platform.

• Admin access to the deployment pipeline (B) – lets the developers use the pipeline and deploy content.
• Contributor access to the Development and Test workspaces (E) – required to deploy items into those workspaces.
• Viewer access to the Production workspace (D) – lets them view Production content without allowing deployment or modification.

• Contributor access to Production (F), because that could allow changes or deployment there.
• Viewer access to Development/Test (C), because Viewer is insufficient for deployment.
• Build permission to Production semantic models (A), because building reports on a semantic model is not required merely to view Production items.

• Reusing features across different models and teams
• Consistent feature definitions
• Managing feature versions and metadata
• Using features for both training and inference

• SageMaker Data Wrangler: Prepares and transforms data; it is not primarily a shared feature repository.
• SageMaker Clarify: Helps detect bias and explain model predictions.
• SageMaker Model Cards: Documents models, including intended use, risks, and evaluation results.

• Port 515: LPD/LPR line-printer service
• Port 631: IPP — Internet Printing Protocol
• Port 9100: JetDirect/RAW printing, commonly used by network printers

• Linux machine: Linux could run these services, but the three printer-specific ports strongly indicate a printer.
• Router: Routers may use Telnet and HTTP, but normally would not expose ports 515, 631, and 9100 together.
• Windows machine: Windows can share printers, but this particular service combination is more characteristic of a network printer’s embedded operating system.

• Permanent table (E): Correct. A dropped permanent table can be restored with UNDROP TABLE during its Time Travel retention period. Permanent tables also have Fail-safe protection.
• Transient table: It can also generally be restored during its shorter Time Travel period, although it has no Fail-safe. Therefore, excluding it makes the question questionable.
• Temporary table: Usually cannot be recovered after it is dropped; its lifecycle is limited to the session.
• Materialized view (D): The answer key treats it as recoverable, but recovery behavior depends on the specific Snowflake object/version capabilities. It should not be confused with an ordinary view.