Cisco 350-901 Exam Actual Questions
Developing Applications using Cisco Core Platforms and APIs (DEVCOR) (Page 14 )

• A separate scope using a /32 subnet: A /32 identifies one host, but it is not a practical DHCP scope for this purpose.
• A static IP within the DHCP range: This can cause an IP address conflict if DHCP assigns that address to another device.
• SLAAC: Used for automatic IPv6 address configuration, not for assigning a predictable IPv4 address through DHCP.

• Co to znaczy: transakcje zachowuja sie tak, jakby byly wykonywane jeden po drugim. Dzieki temu nie ma brudnych odczytów, niepowtarzalnych odczytów ani phantom reads.

• Implementacja: PostgreSQL uzywa SSI (Serializable Snapshot Isolation). W praktyce oznacza to, ze jesli wykryje konflikt miedzy transakcjami, jedna z nich zostanie zakonczona bledem “serialization failure” i trzeba ja ponowic.

• Zalózmy tabele orders(customer_id int, amount int).

• Transakcja T1:

• Transakcja T2, równoczesnie:

• T1 ponownie wykonuje to zapytanie:

• Enable the owner dimension
• Allocate a standard costing inventory model

• Owner dimension (B): This dimension Lets you track who owns the stock. By enabling the owner dimension, items can be configured as either company owned or consignment (vendor-owned) when you create or edit items. Without enabling this dimension, you can’t designate ownership per item.
• Standard costing inventory model (D): Selecting a costing model determines how item costs are calculated and posted. Standard costing provides a fixed cost per unit, which is commonly used for agreed pricing scenarios like consignment arrangements for easier accounting and valuation. It helps ensure consistent cost treatment across transactions for items that can be owned by the company or on consignment.

• Batch dimension (A): Batch tracking is unrelated to ownership and isn’t required to support company-owned vs. consignment configurations.
• Moving average costing (C): This is an alternative costing method. It’s not required to enable ownership config, and the exam’s expected choice focuses on standard costing for this scenario.

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

• The diagnostic output shows that the protocol is TCP (proto=6) and the session state is 2.
• In FortiGate’s session output, state=2 maps to SYN_SENT. This means the TCP SYN has been sent but the handshake hasn’t completed yet.
• Therefore, the session is not ESTABLISHED, FIN/ACK-related states, or other states; it’s in SYN_SENT.

• Answer: B — Improve employee training and awareness

• Why this is correct:

• Why the other options are less effective here:

• Quick practical note:

• Geo-redundant storage (GRS) replicates data to a secondary Azure region, but the secondary copy is normally unavailable for read access.
• RA-GRS provides geo-replication and read-only access to the secondary region, satisfying all requirements.
• Zone-redundant storage (ZRS) replicates data across availability zones within the same Azure region, not separate geographic regions.
• Locally redundant storage (LRS) keeps copies within a single datacenter or region and does not provide geographic resiliency.

• Answer: No.

• Why:

• If you need such an assessment while controlling costs, you’d generally pursue a paid MCS engagement or another option outside of the basic Premier entitlement.

• Create Power Query parameters for the Azure SQL server/database—or at least the database name.
• Use the parameter in the PBIX connection.
• Publish the same PBIX separately to the relevant development, test, and production workspaces.
• Set each dataset’s parameter value in the Power BI service so it points to the corresponding Azure SQL database.

• Development dataset ? DevelopmentDB
• Test dataset ? TestDB
• Production dataset ? ProductionDB

• The same PBIX is used for every lifecycle stage.
• Each stage consumes data from its matching database.
• Deployment pipelines are not required.
• Azure SQL is a cloud source, so gateway administration is generally avoided.
• Only the parameter value differs between published datasets, reducing maintenance.

• Correct answer: A
• What this is saying: You need to write a Transact-SQL query that uses REGEXP_SUBSTR to extract the ID from MessageText, and you should apply STRING_ESCAPE(MessageText, 'json') before calling REGEXP_SUBSTR.

• MessageText may contain JSON characters (quotes, backslashes, etc.). Escaping the JSON content first ensures the string you pass to the regex is safe and won’t confuse the regex engine.
• The pattern you apply with REGEXP_SUBSTR would then extract the first substring that matches your ID pattern from the (escaped) text.

• Example (conceptual):

• The question implies REGEXP_SUBSTR is available in this environment; some SQL Server and Fabric contexts don’t expose it natively in all versions. If REGEXP_SUBSTR isn’t available, you’d need an alternative approach (e.g., using built-in regex-like capabilities or CLR/UDFs).
• If you need the ID specifically from the first paragraph, you might first isolate the first paragraph and then apply REGEXP_SUBSTR, or compose a single pattern that anchors to the first paragraph.

• Risk tolerance describes the organization’s overall risk appetite, not the risks themselves.
• Risk transfer is a treatment option (e.g., insurance), not a documentation artifact.
• Risk analysis assesses likelihood and impact but doesn’t establish ownership or thresholds in a formal register.

• App Tag: a label that reflects the app’s enterprise readiness based on its Cloud Confidence Index (CCI) rating. It lets you quickly group apps (e.g., Poor, Average, Good) for policy decisions.
• App Score: a numeric value representing the CCI score. It provides a precise threshold you can use to enforce policies (e.g., block apps with Score below 50).

• You can create policies that block or restrict apps with a Poor App Tag or with an App Score under a chosen threshold.
• These two aspects let you filter cloud apps by CCI ratings during policy evaluation.

• CCL isn’t described as a real-time policy facet in this scenario.
• GDPR Readiness is a separate consideration and not the two CCI aspects used for real-time protection policy in this context.

cmd 
powershell.exe -ExecutionPolicy Bypass -File C:\Scripts\Configure-VM.ps1

• GPO logon script: Runs only when a user logs on, so configuration may be delayed and is user-dependent.
• GPO startup script: Can work, but requires the VMs to be domain-joined and introduces GPO dependency. It is not specifically tied to Windows deployment.
• Place scripts in a VHD: Merely makes the files available; it does not execute them.

• Transact-SQL (T-SQL) is used to query relational data in Azure SQL Database, not telemetry data from monitoring services.
• To analyze monitoring data from Azure SQL Database Intelligent Insights and Azure Application Insights, you should use the Kusto Query Language (KQL) in Azure Monitor Logs/Log Analytics (and in Application Insights Analytics).
• Using KQL lets you query telemetry tables such as requests, dependencies, pageViews, and customEvents (from App Insights) and any integrated monitoring data you’ve ingested into Log Analytics.

• Ensure Intelligent Insights and Application Insights data is available in a Log Analytics workspace or accessible via Application Insights Analytics.
• Go to Azure Monitor > Logs (or Application Insights > Analytics) and write KQL queries, e.g.:

• cloud applications only
• all Web traffic including cloud applications

• Cloud applications only: Only traffic to cloud apps is steered to Netskope for inspection/enforcement; other traffic bypasses.
• All Web traffic including cloud applications: All web-bound traffic, including cloud app traffic, is steered to Netskope.

• Browser isolation, Web traffic only, or a vague “traffic only” option are not the standard two steering modes.
• These two configurations let you decide what traffic Netskope analyzes in real time and what is bypassed.

• The “Answer(s)” field lists B and C (likely incorrect). The explanatory text correctly describes cloud applications only and all Web traffic including cloud applications as the two configurations.

• In Spark, an executor is a JVM that can have multiple cores. Each task can consume some CPUs (spark.task.cpus).
• The executor’s resources are effectively partitioned into slots, where each slot can run one task. The number of slots per executor is roughly spark.executor.cores / spark.task.cpus.
• Therefore, multiple tasks can run in parallel within the same executor (via these slots). So the statement “Tasks run in parallel via slots” is correct.

• A: A slot is not another name for an executor; a slot is a unit inside an executor.
• B: There’s no requirement that there must be fewer executors than tasks; tasks can be scheduled over time across the available slots.
• C: An executor can run more than one core; it’s not limited to a single core.
• D: There isn’t a rule that there must be more slots than tasks; tasks can wait if slots aren’t available, and you can have equal or even fewer slots than concurrent tasks.

1. Define Power Platform DLP policies
2. Add custom prompt modifications
3. Conduct adversarial testing

1. DLP policies first

1. Prompt modifications second

1. Adversarial testing last

• Amazon Kendra is a managed enterprise search service that can index content stored in S3 and support natural-language queries to find text inside documents (PDFs, Word files, etc.).

• Rekognition analyzes images/videos, not document text search.
• Polly is a text-to-speech service.
• Lex is a chatbot service.

• Create a Kendra index.
• Add a data source of type S3 and point it to your bucket (with an IAM role that allows access).
• Configure/document conversion if needed, then index the data.
• Use the Kendra API or console to run natural-language queries against your indexed documents.

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

• SageMaker endpoint: Not required because the model is being used through Amazon Bedrock.
• SageMaker Model Registry: Used for managing SageMaker models, not for making a Bedrock custom model available.
• Grant access in Amazon Bedrock: IAM permissions may still be needed, but granting access alone does not provide the required inference capacity.

• A) configure matching hold and delay timers

• B) configure matching key-strings

• C) configure matching priority values

• D) configure unique virtual IP addresses

• The correct answer is Mass Transfer Tool.

• The Mass Transfer Records tool is Salesforce’s built-in way to reassign ownership of existing records in bulk. In this scenario, you need to transfer ownership of the departed rep’s accounts and opportunities to a new rep while keeping the team structure intact.

• Go to Setup > Data Management > Mass Transfer Records.
• Choose the object: Accounts (and then Opportunities, if needed).
• Set “Transfer From” (the leaving rep) and “Transfer To” (the new rep).
• Decide whether to transfer related records as well (e.g., opportunities tied to accounts) and proceed.
• Review and confirm.

• Data Loader / Data Import Wizard are for bulk import/export, not bulk reassigning ownership.
• Dataloader.io is a third-party tool; the built-in Mass Transfer tool is the standard Salesforce method for this task.

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

• In Microsoft Entra (Azure AD), admin roles can be scoped to either the entire directory (tenant) or to an Administrative Unit (AU). To assign a role at an AU scope, the user must be a member of that AU.

• Roles in question: Security Administrator and User Administrator can be scoped either to the Directory or to a specific AU.

• User1 is a member of AU1. Therefore, User1 can be assigned either at the AU scope (AU1) or at the Directory scope (global).

• User2 is not a member of AU1. Therefore, User2 cannot be assigned at the AU scope; the valid scope for User2 is only the Directory scope.

• User1: can be assigned at AU1 and at Directory scopes.
• User2: can be assigned only at the Directory scope.

python 
import azure.cognitiveservices.speech as speechsdk 


speech_config = speechsdk.SpeechConfig( 
    subscription="YOUR_KEY", 
    region="YOUR_REGION" 
)

Important Azure Speech SDK classes

• SpeechConfig

• AudioConfig

python 
  audio_config = speechsdk.audio.AudioConfig( 
      use_default_microphone=True 
  )

• SpeechRecognizer

python 
  recognizer = speechsdk.SpeechRecognizer( 
      speech_config=speech_config, 
      audio_config=audio_config 
  )

• SpeechSynthesizer

• AudioOutputConfig

 Bogotá, Colombia